I was recently looking at Matt Raible''s Blog<http://raibledesigns.com/comments/rd/sunsets/building_a_website_with_an#comments>. He was commenting on what he thought a good CMS would possess. Here is the list from his blog: - *Design customization:* I should be able to customize all the (X)HTML that''s generated using one or two files (like SiteMesh allows). It should be possible to change the look and feel of *everything* by modifying some CSS. It should also be possible to use Mike Stenhouse''s CSS Framework<http://www.contentwithstyle.co.uk/Articles/17/a-css-framework>to simplify layout choices for clients. Ideally, a web designer or regular ol'' HTML person could do the customization. - *Static-looking URLs:* The site should look like a static site. The URLs should be all lowercase and end with .html. It should be possible to modify all the URLs to look as if all pages are static. Apache''s mod_rewrite and the URL Rewrite Filter are great tools for making this happen, but it''d be nice if the administration of the application allowed for setting these rules. - *It shouldn''t look like a CMS:* No login links, no registration links, etc. - *Ability to easily add dynamic content:* It should be easy to add dynamic content - such as RSS Feed headlines to pages. - *Menu Customization:* In the application, it should be possible to create menus (both main and local navigation) and configure a page to highlight a menu when a particular page is shown. - *Versioning of pages:* In case someone messes something up, it should be easy enough to revert back to a previous version. - *Easy to use:* It should be possible to train a marketing person (with little technical knowledge) how to use the system in 10-15 minutes. For technical companies (such as Virtuas <http://virtuas.com/>), there are a few additional requirements I''d like to see: - *Articles with syntax highlighting:* It should be easy to publish articles with code that''s colorized. The Java2HtmlPlugin for JSPWiki<http://www.java2html.de/>is a good example of this. I currently don''t know of any for XHTML, XML or scripting languages like Ruby or Python. - *File Upload:* For uploading white papers and other technical publications. Naturally he was speaking in Java, but the same needs apply to any CMS. I was wondering if there were additional elements that you would include, or perhaps ones that you would prefer not to have? Thank you for your input. Dave -- ~~~~~~~~~~~~~~~~~~~ D''Andrew Thompson http://dathompson.blogspot.com _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
* an asset manager - one place to handle versioning of all images, videos, documents, pdfs, etc. to be used throughout the site. * a users and groups manager, giving the admin the ability to lock down and open up the site. * RSS publishing option for all content * the ability to integrate custom applications into the site D''Andrew Thompson wrote:> I was recently looking at Matt Raible''s Blog > <http://raibledesigns.com/comments/rd/sunsets/building_a_website_with_an#comments>. > He was commenting on what he thought a good CMS would possess. Here is > the list from his blog: > > * *Design customization:* I should be able to customize all the > (X)HTML that''s generated using one or two files (like SiteMesh > allows). It should be possible to change the look and feel of > *everything* by modifying some CSS. It should also be possible > to use Mike Stenhouse''s CSS Framework > <http://www.contentwithstyle.co.uk/Articles/17/a-css-framework> > to simplify layout choices for clients. Ideally, a web designer > or regular ol'' HTML person could do the customization. > * *Static-looking URLs:* The site should look like a static site. > The URLs should be all lowercase and end with .html. It should > be possible to modify all the URLs to look as if all pages are > static. Apache''s mod_rewrite and the URL Rewrite Filter are > great tools for making this happen, but it''d be nice if the > administration of the application allowed for setting these rules. > * *It shouldn''t look like a CMS:* No login links, no registration > links, etc. > * *Ability to easily add dynamic content:* It should be easy to > add dynamic content - such as RSS Feed headlines to pages. > * *Menu Customization:* In the application, it should be possible > to create menus (both main and local navigation) and configure a > page to highlight a menu when a particular page is shown. > * *Versioning of pages:* In case someone messes something up, it > should be easy enough to revert back to a previous version. > * *Easy to use:* It should be possible to train a marketing person > (with little technical knowledge) how to use the system in 10-15 > minutes. > > For technical companies (such as Virtuas <http://virtuas.com/>), there > are a few additional requirements I''d like to see: > > * *Articles with syntax highlighting:* It should be easy to > publish articles with code that''s colorized. The Java2HtmlPlugin > for JSPWiki <http://www.java2html.de/> is a good example of > this. I currently don''t know of any for XHTML, XML or scripting > languages like Ruby or Python. > * *File Upload:* For uploading white papers and other technical > publications. > > Naturally he was speaking in Java, but the same needs apply to any > CMS. I was wondering if there were additional elements that you would > include, or perhaps ones that you would prefer not to have? > > Thank you for your input. > > Dave > -- > ~~~~~~~~~~~~~~~~~~~ > D''Andrew Thompson > http://dathompson.blogspot.com > >------------------------------------------------------------------------ > >_______________________________________________ >Rails mailing list >Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >http://lists.rubyonrails.org/mailman/listinfo/rails > >-- Clint Pidlubny clint-DOvxo+vduAZWk0Htik3J/w@public.gmane.org 612.590.8343
* Internationalization (i18n). Regards, Peter
@products = Product.find_all Which, if any, is true: @products is an instance of the Product class and the above is the same as @products = Product.new, @products.find_all OR @products is given a value returned by the Product class method, find_all. So in this case @product would be an array of Product class. And you could not do @products.destroy, but you could do @products.Product[3].destroy? Thanks in advance, Kris.
On Sep 16, 2005, at 6:47 AM, Kris Leech wrote:> @products = Product.find_all > > Which, if any, is true: > > @products is an instance of the Product class and the above is the > same as @products = Product.new, @products.find_allNo> OR > > @products is given a value returned by the Product class method, > find_all. > So in this case @product would be an array of Product class.Yes, a collection of objects of type Product.> And you could not do @products.destroy, but you could do > @products.Product[3].destroy?Right, but @products[3].destroy. -- Scott Barron Lunchbox Software http://lunchboxsoftware.com http://lunchroom.lunchboxsoftware.com
Thanks Scott, that clears that up :) Sorry Dave for posting in your thread... a mistake! Scott Barron wrote:> On Sep 16, 2005, at 6:47 AM, Kris Leech wrote: > >> @products = Product.find_all >> >> Which, if any, is true: >> >> @products is an instance of the Product class and the above is the >> same as @products = Product.new, @products.find_all > > > No > >> OR >> >> @products is given a value returned by the Product class method, >> find_all. >> So in this case @product would be an array of Product class. > > > Yes, a collection of objects of type Product. > >> And you could not do @products.destroy, but you could do >> @products.Product[3].destroy? > > > Right, but @products[3].destroy. >-- Interkonect Services UK Ltd. Boundary House Main Street Hoveringham Nottingham NG147 JR web: www.interkonect.com tel: 0115 9663696 fax: 0115 9663696
* Not just internationalization, but full multi-lingual content Cheers, Brett On Sep 14, 2005, at 6:46 AM, Peter C. Verhage wrote:> * Internationalization (i18n). > > Regards, > > Peter > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >