Write, review and publish without leaving Discord.

Gallery flow

Send one finished media proposal

Use Submit content when an image or short video is already ready for the public Gallery. Luminox collects its title, description, accessibility text and optional credit in one guided form.

1. Press Submit content in the Website panel.
2. Complete every required description field and attach one JPG, PNG or MP4 file.
3. Luminox copies the proposal into a private, read-only review thread shared with its author and Website staff.
4. Website staff approve it, request a corrected submission or reject it with a reason.
5. After approval, a Discord administrator runs /website publish inside that review thread. The isolated publisher then validates and sanitizes the entry before it reaches the website.

Gallery files are limited to 10 MB. Links, archives, documents, scripts and unsupported formats are rejected.

Blog process

Use a private thread as the article editor

Write blog post is designed for comfortable long-form writing. The author chooses a category and title first; Luminox then opens a private draft thread where normal Discord messages become the article.

1. Choose Guild news, Events, Community or Roleplay, then enter the article title.
2. Write the article in one or several messages. Blank lines create separate website paragraphs.
3. Attach up to four JPG or PNG images inside the same thread. The combined safe limit is 25 MB.
4. Edit the title, category or your own messages freely while the article remains a draft.
5. Press Submit for review. Luminox captures the current article, locks the thread and prevents further author changes.

The author may discard the entire draft before review. Discord stores the working conversation and original attachments; the Luminox data file stores only the validated publication record and attachment references.

Staff review

Two roles protect Blog publication

A Discord administrator can always review Website content. A non-administrator must hold both one configured global Moderator role and the additional Website staff role selected with /website staff-role.

If changes are requested after publication, the article is hidden first. Only when the secure hide operation succeeds does Luminox unlock the author thread and request a new revision.

Published articles

Keep moderation controls in the original thread

The private thread remains the permanent audit and control point after publication. Authorized Website staff can return to it to edit the live article, hide it temporarily, show it again, request another author revision or remove it from the public Blog.

• Edit article validates the replacement text and securely updates the existing website entry.
• Hide article keeps the article and its images stored but removes it from public Blog results.
• Show article restores a hidden entry without creating a duplicate.
• Delete article removes the public entry and its generated website images after a confirmation step.
• The Discord thread stays locked and archived between actions, preserving who reviewed and changed the publication.

Secure publication

Discord requests an operation; GitHub validates it

Luminox sends an encrypted, fixed-destination request to an isolated GitHub publishing job. Discord users cannot choose a repository path, automation file or publication destination. Blog approval starts publication automatically; Gallery approval remains pending until a Discord administrator runs /website publish in its review thread. An authorized reviewer may safely retry a failed Blog operation from the same thread.

The isolated runner validates every field, downloads only approved Discord CDN attachments, checks their real signatures, strips image metadata, creates bounded WebP files and rejects any unexpected artifact before changing the website data.

Safety

Limited input, private review and no credentials in Discord

• Gallery accepts one JPG, PNG or MP4 file per proposal, up to 10 MB.
• Blog accepts up to four JPG or PNG images, 10 MB each and 25 MB combined.
• Blog text is validated as plain text and rendered with safe DOM text nodes, never executed as HTML or JavaScript.
• Only Discord CDN attachment addresses are accepted; arbitrary external download links are blocked.
• The original filename never becomes a public website path.
• Repository credentials stay outside Discord and are never stored in guild configuration.
• Every live Blog operation targets the article ID generated by Luminox, preventing arbitrary file deletion.
• The publisher rejects extra files, symbolic links, oversized output and invalid image signatures.

Administrator setup

Configure one panel and one specialist role

Creates or updates the Website panel in the selected text channel and stores its public HTTPS address. Re-running it edits the existing panel rather than posting a duplicate.

Assigns the additional specialist role. A non-administrator reviewer needs this role plus any role configured globally through /moderators roles add.

Shows panel health, queue counts, the configured specialist role and whether the isolated publisher is ready without revealing any secret value.

Refreshes the existing panel and performs a new public website availability check.

1. The deployment owner configures the repository connection privately, outside Discord.
2. An administrator configures at least one global Moderator role if moderators will review content.
3. Run /website set, then optionally assign the specialist role with /website staff-role.
4. Run /website overview and confirm that the panel and publisher report Ready.

Discord permissions

Panel channel and private writing threads

• View Channel, Send Messages and Embed Links.
• Read Message History.
• Create Private Threads and Send Messages in Threads.
• Manage Threads so Luminox can add reviewers, reopen author editing, lock review snapshots and archive completed work.
• Manage Messages so the control message can remain pinned and the public panel channel can stay clean.

Private threads contain only the author, eligible Website staff and Luminox. The public panel is edited in place; routine status checks do not repost it or generate unnecessary notifications.