Open nihaals opened 3 years ago
Maybe something creative?
The first things to pop into my mind were www
and site
. How's that for creative!?
I don't think it needs to be something that sets a theme or something (like some companies name all their services relating to food) since we're unlikely to need a huge set of micro-services (at least any time soon). https://github.com/thunderstore-io/Thunderstore/pull/195 is related though so we could follow some kind of convention for the few services we do have
I'd intuitively call it website
, and have probably already called it that in some conversations on Discord
I think website
it still a bit ambiguous, especially if we're talking generally about Thunderstore. You'd probably end up not using the name and calling it something like "the Next.js frontend"
so let's call it nextjs frontend then, eh? 😄
If we need more descriptive names, we can always rename. For now that should be pretty clear what it's referring to
I think if we call it exactly nextjs-frontend
this works well and is explicit
It would be nice to have an explicit name to use when referring to the
nextjs
project. I think the shared components are already fairly clear but referring toNextJS
might be ambiguous, especially for new contributors. An example of a place this would be used is CI logs. Maybe something creative?