Projects

no-cms

About noCMSIf you are running one or several simple website(s) you'll probably want something that helps you maintain your content. Preventing yourself from having to edit all the pages separately if you want to change something to the layout or add an item to the navigation menu. There are ... [More] numerous CMS-es (content managements systems) out there which can do this for you. But most of this systems are far to big for a simple website. And if you have some knowledge about CSS and HTML you'll probably notice that you'll end up tweaking and updating the system rather than work on the site itself.. Content ParsingThis is where noCMS comes in. noCMS is a content parsing system. Which means that it simply takes an HTML file with content and an HTML file with a template and mixes them together. It will thus help you menage the content on your website(s) but in a very simple way without databases, back-end user interfaces, user policy's and archiving options. If someone is visiting your website ('http://www.mydomain.com/somepage/'), a file on the server will catch this request and send it to the processing file of noCMS. noCMS will then understand that the visitor want to see the contents of 'somepage' and thus look for a page called 'somepage.html'. Before sending this page back however it will load the template file and wrap the contents in this template. So it will serve the visitor with an on-the-fly created output. The next step then is that there will probably be some common contents on your webpages. For example if a list of links is appearing on various pages, you would like to create this list only once or even let the system create it for you by scanning which files are in the folder. This part is solved by Elements and Code object. Actually these objects are nothing else than HTML (elements) and PHP (code) files that can be included into pages and template files by using simple tags. System Requirements A server running: PHP (5.2.2 or newer) mod_rewrite enabled (see http://en.wikipedia.org/wiki/Rewrite_engine) Experience LevelHTML (editing your site contents) CSS (editing your layout, if you wish) FTP (uploading files) Possibly: Parking/Addon/Subdomains (only for multiple domains with one installation see this page) [Less]