On php, mysql, and web development
Considering this page is going to get a bit lengthy, I propose a challenge to myself: before the page should start paginating (10 posts, generally) I will be pulling records from the database, paginating them, and have an admin to manage them from.
Considering that I want this to become open source software, when should it "launch" in alpha, beta, or whatever? I don't have any sort of training in source control. I'm signed up with sourceforge here: mpcms.sourceforge.net but that doesn't really help me in the slightest because I dont know at what point I should say "hey this is version 0.1, so everyone start using it!!!"
Gonna have to do some research in that area.
Wednesday, July 8, 2009 - by Tim
Only 2 days in, and I'm already dying for an administration area.
The $mpCMS object gets created correctly, and connects to the database. In fact, it's doing it behind this humble HTML post. I have plans for how it's going to build itself, starting with the philosophy that the only thing the $mpCMS object will do is load the config file, connect to the database, and then dynamically load the appropriate modules. From there, everything is going to be module-driven. Even plugins; the plugins are all going to be stored in the database, so there's going to be a module to manage them as well. The core modules so far are as follows:
There will be others. All core modules will be things I feel should be supported by any deployment type out of the box, and will come preloaded with any copy of mpCMS.
Settings Manager being one of the easier things to create, I started there. A table to hold the settings, and a class extending $mpCMS to hold an array of the settings, and a few methods to load them, save them, and present them to the system.
More to come in the next few days; I REALLY want the posts coming out of a database by the end of the weekend; even if I don't have an administration area for me to manage them, it would be kick ass if I could move it that far.
Monday, July 6, 2009 - by Tim
I'm developing a content management system for this site so that i can brand it however the hell I want. This is a hard coded post, and a lot of them will be in the next couple of weeks (if i do post, I'm not very good at remembering) and it will serve to motivate me to get my act together sooner so I don't have to write HTML in order to post! (I hope)
The CMS I create is going to be lightweight, easy to deploy in a number of ways, and brandable on both front and backends for anyone that signs up for a recurring donation of an amount to be determined at some time in the future (when I actually have a product worth a donation!)
Notes of interest:
I'm developing the CMS using a number of framework tools. Smarty for templating, ADODB for Database.
The CMS is going to be developed using my Acer Aspire One when I'm on the go, and a Dell Optiplex 320 when I'm at home. It will reside at all times on a Patriot XT 32GB Flash Drive so I can transfer it from place to place.
In the meantime, I'll be writing HTML until I get a backend up!