Because today was the deadline, I really wanted to at least have some code for you guys to look at, so I sat down, popped some fresh batteries into the keyboard, and opened up the text editor.
Since I'm posting code, I decided to also address the current state of this project, and the future state as well. So time to write up one of those fancy things.... Roadmaps...
J!Kids Roadmap
Phase 1
This is the phase J! Kids is currently in. The main functionality is still being coded. Much of the code still needs cleanup and bug removal. There are two versions currently available, a simplistic backend used when kids manage and publish content to the site with little adult supervision, and a complex and completely customizable frontend with a CPanel and simulated backend used when a site is run with a lot of adult supervision.
The features of the backend template are a highly simplistic CPanel with only six links, and large fonts with bright vibrant colors.
The frontend carries the same backend interface, but with the added customization of PHP conditionals paired with Joomla's built in template parameters for easy modifications with little code editing. Along with that, the frontend template uses cookies to store CPanel sessions, to allow a person to add a post, go back to the main site, and instead of seeing the normal page, they would resume their CPanel session as though nothing happened. The CPanel is displayed instantaneously because it is loaded in the background IF the user has permission to do so (modifyable in template parameters). The template uses template overrides to modify the content posting interface and supplies a table-less layout for the site.
Phase 1.5
Phase 1.5 is a small step, which is the simple process of brainstorming tasks and other additions to make to the J!Kids suite along with the two templates, the TinyMCE mod, and the language pack.
Phase 2
Phase two uses the backbone of code built in phase one, and cleans it up, makes it more aesthetically and artistically better. Phase two also incorporates the submission of code for the project using GHOP tasks such as icon creation, and other people's contributions. Phase two combines multiple parts into a whole.
Phase 3
Phase three is the final phase for the first full release out of beta, or production status. This is the time for further bug fixes, documentation, cleanup of code, W3C validation, and the important things needed before final release. The themes compliance with IE6's *cough* quirks shall also be implemented here. So far, the theme works in IE6 except for the PNG icons and the images which shall be converted to GIF.
Ok... Now I got that done with

Now, without further ado, here's the code! It doesn't look great, and it really isn't supposed to at the moment

Cya, thanks for any advice, and have a happy holiday, no matter what religion you are - a day off is always welcome

-Shantanu
P.S. Btw, I kinda assumed it'd be ok to go past the deadline... Umm sorry about that. I guess I just made a lot more out of this task than I ever thought I would, but it definately seems like something to maintain and continue to code for.