Editing a Guide
There are two ways to make an edit: right in your browser (easiest, great for small changes), or locally on your computer (better for writing a whole guide with live preview). Both end the same way — a pull request that gets reviewed before going live.
Best for typos, wording, and small fixes — no software to install.
-
Open the guide you want to change on TCGT.Help and note its title.
-
In the GitHub repository, find the matching file under
src/content/docs/…(for example, the IMB Tracking page issrc/content/docs/printing-shipping/imb-tracking.mdx). -
Click the pencil icon (Edit this file) in the top-right of the file view.
-
Make your changes in the editor. Everything is written in Markdown — see the Style Guide for the basics.
-
Click Commit changes, choose “Create a new branch and start a pull request,” and describe what you changed. That’s it — a maintainer takes it from there.
Best for writing a full guide, because you can preview it live as you type.
-
Install GitHub Desktop and clone the TCGT.Help repository to your machine.
-
Install Node.js (LTS), then in the project folder run
npm installonce, followed bynpm run dev. Openhttp://localhost:4321to preview the site live. -
Edit or add files under
src/content/docs/…. The browser refreshes as you save. -
In GitHub Desktop, write a short summary, click Commit to main, then Push origin, and finally Create Pull Request.
Adding a brand-new guide
Section titled “Adding a brand-new guide”To replace a “Coming soon” page, just open its file and swap the placeholder for
your content. To add a page that doesn’t exist yet, create a new .mdx file in
the right category folder with this at the top:
---title: Your Guide Titledescription: One sentence describing the guide.---
Your content starts here.After you submit
Section titled “After you submit”A maintainer reviews every pull request before it goes live, so don’t stress about getting it perfect — that’s what review is for. Once it’s approved and merged, your guide publishes to TCGT.Help automatically.