Updated Staff Management System docs

[Kevinking500]

Type of PR

• Translation update / creation
• New documentation page
• Content update (not a typo fix)
• Typo / grammar fix

Summary

This PR updates the SMG module documentation to actually represent the module and not make made up information

Checks

• I have verified that my changes do not contain em dashes, smart quotes, or other special characters (the CI lint will catch these).
• If I changed an original (English) file's content or meaning, I have updated all translations of this file.
• If I added a new page, it has correct frontmatter (sidebar_position, title, description).

[cloudflare-workers-and-pages]

Deploying scnx-docs with    Cloudflare Pages

Latest commit:	4c8ef36
Status:	✅  Deploy successful!
Preview URL:	https://192b7ddc.scnx-docs.pages.dev
Branch Preview URL:	https://kevin-staff-management.scnx-docs.pages.dev

View logs

[Kevinking500]

@SCDerox Could you confirm if my method with data storage/usage is fine? It's a big module, so I am committed to the data transparency. I think it doesn't look bloated at all actually when previewing it.
Please lmk :)

[SCDerox]

Thanks for bringing this up, I'll flag it internally and will get back to you within approximately 2 business days. Thank you for your patience!

[Kevinking500]

Huh?

[Kevinking500]

@SCDerox Sorry again, but your last comment was a bit confusing. Could you please confirm if my method is fine? The main reason I am doing it is because every single name (spread across the many models this module has) serves a different purpose for each feature

[Kevinking500]

Guess I don't know. Could you check what might be wrong?

[SCDerox]

Thanks for being so patient today!

The build fails because PR #140 contains this malformed heading in staff-management.md line 638:

  ### Staff Shift {data-usage-shifts}

It should be:

  ### Staff Shift {#data-usage-shifts}

Without a #, MDX treats {data-usage-shifts} as a JavaScript expression.

As a helper, you can find build logs here: https://dingbot.scootkit.com/docs-build

---

Also regarding the formatting of the data used section, please avoid using detail tags so we can render the raw markdown more easily outside the docs themselves (e.g. in files and other plattform surfaces).

[Kevinking500]

Thanks for the bug fix - Though could you explain the last part a bit more, as in like not having those headers with tags, and instead like bolded titles so that the stored data section is 1 name?
If so, I can quickly do that ^^

[Kevinking500]

Ohh wait do you mean the tags themselves and keeping the headers?
Please lmk :)

[Kevinking500]

Oh wait I just realized, do you mean the dropdowns? (

Details

stuff)
If so, should I replace it with a table or just bullet points, lmk what's best

[SCDerox]

Yeah, we replacing with either a table or bullet points would be awesome if possible

[Kevinking500]

Forgot to say it, whoops - I changed them to bullet points and it's ready for review ^^