Wardrobe: What do we have?
Ashley Clarke • January 4, 2019wardrobe
Although we are going to build the next version of wardrobe from scratch it's worth looking at what we have inherited from the wardrobe project to see if there is anything we want to keep.
Looking at the github organisation we have 6 repositories, lets take a look at those:
This is the main blogging application built with laravel 4.
This repository contains the main functionality for wardrobe. (It's a composer dependency). This is essentially how I was planning on building the platform (as a package) so that it can be installed into an existing laravel application, or we could create the entire application (probably through some installer we can build).
It looks like this project has translations for the UI in 17 different languages. This is great, however as we are building a new project we may need items that we don't have translations for, this is not the end of the world as laravel will fall back to the english version, but its worth being aware of. The current setup requires the user to copy the language files into their project, I think it would be better to turn this into a composer package and include by default.
The documentation in markdown (presumably for v1).
This is a 2nd version being built with laravel 5. It has only 3 commits. I will delete this repository and use branches on the wardrobe repository instead.
This appears to be the main code for v2 which has a lot more commits than the "v2" repository. This is essentially what "core" is to "wardrobe"
The "wardrobe" & "v2" repositories don't contain all that much code, "wardrobe" has a bit more which I will take a quick look over. I will also have a browse over the "core" and "cabinet" repositories to see if there is anything to be learned from the existing code base before we start from scratch.