Currently in flux, undergoing a major refactor over to SvelteKit and Flatbread. Gridsome lacking maintenance was causing too many headaches and compromises to be made. The next version of the UI is gonna be wild & I'm very excited for it.
So I decided to develop a site to document all the damn teas I drink. How did it come to this? Where did I go wrong? Why am I spending hundreds on tea? Well hey, I'll meet ya in the cart over on white2tea,,,,, hope that thing has digital wheels cuz I wanna kickflip that thing with a transform: rotateX(6rad); and watch all the samples n cakes go flyin
- Gridsome for SSG
- Tailwind 2.0 for UI (frontend dev in progress)
- NetlifyCMS for saying tea words, headlessly
- mmm.. JAMstack for: I spent all my money on tea now I can't afford hosting
Right now we're in what you could consider the alpha.5 state. The CMS is put together and experience tested well (a few updates still to come). The frontend of the site is usable but definitely a stand-in for what's to come. I've been designing a prototype in Adobe XD that's a complete departure from what's currently live, and I'm excited to finish that up and get to coding on it.
After that, I'm going to add in data visualization components, vendor/author pages, and more tea info that exists in the backend but not yet on the front.
Tea wise, I think this project has some neat potential to show the trends of what I like and what terroirs I tend to gravitate towards. I'm also curious about working with some interactive map ideas down the line. With that, I could place context to terroir, displaying geo-tagged teas along with an average characteristics chart for single origin teas of similar vintages.
To keep up with the status, check in to the issues pannel and the projects tab!
npm install --global @gridsome/cli
- clone 'er down
cd puerh.wtfto open the folderyarn installbecause these node modules don't grow on treesgridsome developto start a local dev server athttp://localhost:8080- Put stuff with your little hands
Is eslint telling you to fix a bunch of shit on the end of every line? Then look no further!
This is important to debug and troubleshoot bugs that may not be well documented with Gridsome yet, particularly routing side effects. Otherwise you may be left with something that works perfectly in development but is buggy on deployment.
npm install -g http-servergridsome buildhttp-server dist/and go to one of the live servers it's given you- Clear cache and hard reload
- Hop around