close
Current Availablity:
Taking on projects.
If you're interested in hiring me for a project, Contact me for more info.
When I released the Whitespace template a few weeks ago, it was admittedly bare-bones. There wasn't much to either the design or the functionality of the template. I was okay with that. I'm a big fan of the Release Early/Release Often way of developing. I set a deadline for myself to get done what I could and released the result of that.
After some feedback (the whole point of the 'Release Early/Release Often' method) I've come up with a list of things I'd like to see in the v2.0 of the Whitespace template. Here's my list:
- Integrate a Dropdown menu for the main menu (this will likely be CSS-based for speed)
- Make a few overrides, such as com_weblinks, com_content, etc.
- Add an offline.php page
- Add a component.php page
- Add an error.php page
- Add a few best-practice bits that I missed the first go-round
Bookmark
Email This
Comments
(4)
Subscribe to this comment's feed
I actually think bare bones is a good thing. There is a distinct lack of good starter templates out there, meaning templates that a designer/developer can take and easily customize. Your list is a good set of features just to make sure that all the bases are covered, but beyond that there's not much I would do to it. Less is more. :)
Thanks for the suggestion, Cory. I completely agree that 'less is more', especially when it comes to design. I actually got a few ideas (offline.php, component.php, error.php) from your book the other day! I don't see those files in many pro templates out there, so perhaps I'll be starting a new best-practice :)
TrackBack URI for this entry
