I’m working the excellent HTML5 Boilerplate into our EE installs, having used it on a few non-EE sites and been very impressed with it. Just wondering if any of you guys have any experience with it, or any insight into how the standard setup might affect EE, particularly the .htaccess, (too long to post, but attached to this post and available on the homepage here if you scroll down).
The last thing I want to do is significantly increase dev time by introducing a whole heap of stuff behind the scenes that doesn’t play nicely with EE!
A couple of things in particular:
I think this would be the correct way to set up the .htaccess to strip index.php, but not 100% sure:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond $1 !^(images|css|js|themes|uploads|favicon\.ico|robots\.txt|index\.php|backend) [NC]
RewriteRule ^(.*)$ /index.php?/$1 [L]
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^(.*)$ http://%1/$1 [R=301,L]
</IfModule>
There is pretty extensive cache control in the boilerplate, but I guess this will cause problems unless EE’s caching is disabled?
Best to remove -MultiViews?
# without -MultiViews, Apache will give a 404 for a rewrite if a folder of the same name does not exist
# e.g. /blog/hello : webmasterworld.com/apache/3808792.htm
Options -MultiViews
# -Indexes will have Apache block users from browsing folders without a default document
# Options -IndexesAssume gzipping resources isn’t an issue.
There is also provision for a custom 404 page - EE handles 404’s just fine so I’m removing this:
# custom 404 page
ErrorDocument 404 /404.htmlOne last thing concerns their crossdomain.xml - again, I can’t see any issues immediately but there might be something EE is doing already on that front?
Any ideas or experience on this already? There doesn’t seem to be very much discussion on the forums or elsewhere, surprisingly.