India Grill.. yum.
Permalink
So the core team all just mustered a little pre-turkey day Indian chow down and came to any number of exciting conclusions about feature focus and priorities going into 2009. Here's some of the stuff we're going to be working on and launching over the holidays:
1) the marketplace, duh. This is going to come out end of year.
There will be a single destination page for every block, and on that page you'll have your own discussion area, bug tracker, etc. There will be the ability to group blocks together into lists so you can package a bunch of stuff up into something that makes sense for a cleint, and buy it all in one fell swoop.
It's also going to have direct hooks into c5. So if a site owner is adding blocks, or browsing themes they might be doing it from their end site's interface as much as they are from concrete5.org
2) There will be an improved level of "owner-centric" controls in the dashboard. There will be reorganization and the addition of a lot of little things,(ie: spot for a google analytics code that will be automatically added to every page.) Also as part of this, Themes will get an optional "owner controlled" CSS style sheet. A theme developer can choose to add this, define some stuff in there - and end users will be able to mess with options in some preview-y dashboard interface.
The goal here is go get "Joe the site owner" to a spot where he wants to actually mess around with his site till the wee hours in the morning getting it look better to him. Look at what people do with MySpace! Let's give them a chance to be creative, with some better controls built right in.
3) We're going to be slowing down the build cycle. In order to give the international folks a chance to catchup on translating the ever growing list of strings we keep making as we add to the core, we're planning to run with more release candidates "RC" and fewer major upgrade releases. Andrew will post more about this I'm sure - but in the meantime, please keep giving us your great direction at:
http://www.concrete5.org/community/features/...
thx!
1) the marketplace, duh. This is going to come out end of year.
There will be a single destination page for every block, and on that page you'll have your own discussion area, bug tracker, etc. There will be the ability to group blocks together into lists so you can package a bunch of stuff up into something that makes sense for a cleint, and buy it all in one fell swoop.
It's also going to have direct hooks into c5. So if a site owner is adding blocks, or browsing themes they might be doing it from their end site's interface as much as they are from concrete5.org
2) There will be an improved level of "owner-centric" controls in the dashboard. There will be reorganization and the addition of a lot of little things,(ie: spot for a google analytics code that will be automatically added to every page.) Also as part of this, Themes will get an optional "owner controlled" CSS style sheet. A theme developer can choose to add this, define some stuff in there - and end users will be able to mess with options in some preview-y dashboard interface.
The goal here is go get "Joe the site owner" to a spot where he wants to actually mess around with his site till the wee hours in the morning getting it look better to him. Look at what people do with MySpace! Let's give them a chance to be creative, with some better controls built right in.
3) We're going to be slowing down the build cycle. In order to give the international folks a chance to catchup on translating the ever growing list of strings we keep making as we add to the core, we're planning to run with more release candidates "RC" and fewer major upgrade releases. Andrew will post more about this I'm sure - but in the meantime, please keep giving us your great direction at:
http://www.concrete5.org/community/features/...
thx!
Is releasing ecommerce block/interface part of number 1?
Is there a way to be able to turn off the "store" and the redirect to this forum in the new versions? Checkbox not a fork, or in config. I mean we can constantly fork our install we make for clients, but some of us might want to support our clients without them turning to the forum first because it is in the admin panel.
If I can get $200 line item for a gallery and the client goes to the store to see they can get it for $70, even though it took 5 hours to theme it then that makes me look bad.
Yes, no?
If I can get $200 line item for a gallery and the client goes to the store to see they can get it for $70, even though it took 5 hours to theme it then that makes me look bad.
Yes, no?
Yes, we'll have everything switchable, and we won't require any changes to current themes or blocks architecture that might put any of your efforts as a fellow web developer backwards.
If anything, we'll give you some better infrastructure to let your clients engage you on small tasks.
If anything, we'll give you some better infrastructure to let your clients engage you on small tasks.
Thank you. I know this wasn't specifically mentioned in this post but in a few others (the whole block thing and the central forum). This is an amazing idea and letting us turn parts of it off is a great idea.
Now i know this is a biggie and probably a pain in the ass to do, but would there be a way to let the developer get a cut (if only credits for c5 forum etc. blocks) by seeding the installs to our clients and their subsequent block purchases by end users? Kind of an affiliate thing, gift that keeps on giving to the developer sort of thing? I am not really interested in it, but I could see the idea that some would find beneficial for those that give out free c5 hosting or something of that sort. Not my cup of tea but I know some guys somehow do that.
Now i know this is a biggie and probably a pain in the ass to do, but would there be a way to let the developer get a cut (if only credits for c5 forum etc. blocks) by seeding the installs to our clients and their subsequent block purchases by end users? Kind of an affiliate thing, gift that keeps on giving to the developer sort of thing? I am not really interested in it, but I could see the idea that some would find beneficial for those that give out free c5 hosting or something of that sort. Not my cup of tea but I know some guys somehow do that.
thats a good idea.
what ever we can do to make it easier for site buiders interact with site owners - we're for it.
anything else?
what ever we can do to make it easier for site buiders interact with site owners - we're for it.
anything else?
How block translation will be managed, for now we can find in messages.po the translation strings for the blocks you ship with C5.
But for all the others blocks, applications, what is your idea about translation management?
sorry if this was already discussed, but i didn't find it
But for all the others blocks, applications, what is your idea about translation management?
sorry if this was already discussed, but i didn't find it
I don't have a brilliant answer on that one sadly. We're going to be creating a bunch of searchable/sortable flags around blocks so certainly we could do a matrix of what languages were available with them. The reality is, with community driven code we'll have to expect the translations for individual blocks will fall behind the core. I think it'll have to be the responsibility of block owners to motivate folks to take care of translation for them. I envision a reality where less popular blocks probably don't make it out of english, but really good ones end up in as many languages as the core...
if there's a better idea, i'm all ears..
in terms of technically how, i'm thinking an individual translation file for each non-core block.
if there's a better idea, i'm all ears..
in terms of technically how, i'm thinking an individual translation file for each non-core block.
Why not offer a subversion repository for block developers?
I don't mind translating a few strings to German for another block developer as long as it isn't too complicated..
A place where we could upload our po files would be enough, wouldn't it?
I don't mind translating a few strings to German for another block developer as long as it isn't too complicated..
A place where we could upload our po files would be enough, wouldn't it?
However, undocumented though it may be, blocks do have the ability to contain their own custom strings file.
So, for example, if the core c5 language stuff is at
/languages/de_DE/LC_MESSAGES/messages.po
Then, there is also an (optional) /languages/ directory that can be included in blocks. So, a block maker could provide multiple translations of his or her block by including
/languages/de_DE/
/languages/fr_FR/
etc... in their block's directory. These will be used if they exist, otherwise they will be skipped over.
So, for example, if the core c5 language stuff is at
/languages/de_DE/LC_MESSAGES/messages.po
Then, there is also an (optional) /languages/ directory that can be included in blocks. So, a block maker could provide multiple translations of his or her block by including
/languages/de_DE/
/languages/fr_FR/
etc... in their block's directory. These will be used if they exist, otherwise they will be skipped over.
but what actually is more important to me are the part you have to translate because you want to print it on the page (and not only to the user using c5 to edit a page)
You might want to check the message "content blocks display..." herehttp://www.concrete5.org/community/forums/internationalization/mult...
His explanation is better ;-)
You might want to check the message "content blocks display..." herehttp://www.concrete5.org/community/forums/internationalization/mult...
His explanation is better ;-)
