At present the @dwyl mission statement is in multiple places and the one in HQ:
https://github.com/dwyl/hq#mission-statement
is out of sync with the recently updated dwyl/start-here#191 >> [/start-here/mission.md](https://github.com/dwyl/start-here/blob/931fb1bf29ee821b62f05ffc

Right now we don't have any rules in place for how to write and format our feature files.

We've already decided that we don't want the name of the files to represent the feature text in ui-core, but apart from that, there has been no other decision made and it'd be nice to have a consistent style across repositories

Current inconsistencies

Steps are written from different perspec

Clean up some of the default pages and language in Sails, for example to contact form to make it more project focussed and a clean slate on which to build.

As @Bachibouzouk pointed out: Information regarding OEP-metadata is scattered across this organisation. We need to clean this up and here is my proposal:

OMI would be a good place for metadata in general (I think we had a recent discussion regarding that!?). BUT: Specification, documentation and implementation are three different t