Understanding the developmental cycle of a product

A simple website made to explain how README file + WIREFRAME + GIT branching complement each other in developmental workflow for a digital product.

Image for wireframe article

The purpose of a WIREFRAME

From a product developmental perspective wireframing is essentially a blueprint, an imagie file sent from a client, laying out the structure of a webpage for example, whether it be content placement, naviagation, basic interactions. Then from that skeletal blueprint developers take over and build the product itself.

Read more
Image for README article

Purpose of a README file

Now that you have your website layout, first thing you have to read is the README file. In there you will usually find information about the project, guidelines, requirements, licenses etc. The file acts as an evolving filing overview of the product.

Read more
Image for GIT branch article

Purpose of a branch in GIT

And finally we have branching. As in any collaborative projects, especially if the team is spanning multiple locations, safety - security - support becomes very important. That's where GIT and GITHUB come in. Branching allows you to copy parts of the main code, to work on it independently without accidentally corrupting the main code, and to collaborate effectively on any changes made with your team. Once copy branch has been approved it gets merged into the main code.

Read more