Origin
Origin êŽë š
â ïž
This post was written 13 years ago!
Personal opinions and technical details may have changed since writing.
Iâve written loads about my flat build process , automation, browser support â in fact, if you follow me on Twitter youâll know I canât shut up about the Web. What Iâve been lacking is a canonical resource for my work beyond theoretical writing and live production examples. Despite web standards being open they arenât always easy to reverse engineer.
What is Origin?
Starting a new project for me used to mean cobbling together and rehashing code from past work. This year I started to consolidate everything into my own personal boilerplate to kick start front-end development.
âOriginâ is my code name for this on-going project (everything needs a name). Itâs not a behemoth of code like Bootstrap or Foundation. Itâs specifically tailored to suit the websites I make. It will never be complete and it will evolve dramatically as my preferences and needs change.
This is not a framework I expect others to use âas isâ but I decided to make it public because:
- A lot of people asked kindly
- I learn from similar projects by other developers
- It will serve as a reference point when discussing particular techniques
If you care to poke around the code is on GitHub (dbushell/dbushell-Origin). Or you can see the GitHub page for my starting pattern library. This doesnât include everything I consider a âbest practiceâ and a lot of things arenât commented. Make of it as you will â just please donât include it in a â10 new resources for developersâ blog post!
If you like the idea of automated builds and need a mature Grunt workflow then give Yeoman a test drive. For a BEM-style CSS framework thereâs Inuit.css (csswizardry/inuit.css). And if you need to prototype something fast, Bootstrap and Foundation have their uses.
