Typical dating patterns
The easiest way to ensure these standards are tracked as part of your project is to pull in North as a Bower dependency.Currently open to review, v0.4.0 is a preview version of North.Once the review period is over, a branch for the current major version will be made.
Much like visual design, the process of developing a product has changed as the understanding of the medium being worked in has changed from an extension of print design to its own entity.
Whereas in print design a final product was always the deliverable and designs for that product would be handed from one role to another without back and forth communication, the web requires a new process better suited for the complex and interactive nature of the final product.
Often referred to as , the old method of a static page being created by a designer, approved by a product owner, and then handed off to developers without further communication does not produce results in the best interests of anyone involved.
The product owner doesn't see the final product until it is all finished and ready for launch, much too late to make any significant corrections or alter the path of the project.
Align and Guide Your Project North is a set of standards and best practices for developing modern web based properties.
Included are standards and best practices for all aspects of a project, from kick off through development.
North encourages an agile, content-first, approach to product development and a mobile-first, in-browser, system based approach to design and development. Standards and best practices change, and as they do and have been vetted, North will grow and change with them.
North is versioned using SEMVER in order to provide a way to specify what version of North is being followed for any given project.
Instead, a more process, where product owners, designers, and developers all work in conjunction with one another to build value in a product throughout its development cycle, is needed.
One where a small amount of work and constant feedback between all parties can build a large project out of small parts.
One where the final project may not have every bell and whistle hoped for, but rather has an array of features that fulfill the maximum potential of the cost of development based on business and user needs.