Preliminary planning and preparation work is necessary for project propulsion. Let's lay the "groundwork" by looking at what is needed before you build your next Brutalist Framework project.
Let's first take a quick 'n raw look at BF...
Brutalist Framework was built with an application-first design approach. As the web experience has become primarily mobile, it makes sense to design websites to look and feel more like a mobile application. The design approach process is dualistic: it is both deconstructive and constructive.
▚\◡\◢\◭\╔\◪\◧\◝\▗
Break down overall concepts and ideas into dislocated, raw elements and components.
The idea is to challenge the current or conventional design (if one exists), and explore the possibilities of what it could become.
Assemble, consolidate, and build components into a creative end product that we're happy with.
The goal is to actively build a solution that progresses a concept to evolve based on pre-esisting data or experiences.
NOTE: An e-book is coming soon, which will explain this in greater detail.
Planning your next website or application project will involve various aspects. Thorough project planning should include:
Consider these free e-books to help you get started:
If you have opted to use BF to build your next project, consider whether it will be static or dynamic:
Depending on whether you're building a static or dynamic page, a couple boilerplate files are included in the root directory of BF as starting points for your next project.
Use the boilerplate.html template for static projects, or use the php_boilerplate.php template for dynamic ones.
Once your website or app has been built, a few things will need to be taken into consideration post-launch:
To leverage new features in future versions of BF, keeping the CORE files up-to-date will be necessary. To update, simply replace all files within the /bos directory with those found in the latest version. Eventually, there will be an upgrade script that will automate this process.