1. A Framework Should Be Custom
Everything should be precise, you don’t need the extra code needed to change, adjust, and extend because everything has been custom written for you and your site.
Every piece of code is written with a purpose, not one line, space, or mark is accidental.
Nothing is repeated and it's packed, stacked, used, and written to use as little code as possible while being as effective as possible.
The best way to build a custom framework is to start at the beginning.
You could start with a tutorial and work through into a guide, and from the guide into a bunch of different layouts and mock ups that you're able to pick and choose elements from.
Once the layout is chosen the code is rendered.
And from this point on you're able to start writing your custom code.
You're adding to a blank template versus all of the current front-end frameworks where you start with every option available to man and to speed up the site or add something they didn’t think of, you have to rewrite or remove code.
And that's even if that particular framework allows you to modify and remove the code because some frameworks don’t.
And some frameworks that do will cause you to rewrite the code you modified every-time they update. This is the reason most people don’t even try to customize their templates. Which leaves a slow, bloated, low-quality, inferior experience.
These front end frameworks come with a hidden tax that’ll put you at a disadvantage and eventually out of business.