Is impressCMS going to follow the GoPHP5 initiative???
http://www.gophp5.org
We should register?
Clap Clap Clap!!... Congratullations Ana!... nice work!!!... lets make the theme right now... i want to see our new site working nowwwww!!!
I mentioned to Marcan I'd like to propose we use GiJoes "Easiest Multi language" hack in the ICMS core.
Although there are probably better ways to achieve this at a later day, most multi-language methods work the same way - ie by language code "" etc... so this should not effect content overall.
Marcan proposed adding a setting to enable/disable this - with it being set to off by default.
What's everyone's thoughts?
Unless I'm mistaken - the colour/image would change on the center banner depending on which site you where on.
My 2 cents...
Slice that puppy up and get it online!!!
Nice work Ana!
I honestly didn't think I'd like green, but that really is nice!
IMHO... #2, but drop the "!"
EDIT: Now that I've looked at the completed layout, Green is good, but still drop the "!".
i like the text balloon, it's a sign of communication! Also the "!" is ok i think, isn't it?
1. Loose the exclamationmark at the end (!), it's really a steal from Joomla!.
2. The text balloon, what does that refer to?
3. A logo consists of an imagemark and a wordmark. It would be great to have both.
Herko
Quote:
snow wrote:
- What would these small variations be in between themes for each area?
- What width should the theme be?
I had planned this theme to be fixed width at 960 pixels.
ana, I love it!
will love to see when its running
great, ana! Keep on good work!
michael
I'll let everyone else reply first - but - I am very impresed.
I am attaching here template #6 viewed with the logo proposal in green version.
So besides deciding the logo, there's some things of the design in case this one is chosed that need to be decided too.
- What would these small variations be in between themes for each area?
- What width should the theme be?
I had planned this theme to be fixed width at 960 pixels.
About building it:
I can build it using a personal morphogenesis template I use to make most of the things I do. It contains only 1 table and if the styles are disabled it still looks as if it were tableless. If it were fixed width I could try do all the rest of the design without tables but if it were percent that's harder for me and would have to add a couple of tables. In case of percent I'd add tables if the theme were to have the shadow it has now at the sides and if curved corner stretching boxes are needed. If that's ok with you all I can make it like this.
In case of yes. I'd need the requirements defined and if changes are needed, for them to be specified.
Quote:
snow wrote:
I think it's better to stick to one color that never changes.
I think it's better to stick to one color that never changes.
I preffer the bolder ones, and the green or plumb colour is very nice .... plumb looks more "posher" to me
As a thought - perhaps the colour could change on each sub-site?
Or is it better sticking to a single colour for corporate reasons?
(off topic: if any designer ever wants a laugh - look at the intel or nvidia guidelines on using their logo and name .. ouch!)
Here are some more samples.. and changing the yellowish orange to some other colors. I like apple green.
The slogan is added, don't know if that's the one. And an exclamation mark, don't know if that should stay or go.
P.S. I'd draw a leaf but I don't know how to
Yesterday, I committed changes in revision 14, including updating the changelog. Later, young-pee committed revision 17, including changes to the changelog, which wiped out my changes to the changelog. I updated my sandbox and made another commit, revision 18, again with the appropriate entries in the changelog. Revision 19 reverted to revision 17, going back to a previous version of the changelog.
The changelog will be the most edited file in the repository and we need a process to make sure all the changes get recorded with every revision.
Yep, I worked many hours trying to find a solution. I promise I will do everything I can to fix this after our first release. Perhaps other great developers on are team will also have solutions to propose. Bur for now, I would really like to see the items mentioned in the 0.5 version of our roadmap ready for jan 1st.
But we'll fix this sooner or later