Hey guys,

I've taken some time off from making my own CMS but now I want to get back in the ring, so to speak.

Now, the thing that bothers me, is where to start. I've got my MySQL class set up but where do I go from here? How do I make the structure for the template, modules, blocks and so on. What's the best approach on this particular subject.

I hope you guys can fill me in a bit.

Mark

__________________

"Life is a bitch, take that bitch on a ride"

Make the Template class first, that will be very important, Modules and Blocks and certain Addons can come later, but your best bet is to make a Template class first, then possibly make an SMTP class for handling the emails, and whats going in and out. Just by making these classes, and then starting on the main work is good, considering then you got everything you need right there, and it should help you a bit. :]

__________________
VillageIdiot can have my babbies ;d

I would suggest going for the database module first, then the template system, and after that, make some global input filtering. But before you start these out, I suggest you go and create a list of requirements and basic functionality for what you want to do (using a pencil and a piece of paper, that is). Makes stuff easier later.

__________________

I'd go with the pencil (PENCIL, no pen, you'll do lots of erasing) and paper, from experience..

1. templating class
2. cache class (if you'll have it)
3. input filtering system
4. mailing system.
5. module system
6. member system
7. all your modules and addons

(thats atleast my personal preference as far as things go)

He already made a SQL class. :/

__________________
VillageIdiot can have my babbies ;d

Well, I think after you finish your MySQL Class you can start on your session/authorization classes. Since most developers primary mission in creating a CMS is to manage their users, I find that the user related scripts need to follow the database scripts.

After the session/authorization classes, are written, you can start on the index.php which should act as the traffic control agent for your system. index.php should direct the script to the classes and functions that will be used for the user's request.

Once you have the index started, you can work on the template class. Since the template is very much dependent upon the action you are performing, it will be a continuous project.

Maybe I do things differently than everyone else but I like to work on a section of code and get it to work then build on that for the next section. For example, I usually hard code some sample output for whatever action I am coding then if it works, I modify the code to use the template and of course, I add the proper code to the template class to make it work.

Another thing, go ahead and manually add content items to you database and when the frontend system works correctly, then design the backend system for the administration of the CMS.

vujsa

__________________
Need PHP Help? - Handy PHP

Thank you all for replying on such a short notice. I'm eager to start off as soon as possible.

I noticed that some of you have a different way of approaching basic elements like the MySQL class and so on. Not that it matters much, though. I like each and every one of you guys perspective and I will make sure to take bits of each suggestion/advice.

Surely I will ask a lot of more questions here, but for now I am going to start off finishing up some old work.

Once again, thanks you all!

Viva la TalkPHP.

__________________

"Life is a bitch, take that bitch on a ride"