[andrewgos]

Updates the Design System FAQ to reflect where the rollout is now, and adds answers to questions that keep coming up about Bootstrap and theming.

Updated

• Rollout status: tokens and initial components landed in 5.2, and component work continued into 5.3.
• Practical changes in Moodle LMS: now gives real examples (dialogue colours moved to tokens, the Edit mode switch now uses the Switch component), notes the temporary extra variation during migration, and says who owns migrating existing code. The separate "Is MoodleHQ using tokens…" question was folded into this one.

Added

• Where are tokens and components documented? (links to design.moodle.com)
• Why use Moodle-specific classes instead of Bootstrap's?
• Why doesn't the Design System use Bootstrap's variables?
• Why has my custom theme's appearance changed after upgrading?
• How can a theme customise Design System components?

Reorganised

Questions are now grouped: docs link first, then rollout, Bootstrap, theming, and finally scope (App/Workplace).

Notes for reviewers

• Two anchors changed or were removed: #what-practical-changes-… (heading reworded) and #is-moodlehq-using-tokens-… (merged). Nothing in this repo links to either, but links from outside the repo would now land at the top of the page.
• Please check the custom theme answer's advice ("define those variables in your theme before Boost's are loaded") is the guidance we want to give.

Screenshots

[netlify]

✅ Deploy Preview for moodledevdocs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4ded306
🔍 Latest deploy log	https://app.netlify.com/projects/moodledevdocs/deploys/6acdd57e5ac9f5c76e4821b3
😎 Deploy Preview	https://deploy-preview-1722--moodledevdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.