You've already forked AstralRinth
forked from didirus/AstralRinth
9c176013ab
* Begin Work * WIP * WIP * WIP * Use error notification keys * Finish & fix error * Fix lint error * Normalize message IDs (#9) It makes sense to compose message IDs in order: - Place (page, sub page / "modal") - Thing - (optionally) Relation to the thing For example, a label for a password field would be: - auth.sign-in (on sign-in subpage of auth) - password (password field) - label (is a label for the field) Another example - button to sign in: - auth.sign-in - action (this is an action to do something) - sign-in (action to sign in) This helps keep the IDs closer to the actual structure of the page, oftentimes smaller in the code, and easier to understand by translators. --------- Co-authored-by: Sasha Sorokin <10401817+brawaru@users.noreply.github.com> Co-authored-by: Prospector <6166773+Prospector@users.noreply.github.com>
Modrinth's center for its frontend service
For contributing information, please see the knossos section of the Modrinth contributing guide.
For a detailed explanation on how things work in general, check out the Nuxt.js docs.