Create different builds of HTML5 Boilerplate? #1625
Conversation
The changes from this commit will make the build script create two different versions of HTML5 Boilerplate, one with the Apache server configurations and one without. The reason behind this change is to allow¹ users to choose if they want the Apache server configs or not, and to move slowly towards providing multiple builds of HTML5 Boilerplate that contain different server configs. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ¹ #1527
alrra
force-pushed
the
multiple_builds
branch
from
d91ac4f to
09f0e38
Compare
|
shipping .htaccess by default sets up a good pattern of delivering performance by default. Every noob that doesn't know better gets to ship this to their hosting environment getting gzip/expires out of the box. I would prefer to ship it by default and create a "naked" distribution without it. |
On the site we can still offer the Apache build by default, but we can also link to the release page where users can download a different build (and hopefully if the future we'll have more than two). |
|
Another possible build option would be one that doesn't have analytics, since there were a number of folks who strongly disagreed with including GA. |
|
What about a builder with options, rather than static builds?
|
Going on that route will end up basically having a site builder or something. I've proposed¹ this due to the fact that server configs are usually harder to deal with then just removing a couple of lines (e.g.: ¹ that doesn't mean we'll necessarily do it |
|
Another idea is to make the yeoman generator more useful. However since it is a command line tool, it won't be that useful for quite a good portion of the users. |
|
Not hugely important, but once this is merged this piece of the docs should be updated.
Definitely. Some just getting started designers or front-end developers might not know anything about servers, and for those people it's better to include all those smart defaults in the
Is this difficult to integrate? If not, we could directly include builds for all other server configs.
+1. Right now we aren't using enough of yeoman' power. |
alrra
changed the title
I don't think so - it's just creating a single archive with naked-fronted template + server configs. Regarding bundling frontend+server in general: To me it depends what users want/would find useful. I think it's important to not take two separate projects which people use, and bundle them together creating something that a few people would use. Sometimes the same person uses both, and other times they are most definitely the concern of different people/roles. |
I gave this some more thought and I think/agree that before embarking on a change like this it would be useful to ask a wider range of people (even the ones that aren't on GitHub) what they use and how they use it. Closing, will open a different issue regarding this after |
|
Why deleted the branch? It is something we discuss later, no? |
@emoju Because for the time being it is not needed, and if for some reason we'll ever need the code, the branch can be easily restored. |
There was a discussion in the first part of the year about removing the
.htaccessfile from the project.I personally think that including some boilerplate server configurations is important, but I do agree that users should have a choice in the matter! So, with this pull request I propose that we slowly move towards providing different builds of HTML5 Boilerplate.
Right now, the changes from this PR will generate two versions:
dist/h5bp(no server configs)dist/h5bp+apache(Apache server configs)and also two archives that we can attache to a release:
But in the near future (after
v5) my hope is that we'll provide also anginxbuild (already talked with @AD7six about it) and so on.Thoughts? (Cc: @h5bp/html5-boilerplate)
Also, any other ideas are welcomed!