0
All this planning and development has a definite goal in mind: to get a fully working version of this mod up on this site for both my own purposes, and as a flagship product to sell to interested parties. To that end, I've tried to keep development moving along by coding distinct parts of the mod and making incremental versions ready for testing. Getting 0.2.0 is taking some time as I change some things behind the scenes, but I think it will be worth it.
When we finally get to v1.0, the Core itself should be a very polished product ready to be used. It won't have a lot of real productive benefit to you at that stage (it will take development of the plugins to really get this going), but it will help a great deal in just managing clients. Anyone who's had to answer one of my "can you send me your site info?" PMs for the bazillionth time will appreciate that.
To get to this goal, I think it's important that I start planning out some definite milestones for the various, I'll call them, sub-major versions of the product. Version 0.1.0 was the very first version I put up, and it was very basic, just the content blocks and a basic box in the middle, but a lot of the ACP side too. I did a couple fairly significant additions prior to v0.2.0 (announcement management, some preliminary profile work), but v0.2.0 is going to be a pretty sizeable milestone. I'll use this post to try and keep track of my goals for the big milestones upcoming. After each of these sub-major versions, there will likely be several minor versions as well, for bugfixes.
So here are my planned features for the milestones:
Version 0.2.0
Member List
Language files split per-class
Version 0.3.0
Profile tabs
Classifications
Version 0.4.0
Full profile management
Version 0.5.0
Management of default block layout
Version 0.6.0
Work on Stats content block (plugins will expand on how this works)
Version 0.7.0
Custom content blocks (maybe)
Work on getting code reviews
Version 0.8.0
Portal plugin
Look for things that should have settings
Version 0.9.0
Profile Tab (is this needed?)
Look for things that need permissions
Version 1.0.0
Ensure all text is in language files
Ensure all HTML is in skin templates
Move as much CSS in the templates as possible into stylesheet
Validate proper usage of all settings/permissions
Code security checks
Does this look like a good roadmap? Any questions, suggestions?
When we finally get to v1.0, the Core itself should be a very polished product ready to be used. It won't have a lot of real productive benefit to you at that stage (it will take development of the plugins to really get this going), but it will help a great deal in just managing clients. Anyone who's had to answer one of my "can you send me your site info?" PMs for the bazillionth time will appreciate that.
To get to this goal, I think it's important that I start planning out some definite milestones for the various, I'll call them, sub-major versions of the product. Version 0.1.0 was the very first version I put up, and it was very basic, just the content blocks and a basic box in the middle, but a lot of the ACP side too. I did a couple fairly significant additions prior to v0.2.0 (announcement management, some preliminary profile work), but v0.2.0 is going to be a pretty sizeable milestone. I'll use this post to try and keep track of my goals for the big milestones upcoming. After each of these sub-major versions, there will likely be several minor versions as well, for bugfixes.
So here are my planned features for the milestones:
Version 0.2.0
Member List
Language files split per-class
Version 0.3.0
Profile tabs
Classifications
Version 0.4.0
Full profile management
Version 0.5.0
Management of default block layout
Version 0.6.0
Work on Stats content block (plugins will expand on how this works)
Version 0.7.0
Custom content blocks (maybe)
Work on getting code reviews
Version 0.8.0
Portal plugin
Look for things that should have settings
Version 0.9.0
Profile Tab (is this needed?)
Look for things that need permissions
Version 1.0.0
Ensure all text is in language files
Ensure all HTML is in skin templates
Move as much CSS in the templates as possible into stylesheet
Validate proper usage of all settings/permissions
Code security checks
Does this look like a good roadmap? Any questions, suggestions?
