Frequently Asked Question

A Template represents all the graphic elements of the arrangement of the columns, going through the choice of colors to establishing the structure of the various elements surrounding a website, apart from its content.

Today the majority of website builders use a predefined Template, to avoid worrying about graphic dimensions and focus more on everything that is content on the site

Bootstrap only defines visual components (like buttons) and non-visual components (like grids). By aggregating these components, you can build a template.

We'd like to, but no. It would be a lot easier not to use any custom class, but let's face it : this is nearly impossible. There's often a detail that require a class that Bootstrap did not (yet) defined.

So the goal of this template is to use the standard Bootstrap classes as much as possible.

When this is not possible, the template relies on the custom utility API, and in last resort, some semantic classes (like .admin, .site etc) to reach the desired design.

Custom classes are defined under the sass/ folder.

It would be better if you already know CSS, HTML, and JavaScript.

Javascript is really sprinkled in this project, but all pages are build thanks to GulpJS, which require some knownledge about the NodeJS ecosystem - but all is made to make this tool begginer friendly.

Yes ! The page you are currently viewing is the "FAQ" part of the template.

There also a page that explain more precisely where to click, in order to take full advantage of the template.

Yes ! Go to the GitHub project, and read the CONTRIBUTING.md files.

We are welcoming any new PR or issues. If you want a new design or a new page, it is also possible.

You can try SB admin 2, which is more focused on the admin part.

In the free and open-source space, I'm not aware of many projects like this one, but feel free to contact me if you want your project to be referenced here.

There are no "docs". You can read the README of the GitHub project to see how to install and customize it.

The most simple way to understand this project is to read the source code.

Note that this is only a "frontend" project : there are no backend like Django, Rails or Laravel. All the authentication screen are purely "fake" screen : nothing is read from the user inputs.

Therefore, the code itself should be quite easy to follow and understand (I hope). There are no algorithms.

However, if something is not clear, feel free to reach me, or submit an issue on GitHub, I will try to document it somewhere.

Simply copy/paste the sass/ folder, located at the root of the GitHub project.

You have then to include these SCSS file into your own build tool, and copy/paste the HTML of this demo to get the same pages on your project.

Normally this is a job for the designer.

However you can take inspiration from other pages to try to make it yourself.

You can also try to submit a PR on the GitHub project, we'll see if we can make it.