They used to be the same, but I cleaved off peers-template in order to reuse it in other projects (if you look back in the peers-template commit history you can see references to older commits from the website before the split). I also planned for a config that allows someone to drop in their own mfws basic style sheet.
If we decide to return peers-template to within peers-www, I'd still like to keep peers-template so I can keep using it.
They used to be the same, but I cleaved off peers-template in order to reuse it in other projects (if you look back in the peers-template commit history you can see references to older commits from the website before the split). I also planned for a config that allows someone to drop in their own mfws basic style sheet.
If we decide to return peers-template to within peers-www, I'd still like to keep peers-template so I can keep using it.
OK, makes sense. Perhaps a submodule could be useful here, but I think it's simple enough as it is now.
OK, makes sense. Perhaps a [submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules) could be useful here, but I think it's simple enough as it is now.
Would it make sense to import
peers-template
into this repo instead of having 2 distinct repositories?They used to be the same, but I cleaved off peers-template in order to reuse it in other projects (if you look back in the peers-template commit history you can see references to older commits from the website before the split). I also planned for a config that allows someone to drop in their own mfws basic style sheet.
If we decide to return peers-template to within peers-www, I'd still like to keep peers-template so I can keep using it.
OK, makes sense. Perhaps a submodule could be useful here, but I think it's simple enough as it is now.
Mind blown due to huge blind spot of mine in git...