Confirmed users, Bureaucrats and Sysops emeriti
1,737
edits
Website CMS:Requirements: Difference between revisions
no edit summary
No edit summary |
|||
| Line 61: | Line 61: | ||
* Users will have their own usernames and passwords to login | * Users will have their own usernames and passwords to login | ||
* Simplified front end for Bugzilla (similar to [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=itrequest IT requests] (would require integration with bugzilla japan)) | * Simplified front end for Bugzilla (similar to [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=itrequest IT requests] (would require integration with bugzilla japan)) | ||
= Can we build on an existing CMS? = | |||
I've had discussions with a variety of people about this, and it's always a gray area. One CMS seems great, but doesn't do one or two important things - another has some features we like, but is written in ASP. I reviewed several CMSs (narrowed down by pages like [http://cmsmatrix.org CMS Matrix]), and most of the candidates fell short pretty quickly. People I talked to sent me some other potentials, but they didn't fit our requirements either. Some of the common problems included: | |||
* Marrying the site to a database, meaning the CMS stores all our data in a database. Flat files are definitely a requirement of the CMS, so these wouldn't do. | |||
* A lot of CMSs have their own template files and URL structures, that wouldn't be compatible with what we have now (more on why what we have is good below) | |||
* A lot of the large CMSs ([http://typo3.com/ typo3], I'm looking at you...) could probably do what we need, but I don't think the trade off in complexity is worth it. | |||
Right now, mozilla.com is setup well: | |||
* locales are divided up by directory to allow easy management (both of files and permissions) | |||
* automatic language fall back to english (but if a new file is created in the requested language, it will be given instead automatically) | |||
* lightweight code - there is no heavy framework included on the pages | |||
* consistent headers/footers (templating) | |||
* ability to tweak menus/headers/etc. on a per language basis | |||
* etc. | |||
I have no doubts we could modify an existing CMS to fit our needs, but I'm worried about the time commitment, and afterwards ending up with something that isn't ideal. There may be a perfect CMS out there, but finding it can be an exercise in futility. (The sad result being, we add to the clutter with our own). | |||
I'm hoping we can focus on usability and simplicity with our own CMS. By talking with localizers and others that actually use it, we have a good idea of what we need, and I'd like to stay close to those requirements. | |||