4 ms·
You can make a production quality CMS in a few days as long as it is specialized. Genericity is the productivity killer. I spent some time revamping my website
by tybris 17y ago
You can make a production quality CMS in a few days as long as it is specialized. Genericity is the productivity killer.
I spent some time revamping my website last weekend after having done no web development for about 4 years. I roughly split up my time like this:
-2 hours to build a proxy to S3 in GAE (Custom)
-2 hours to set-up a pure-Java PHP implementation on my GAE proxy (OSS)
-3 hours to set-up a WebDAV interface to S3 in GAE (OSS)
-4 hours to create XSLT templates and build them automatically (Custom)
I use NetDrive to connect to S3, and Kompozer to edit the content. Highly scalable, nearly free website with a perfectly good CMS and no need to make back-ups. Updating the software or adding services is as simple as typing my password in Eclipse. (by the way, everything in Java)
Over the years I've found web developers are not the smartest types.
- smanek 17y agoI don't think CMS means what you think it means ... You have to manually edit files and code to do things. And that's fine - that's how my website is run too. But that isn't a CMS. A CMS provides a pretty interface for everything content managers need to do. It allows non-technical people to publish, edit, and collaborate. It has a publishing system so modifications can be approved before being pushed live (which in turn implies an access control system).
- tybris 17y agoI don't edit the pages directly. I edit the content using Kompozer (wysiwyg web authoring) and that gets automatically transformed into a website.