Modulaise tools suite
The purpose of the Modulaise tools suite is to assist you in developing quality HTML-frontend code for complex scalable websites.
Table of Contents
What does it do?
Best practices approach to developing front end code
Using the Modulaise tools suite, you will be creating front end code that adheres to the Web Performance Best Practices rules, as outlined by Google.
With an easy to understand modular anatomy, you will be constructing your first site in minutes.
Reusability of code
Using a flexible yet plain and simple module anatomy allows for a greater degree of code reusability.
Maintainable frontend code
By encouraging you to seperate your code into modules, finding and debugging that troublesome codes becomes easier.
Coding by convention
Using a well structured agreed upon project structure, makes it easier for teams to collaborate, since there is never any doubt about where certain files lives.
Easy build and deploy cycles
With a strong emphasis on build cycles, the Modulaise tools suite allows you to build and deploy your frontend quickly and continually, thus empowering you to release early and release often.
Empowering you to not repeat yourself
Using a simplified template system, and page / pane / module analogy, you are encouraged to not repeat yourself while coding.
Easing iterative development
Easing building, deploying and refactoring truly enables you to develop iteratively.
What is it not?
It is not a new programming language
It is not a content management system
It does not require you to be an elite PHP programmer
At most you will be utilizing 5 - 10 PHP function calls, all of which are documented and easy to grasp.
It is not a CSS framwork
You are absolutely free to pick or omit any CSS framework.
Where to go now?
Latest documentation is available online at the GitHub - Modulaise Wiki.
Here you can find the installation instructions, and a handy tutorial. The installation and tutorial will take you approximately one hour to complete.
Feedback and suggestions
Otherwise feel free to fork the project. ;o)
20101230, Lars Jensen
Created the readme file
2011013, Lars Jensen
Updated the readme file.
2011020, Lars Jensen
Included table of contents, and hints for tutorial.
"Seperation of concerns"
"Release early, release often"
"Iterative and incremental development"
"GitHub - Modulaise"
"Create an issue for Modulaise"
"Web Performance Best Practices"