Closed CharlBest closed 7 months ago
Wow, what a list! Thank for the patches/interest!
Lots of thoughts, typed quickly. Ignore typos please đ. Also moving to discussion vs issue once I figure out GitHub buttons.
A key goal for the projects: keep the template so itâs a quick âfork and goâ. I donât want to add a bunch of setup steps. Itâs a template for capable devs to fork run with, not a one stop shop. Iâm all for things that are easy optional extensions most projects need. Iâm for adding features that are 1) likely to be needed by a wide range of saas apps and arenât too specific, 2) donât increase the mental load of working in the codebase, 3) donât add extra setup steps. Optional steps that give you cool features, that are well isolated and can be ignored, arenât too niche, and are safe from security POV: all for it.
As an example, even though I recommend Cloudflare Pages, I keep the generic adapter so any platform works with zero config.
My general workflow: build cool things on template, and back port when I think they could be useful to a lot of others.
To answer your list:
Later things
Things that seem too niche:
Unsure:
I'm planning on using this starter for one of my projects and there are some things I want to add. Curious to hear if I should encapsulate some of them, that you would be interested in and make a PR(s). Before I do unnecessary work that you don't think fits into this project, here is a rough list I was thinking about.
Daisy UI:
<html data-theme="dark"
)Supabase:
JS/HTML:
navigator.share()
)<meta http-equiv="Content-Security-Policy"
)Additional: