Learning to cook at home with Parsnip - built entirely with Svelte!

1

Flamelink.io

We've gone with Firebase for our "backend" needs. This is primarily just firestore for data, cloud-functions for database sanitization, auth, and basic usability analytics. We're using it in conjunction with a CMS service called Flamelink that allows the non-technical folks on our team to add content to firebase in reasonably intuitive way without us needing to build/maintain a second app just for content-management (we're a super small team!). Definitely, some pain points here and we're exploring alternatives in the future, but it's been helpful for bootstrapping. We've also run into some issues around pre-rendering (e.g. Routify's equivalent to sapper export) with Firebase so we're holding off on pre-rendering right now.

#CMS #Blogging #JavaScript 5 social mentions

2

Tailwind CSS

We've opted for TailwindCSS for all our styles, which is super helpful when working with a design team since we can export custom defaults and classes to our tailwind.config.js as a "source-of-truth" for the app while individual components can manage their own tweaked styles.

#Developer Tools #Design Tools #Website Design 867 social mentions