Status update

Ruby Apps Radiant CMS
1

I’m an humble user of the radiant system. From this standpoint, I feel
the need, and it would be great, if we could do collectively, as
members at various title of this community, lead by John as the
benevolent dictator, a status update of the 1) core system road map
(in terms of features, where are we today, where do we want to go,
when do we hope/wish/think we could be there …); 2) third party
working behavior/plug-ins (in terms of functionality, where they
could be found/downloaded, their evolution); 3) system documentation
(how to install/maintain the system; how to setup a navigation system;
how to simply extend the system–what is, for example, the best
“radiant way” to writing and reading some data from an external
database/table; etc.). Finally, could/should we do this on the wiki or
on the mailing list? Hope this request doesn’t seem too rude or naive
… --M

2

Maurizio B. wrote:

I’m an humble user of the radiant system. From this standpoint, I feel
the need, and it would be great, if we could do collectively, as
members at various title of this community, lead by John as the
benevolent dictator, a status update of the

  1. core system road map
    (in terms of features, where are we today, where do we want to go,
    when do we hope/wish/think we could be there …);

Back in May I posted a tentative road map:

http://lists.radiantcms.org/pipermail/radiant/2006-May/000165.html

Which contains the features I am looking to implement. I had meant to
revisit this collecting everyone’s input at some point, but haven’t had
the time. A quick revamp of the old road map with updated version
numbers (as we decided to release Grindstone as 0.5 instead of 0.1 in
order to indicate the project’s maturity):

0.5 - Stability
–database support
–setup script
–documentation

0.6 - Plugin System
–clean up behaviors
–configuration tab
–make it easy for plugins to add tabs to the UI

0.7 - Full Featured Blogging Engine
–commenting system for every page
–additional helps for RSS?
–tagging for pages
–search?
–import scripts for other major blogging engines?
–Support for MarsEdit and other APIs?

0.8 - Assets and Attachments

0.9 - Drag and Drop
–drag and drop sortable page view
–<r:next /> and <r:previous /> tags for siblings

1.0 rc1 - Workflow: Version Control and Permissions
–simple version control
–additional roles: publisher, ?writer?, ?editor?

After 1.0
–true multi-lingual support?

The fun part about all of this is that this is road map for features I’m
planning to work on in the order that I think they should be done. A
couple of people are working to preempt me by working on features that
they would like to see sooner rather than later.

  1. third party
    working behavior/plug-ins (in terms of functionality, where they
    could be found/downloaded, their evolution);

I’d love to see someone take up the challenge of developing a third
party plugin site for Radiant. We need something like Textpattern’s
http://textpattern.org/. In the meantime there is only this:

http://dev.radiantcms.org/radiant/wiki/ThirdPartyBehaviors

  1. system documentation
    (how to install/maintain the system; how to setup a navigation system;
    how to simply extend the system–what is, for example, the best
    “radiant way” to writing and reading some data from an external
    database/table; etc.).

This would be a great place for the Radiant docs project to start. I’d
suggest that you coordinate with Rodney on the docs mailing list if
you’d like to help out:

http://lists.radiantcms.org/mailman/listinfo/radiant-docs

Finally, could/should we do this on the wiki or
on the mailing list?

It’s up to Rodney Ramdus right now. He’s in charge of the docs project.

–
John L.
http://wiseheartdesign.com

3

On 11-Jul-2006 11:43 -0400, John W. Long was heard to say:

  1. third party
    working behavior/plug-ins (in terms of functionality, where they
    could be found/downloaded, their evolution);

I’d love to see someone take up the challenge of developing a third
party plugin site for Radiant. We need something like Textpattern’s
http://textpattern.org/. In the meantime there is only this:

http://dev.radiantcms.org/radiant/wiki/ThirdPartyBehaviors

I think this is absolutely sufficient for now, considering the frequency
at
which plugins / behaviours are currently added. One improvement of this
page could be if maintainers or users flag those behaviours that are
currently broken and announce it on the mailing list.

Once many more plugins or behaviours are created a dedicated repository
with search functionality, rating and issue tracking is certainly a good
idea.

Oliver