ToneCustoms — Community Publishing Guide

Use this guide to publish announcements and developer insights directly in GitHub without needing another website service.

Quick publishing form (recommended)

1. Open Publish ToneCustoms Community Post.
2. Select Run workflow on the main branch.
3. Choose announcement or insight, enter the title, matching category/status, message and optional official HTTPS link.
4. Select Run workflow to submit. The workflow validates the content, updates the correct page and commits the post to main.
5. The existing website deployment workflow should run on that Markdown commit. Check its green status and the published page.

Only collaborators with workflow-dispatch permission can publish this way. The first actual submission has not yet been verified. A failed workflow does not publish the post; review the run logs for the validation error.

Post an announcement

1. Open ANNOUNCEMENTS.md in the public docs repository.
2. Click the GitHub edit pencil (or create a pull request if review is required).
3. Add a dated row at the top of the Latest Announcements table.
4. Add a detailed dated section if needed; include accurate dates, official links and any eligibility rules.
5. Commit to main. The existing documentation deployment workflow is configured to publish Markdown changes after its checks pass.
6. Confirm the new post appears on the Announcements page.

Post a developer insight

1. Open INSIGHTS.md.
2. Add the new dated post under Insights feed, newest first.
3. Use the format below and remove the “No developer insight posts” placeholder after the first post.
4. Commit and check the live Insights page.

### YYYY-MM-DD — Post title

**Status:** Concept / In development / Preview / Released

**Inside the build:** What the team is working on or exploring.

**Why it matters:** The gameplay or community benefit.

**Community question:** What feedback would be useful?

**Links:** [Relevant public demo or guide](https://example.com)

Publishing rules

• Confirm the post is approved and accurate before publishing.
• Do not invent script versions, release dates, giveaways, special membership perks or partnerships.
• For a giveaway, publish the actual eligibility, entry method, end date, selection process and platform rules before accepting entries.
• Use Announcements for official releases and notices; use Insights for previews and behind-the-scenes notes.
• Link to Discord for community conversation and to GitHub feature requests for structured ideas.
• Never post credentials, paid source code, private customer records or confidential business terms.

Capabilities: These pages are public and editable by authorized GitHub repository contributors. They do not automatically cross-post to Discord, enable GitHub Discussions, or create member-only access.