Before you decide on the CMS system, I suggest that you consider the following.
1) Is the site static. (Does it include posting forms, validation and
stuff that cannot be handled by a third party service?)
2) Are you going to build an app around the CMS or is just purely for
displaying the content?
3) Would you users (complete non techies) update the content?
If your answer is no to the above, I would strongly suggest static
website generators like webgen or jekyll. They give you the best parts
of the CMS in terms of layouts and markup and helpers and such and
they generate static html files. When served of a static file server
like nginx, they are just bloody crazy fast. And the best part is that
you have the full programmability of Ruby. If you are bothered about
those pesky .htmls in the end, you can make them go away with the
magic of mod_rewrite. And with the power of javascript, you can mashup
stuff like comments by embedding an iframe in the page. This is the
way sites like disqus do it.
Regards,
Vagmi
http://blog.vagmim.com
“There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the
other way is to make it so complicated that there are no obvious
deficiencies." C.A.R. Hoare.
--
You received this message because you are subscribed to the Google Groups "BANGALORE RUG-Ruby Users Group" group.
To post to this group, send an email to bangal...@googlegroups.com.
To unsubscribe from this group, send email to bangalorerug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bangalorerug?hl=en-GB.
I'll add my voice to the static site generator recommendation. For
'brochure' type sites they can be an invaluable way to manage the
content. I personally have used nanoc and jekyll and like them both
(although they have different strengths).
That said, if the content needs to be user editable they may not be a
great fit.
-- James Healy <ji...@deefa.com> Thu, 17 Dec 2009 21:12:57 +1100