My bad, probably didn't articulate that too clearly. let's say feature X is some sort of blog functionality, it'll break down something like this
components/blog/Hero.html, components/blog/InfoBox.html, components/blog/Article.html, component/blog/IndexCard.html, components/Footer.html(not in /blog since it's the same everywhere across the site)
Since I am using svelte nowadays, templates are found in routes/ so I'll have something like /routes/blog/index.html and /routes/blog/[slug].html.
in lib/ probably something like lib/communicationService.js which is generic. lib/blogService.js might have methods .getLatest() or .report(blogId, user, reason)
My bad, probably didn't articulate that too clearly. let's say feature X is some sort of blog functionality, it'll break down something like this
components/blog/Hero.html
,components/blog/InfoBox.html
,components/blog/Article.html
,component/blog/IndexCard.html
,components/Footer.html
(not in/blog
since it's the same everywhere across the site)Since I am using svelte nowadays, templates are found in
routes/
so I'll have something like/routes/blog/index.html
and/routes/blog/[slug].html
.in
lib/
probably something likelib/communicationService.js
which is generic.lib/blogService.js
might have methods.getLatest()
or.report(blogId, user, reason)
Ah I follow you now! Yea that is a pretty similar approach to how I approach it. Thanks for the insight!