Use Bower package manager for most front-end libraries
(JS, CSS, images, etc.). Configure its directory
option to point to appropriate folder.
Use Gulp to process your assets. You can compile CSS and JS, optimize code, add browser prefixes to CSS, lint, compress and organize files, etc. You can also create Gulp task to run local web server. See gulp-connect-php as an example.
Contacts Forms:
Frameworks
Graphcs:
Tours:
Pick a set of conventions for all your class names. Keep number of rules to minimum. Some ideas:
- use short prefix, ex. acronym of the company
- use 2-3 words
-buttonsuffix for buttons, ex.close-button-inputsuffix for inputs, ex.name-input-headingforh1-h6, ex.large-headingwebsite-suffix for header and footer, ex:website-logo-containersuffix for reusable elements, ex:news-container- single adjective for boolean properties, ex:
active -stylesuffix for style variations, ex:green-style
Show element hierarchy in class names. For example, use the same prefix message- for all ements
in a container:
<div class="message-container warning-style">
<h1 class="message-heading">Sorry...</h1>
<p class="message-body">This product is no longer available.</p>
</div>Frameworks:
Libraries:
Linux:
- Set server to UTC timezone.
- Synchronising time:
sudo apt-get install ntp; ntpdate -s ntp.ubuntu.com; - Set MTU to 1500 (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html)
Hosting:
- aws.amazon.com
- godaddy.com
- rackspace.com
- digitalocean.com $60 / year
- namecheap.com $210 / year
Domain:
- domains.google.com
SSL:
- letsencrypt.org