FWIW I would be saddened to see another weekend hack Ruby CMS, but I'd love to see these company-backed ones (refinery, browsercms) made awesome. Being Ruby and on GitHub, its pretty easy to make modifications that can be eventually merged into the main codebase.
If you must start from scratch (and there may be good reasons to) I would like to add that I think Radiants "no fluff" attitude sets the bar too low for what should be core functionality. eg. the ability to reorder pages in Radiant requires an extension, and I couldn't find one as natural to use as bcms's built in drag and drop. There are things that are very hard to add later , and there are things that are necessary for 90% of projects with non-technical users eg. a decent editor - that should be in early. Along these lines I would strongly suggest making it an engine or whatever that can integrate with an existing app eg. Spree or plain Rails -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
