-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename nextjs #34
Comments
The first things to pop into my mind were |
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). thunderstore-io/Thunderstore#195 is related though so we could follow some kind of convention for the few services we do have |
I'd intuitively call it |
I think |
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 |
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?The text was updated successfully, but these errors were encountered: