Metadata project moving into development stage, opens Github repo

Metadata had a productive meeting today.

The MV* style architecture I suggested in the pseudo-code I shared in the last post was discussed, and everyone seems on board. Will write more on this in full later.

We’re moving our development to a Github repo, where anyone can open up an issue to voice concerns of any flavor. I’ve imported the pseudo-code sample as a base to continue development.

Most architectural planning discussion will happen in issues, and will be turned into verbose (and I mean verbose) documentation within the repo. I’d like all our software architectural decisions/reasoning, project background, and anything else relevant to be documented. Maybe even consider a documentation first approach to development.

The project is going to be in permanent alpha until further notice (i.e. use this on a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing. at your own risk, no promises re: backwards compat., etc.).