12 Commits

Author	SHA1	Message	Date
Simon	fb07c3d0c5	feat: Add fingerprint on js	2020-11-26 16:00:27 +01:00
Simon	ef696aae40	feat: Remove markdown from title	2020-11-25 17:20:05 +01:00
Simon	7fd66503cb	feat: Remove markdown from title	2020-11-24 14:10:52 +01:00
Simon	37aa370ae0	feat: Add main.js by default	2020-09-09 12:15:40 +02:00
Simon	371b954e21	feat: Add debug mode	2020-09-09 12:15:15 +02:00
Simon	d740c03ae5	feat: Add js layout	2020-05-07 22:04:25 +02:00
Simon	f90a8bfa6c	feat: Add title on header	2020-03-26 17:56:57 +01:00
Simon	8da32f8afd	fix: Avoid http-equiv <meta> tags ... HTTP headers are more efficient than the http-equiv meta tags. The <meta http-equiv=/> tags The http-equiv meta tags allow to communicate to the web browser information equivalent to the ones of HTTP headers. For example, the meta <meta http-equiv=content-type/> will have the same consequences than the HTTP Content-Type header. Two points don’t stimulate the use of http-equiv meta tags: Going through the meta requires to interpret the beginning of the HTML page, which is slower than going through the HTTP headers in terms of performance If the HTTP header is already present, the meta is ignored In which cases are the <meta http-equiv=/> useful? Only one case can justify the presence of these meta tags: if you don’t have access to the configuration of your server, and that is to say to the HTTP headers. However, we advice you to use a configurable server so that you can establish the most efficient site possible. This page contains 1 http-equiv meta tag. If possible, you should replace it: x-ua-compatible	2020-03-11 16:53:07 +01:00
Simon	0a71e48957	Add language	2020-03-09 15:08:09 +01:00
Simon	c78f0f5f46	Fix style	2020-02-27 11:39:57 +01:00
Simon	ca2764655a	first version	2020-02-26 23:44:15 +01:00
Simon	8f7d784ed2	first commit	2020-02-26 23:13:24 +01:00