[Dev] More for my own sake..TowelCMS

Well, because of a lack of braincells in my body, I am re-writing this thread.

TowelCMS

Mission Statement:
To create a Content Management System similar in design to WordPress but with coding I can understand and learn from. This CMS will not be released, and will simply be used as a framework for all my websites in teh future.

Basic Features (Complete)

- News/Content via MySQL.
- Sidebar Widgets using PHP and SQL (Easy Plug-and-Play).
- View Random Pre-set Advertisements via MySQL.
- Plug-N-Play Themes/CSS/Templates

Basic Features (Incomplete)

- News/Content via MySQL.
- Sidebar Widgets using PHP and SQL (Easy Plug-and-Play).
- Create/Edit/Delete Posts (Content).
- Create/Edit/Delete Pages (Content Catagories).
- Edit/Delete Advertisements.
- View Random Pre-set Advertisements via MySQL.
- Plug-N-Play Forum.

Screenie (Layout sucks nuts).

http://s13.postimage.org/lsomdo9ed/Untitled_4.png

And White

http://s16.postimage.org/wr9zq3ann/Untitled_5.png

Umm... so this thread is for you to store the directory structure of your application? You want us to critique... the structure? Because there is no code, or screenshots, or demos to critique. I understand that you will be later adding your screenshots and a demo link.

Okay then... my file structure suggestions (difficult to do this without seeing code/demo):
- Change /pages/index.php to pages/home.php

The rest is optional; my personal preference:
- Change /style to /css
- Change /pages to /views

The way you handle pages and templates is, at face value, a little odd. It says content within the templates. So the content is loaded into the template? Seems a bit unnecessary with the scattered structure you are using.

Ideally, if you were to use a MVC-esque design pattern, /templates would be /views, /index.php would point to a controller, which then loads content into the views via a Template class. And models would be called when data is needed from the database to be placed into the views.

yeah im not going to lie, I was really baked when i wrote that thread ^^ the index page grabs the theme option set by a get variable, then stored in a session.

The index page loads the corresponding CSS file, then inserts templates (divs/paragraphs/scripts to grab content from sql db) and loads the page based on a GET function, acquired and verified by index.php.

It's really not that complex, and I've only jsut started adding the SQL bits. After I try to make it mostly injection-proof I will post a live demo :D