CMS vs JavaScript framework

The fashion is no longer for using CMS, but for a framework like Bootstrap.

This trend on new portal sites is confirmed in Google Trends. Search for the word CMS (Content Management System) is falling, while BootStrap is experiencing a sudden increase in 2012 and there is no doubt that this is due to the framework launched by Twitter.

But if webmasters switch to HTML frameworks 5 at the expense of CMS, then what can this be connected with? An attempt to explain: the increase in the audience of mobile and tablet PCs due to the PC, since CMS remains quite heavy and slow, and by the time of loading, is no longer really suitable for a mobile browser.
On the contrary, BootStrap since version 2, like other HTML 5 "boilerplates," takes into account the reduced screen of mobile devices and provides fast page loading.

We will compare the benefits of both ways of creating a site. This, of course, applies only to simple sites for presenting a product or blog, and not those whose pages use a lot of information taken from the database .

General purpose of code reuse

CMS and the presentation framework share the same goal - to offload the webmaster from page presentation tasks so that it can focus on content. They also have the advantage of offering a similar user interface on all sites.

Making a site with BootStrap is more difficult, but the main thing is there: JavaScript code (based on jQuery) and CSS were tested on most PC OS and mobile devices, which the webmaster no longer has to do.

Both systems offer plugins that aid in navigation or presentation. BootStrap plugins focus more on wigdets, which can also be provided by Wordpress themes, but you can hardly find a theme with all the widgets you want.

CMS blogs: perfect design

The basic design of CMS blogs has actually always been insufficient. To do this, you need to place the content of the site in the database, and then create a page from an SQL query. Then, when we see that it is too slow, we add a cache plugin that creates a static HTML file for each page.

My PHP pages are organized as follows:

<?php include("top.php");?>
<p>Contenu de l'article</p>
<?php include("bottom.php");?>

Headers and footers and dynamic content are included in every page that actually contains only its own content, equivalent to what Wordpress puts in the ticket table, the POST table.

Why put content in a database and then copy it to a file on your local system, rather than storing it directly in an HTML container?
The presence of a database does not even give us a search function, since this requires an explicit list of tags. In fact, you get a real search tool by including the Google search box, which also works well on a static site.

To ensure access to mobile networks, it is necessary to revise the way CMS is developed for modern sites. A mixed, static or dynamic design can be considered depending on the data transfer rate, which can be estimated using WebSocket or WebRTC technology.

Don't neglect SEO

Wordpress became a liability for site positioning. The softness of tag clouds stuffed with internal links, a blogroll that turns a site into a link farm, and not always optimized themes added to the fact that load times have become a positioning criterion and, in addition, all pages return HTTP redirect code, make this CMS (like others), can harm site traffic if the code is not perfectly studied by the webmaster. But the goal of CMS is to rid you of the code...

Trend: Return of static sites

While users want to limit themselves to blogging without touching lines of code, they seem to prefer to use CMS like Wordpress. But that now competes with social sites that are blogging platforms, too: Facebook and Google +, or even GitHub, offering a page generator (for free).

If webmasters want to create a high-performance and optimized site for desktop and mobile PCs, they prefer to use a CSS framework, the code of which can be overloaded to customize the appearance. It seems that now there is a trend towards creating static sites based on these frameworks.

BootStrap, originally created for Twitter, supports part of CSS, offers several examples of personalization. This is a framework, among other things, for other templates, see the CSS section.