I've been thinking once we finish up with #62, we should migrate this repo into the main Fontsource monorepo under a new /website folder.
The main benefit I see is simply more exposure to our developer community which could lead to more issues being highlighted and possibly more pull requests being contributed. The website then becomes a more 'active' element of the Fontsource project. Other than that, it's mainly just housekeeping and organisation following monorepo fashion.
Things to do to make the change:
[ ] Re-organise all the issue labels in the main repo to be more distinguishable for which platform is being addressed e.g. Platform: Website.
[ ] Move over the repo
[ ] Setup Vercel accordingly
Changes made to the website on the main repo will then always have to be facilitated with pull requests and reviews rather than committing to master like this repository though.
I've been thinking once we finish up with #62, we should migrate this repo into the main Fontsource monorepo under a new
/websitefolder.The main benefit I see is simply more exposure to our developer community which could lead to more issues being highlighted and possibly more pull requests being contributed. The website then becomes a more 'active' element of the Fontsource project. Other than that, it's mainly just housekeeping and organisation following monorepo fashion.
Things to do to make the change:
Changes made to the website on the main repo will then always have to be facilitated with pull requests and reviews rather than committing to master like this repository though.