verekia / initializr-website Goto Github PK

Hi, what about moving to bootstrap2 ?
http://twitter.github.com/bootstrap/upgrading.html

Broken link to http://demo.html5boilerplate.com/

https://i.imgur.com/nAMFF0t.png

There are no descriptions of the "Pre-configuration" or "Fine tuning" alternatives, which would be good to have. Especially for newcomers (like myself) would this be a useful feature and it's important to lower the threshold for those not so experienced. The thing that made me notice the absence of such a feature was the choice between "Mobile-first Responsive" and "Twitter Bootstrap" which I could not find answers on easily via Google. I have to say that the difference is not very obvious.

I suggest a small popup next to the cursor when hovering over a feature (or group of features) with a short explanation and a link for further reading. Possibly hovering over a question mark would be a good implementation.

I expect this is an issue with the h5bp site, not the initializr site, so I've cross posted it here:

h5bp/html5-boilerplate#1157

But I figured you might want to know in the meantime.

Polish guide site (http://blog.plainly.co/initializr-polish-guide/) Does not exist any more.
So link shown below can be updated or deleted.

Thanks
Artur

I feel strongly that all the various options offered in the section titled "H5BP Optional" should display some information about each option being discussed (possibly in a tooltip) for newbie developers.

I feel it would be much better if we could tell them what purpose of plugins.js is, for instance. This would also allow them to make more informed decisions and pick up some design patterns in the way. (For instance, they could read a little about Humans.txt and decide for themselves if its cool).

Currently the website lacks support for HTTPS. Without encryption, content on the webpage can be modified or intercepted for malicious purposes. This leaves people open to attacks such as JavaScript injection and tracking. Modern browsers are also deprecating insecure HTTP for newer features, and many page optimizations will not be present. With the dawn of Let's Encrypt, there really is almost no reason to not support HTTPS.