Anime fans do three things that general social networks handle poorly. They talk about an episode in the hours after it airs, they try very hard not to be told what happens before they have watched it, and they share fan art that deserves better than a feed that scrolls it away in a day. A fan site built for those three habits looks different from a generic forum.
This guide uses Jetonomy for structured discussion, MediaVerse for galleries and BuddyNext for profiles and the social layer, with the Reign theme providing the design. Spoilers get a section of their own, because the honest answer about what the software can do is shorter than most people expect.
Decide your spoiler policy before you build anything
The strongest spoiler protection is a rule that members understand, supported by a layout that makes the rule easy to follow. Software helps with the second part. Write the policy in plain sentences first, and then configure the site to match it. A usable policy answers four questions:
- What counts as a spoiler? Plot events, character fates and ending details are the obvious ones. Decide whether art that shows a late-season character counts.
- How long after airing is an episode safe to discuss openly? Pick a window, such as a week, and apply it to everyone.
- Where do spoilers go? A separate space, or inside the topic for that episode only.
- What happens when someone breaks the rule? A reminder, then a warning, then removal. Moderators need the same script.
Pin the answers where new members land, and repeat them in the description of each space.
What the plugins offer for spoilers, and what they do not
Before designing around a feature, check that it exists. This table separates what is documented from what is not.
| Technique | Who applies it | Available in | Limit |
|---|---|---|---|
| Separate spaces for different viewing stages | Site owner | Jetonomy free, BuddyNext free | Relies on members choosing the right space |
| Episode number in the topic title | Member | Any plugin | A convention, not enforced |
| Coloured topic prefix such as “Spoilers” or “Spoiler-free” | Member picks, owner defines | Jetonomy free | A label only, it does not hide anything |
| Tags per series | Member | Jetonomy free | Helps search, does not hide anything |
| Spoilers content warning that blurs a post behind a “Show anyway” button | Moderator only | BuddyNext free | Applies to posts a moderator reached through a report |
| Member-applied spoiler tag or blur | Not available | None | Not found in the Jetonomy, BuddyNext or MediaVerse docs |
The row that matters is the last one. BuddyNext does have a Spoilers content warning, alongside NSFW, Violence and Strong Language. It blurs a feed post behind a label until the viewer clicks Show anyway. But it is a moderator action, applied from a report row after someone has flagged the post, and it is not something a member can switch on for their own post or a personal filter a viewer sets for themselves. The Jetonomy composer toolbar offers bold, italic, inline code, code block, link, blockquote and image upload, and no spoiler control.
That means a fan site has to lean on structure and habit. The rest of this guide shows how.
Weekly episode threads in Jetonomy
One space per show, or one space for the season
Jetonomy organises discussion into spaces, and each space has a type. The Forum type suits episode discussion: members post titled topics, replies thread up to three levels deep, and votes surface the best replies. Two layouts work:
- A space per series. Good for a few big shows with a loyal audience. Each week is a topic inside the space.
- One “This season” space with a topic per episode and a prefix or tag per series. Good for a broad community that follows many shows.
Pick one and stay with it for a season so members learn where to look.
Titles, prefixes and tags
Use a strict title pattern: series name, episode number, and the word discussion. Predictable titles are searchable, and Jetonomy search matches every word you type as a prefix.
Prefixes are coloured labels that appear before the topic title in the space listing. The owner defines them per space, up to 50 characters each with a colour, and a member picks at most one when writing a topic. Prefixes are plain labels and clicking one does not filter the listing, so use them as a signal. A calm grey for “Spoiler-free” and a bold colour for “Spoilers” tells readers at a glance what they are about to open. Tags do the filtering work: add one tag per series and each tag gets its own page across all spaces, sorted by latest or popular.
Scheduling the thread for air time
A moderator can write next week’s episode thread in advance and use the composer’s split button to schedule it. The picker uses the site’s timezone, and the post goes live at the first queue run after that time, normally within a minute or two. A site with no traffic and no server cron waits for the next page view, so run a real cron job on a busy fandom. Drafts and scheduled posts show on the author’s Drafts tab and can be edited or published early.
This is the useful part for a weekly show. The thread appears when the episode does, and nobody has to be awake to open it.
Pin, close and archive
Moderators can pin the current episode’s topic to the top of the space and close old ones. Close an episode topic after your safe window, so that late replies move to a general discussion topic instead of reviving a thread full of spoilers for people who just started the show. Moderators can also move a topic to a different space, merge duplicates and split a reply into its own topic, which helps when one comment starts an argument that deserves its own thread.
Separate rooms for different viewers
The most reliable spoiler barrier is a wall between audiences. Create spaces that map to how people watch:
| Room | Who it is for | Rule |
|---|---|---|
| Airing now | People watching live | Keep to the latest episode, mark anything older |
| Finished and fair game | People who completed the show | Spoilers allowed, label the series |
| Source material | Readers of the manga or novels | Anything from the source goes here only |
| Recommendations | Anyone | No plot details at all, only reasons to watch |
Spaces in Jetonomy have a visibility level (Public, Private or Hidden) and a join policy (Open, Requires Approval or Invite Only). Public and open is right for most rooms, because public discussion helps new fans find you. Private spaces are free in Jetonomy, so a spoiler-heavy theory room can require approval to join without any extra cost.
If the site also runs BuddyNext, a BuddyNext space can carry a Discussions tab powered by Jetonomy. Install the Jetonomy companion from the BuddyNext add-ons screen, then switch on Enable discussion under the space’s integration settings. Members get the structured threads and the space keeps its own feed for quick reactions.
Fan art galleries with MediaVerse
Albums and space galleries
MediaVerse free gives each member albums with a cover photo, and each album has one privacy setting that all photos in it follow. A fan can keep a sketchbook album public and a work-in-progress album visible to followers. On a BuddyNext site, a space owner can switch on a Media tab for the space (in the space’s integration settings), and the Albums view there keeps named sets that belong to the space. A fan art space can hold a monthly album, so each month’s best work is easy to find. The owner can also restrict album creation to organisers to keep the gallery curated.
Photos in an album show with the album’s privacy, and MediaVerse asks for confirmation before making an album more public than some of its contents. Tell artists this before they upload private sketches.
Credit, permission and takedowns
Most fan art is derivative work, and reposting someone else’s artwork without permission is a common problem on fan sites. This is general practice, not legal advice. Ask members to post only their own art, or to link to the artist’s original post and credit them. Keep a visible way to report art that is not the poster’s. In the BuddyNext media lightbox, a report offers reasons that include copyright infringement, and media reports land in the MediaVerse moderation queue. Decide in advance who handles takedown requests and how fast.
MediaVerse can detect duplicate uploads, but only within a member’s own uploads, so it will not catch someone reposting another artist’s work. Moderators and members have to do that.
Adult content
Anime communities often attract mixed audiences. MediaVerse offers optional AI moderation that checks each new upload against criteria you choose, including nudity or sexual content and violence, and the default action hides flagged media until you review it. It is off until you enable it, and it sends each uploaded image to OpenAI for analysis, which is a privacy decision to explain in your terms. If you expect younger members, take local advice on consent and data rules rather than leaning on a plugin.
Reactions, comments and challenges
Members can react with emoji, comment in threads and mention each other on media. MediaVerse Pro adds photo challenges (themed competitions), Pinterest-style and portfolio layouts, and upload streaks. A weekly prompt like “draw your favourite ending theme scene” fits the challenge format, though a simple pinned topic works on the free plan.
Where BuddyNext fits
BuddyNext provides the social layer around the discussion: member profiles, a feed, spaces, direct messages and notifications. Use it for the loose chatter that does not need a thread.
- Profile fields. A Watchlist group with a multi-select for genres, a short text for currently airing favourites and a dropdown for how spoiler-sensitive the member is gives other members a hint before they tag them.
- Hashtags. Members type #seriesname in a post, and each hashtag gets a feed page and a follow button. They are handy for live reactions during an airing.
- Polls. Polls with two to five options are free in the feed. Use them to pick the next watch-along or to vote on a best opening song.
- Mentions and following. @mentions notify the person named, and a member can follow a hashtag to keep an eye on its feed.
The Spoilers content warning sits here too. When a member reports a feed post that gives away a plot twist, a moderator can open the report row and apply the warning instead of deleting the post. The post stays in place, blurred, with a Show anyway button. That is a proportionate response to a first offence.
Live reaction nights
Some fans want to react in real time as an episode airs, and a long forum thread is the wrong place. Use the BuddyNext feed for it. Agree one hashtag for the night, so every reaction shows on a single tag page that members can follow, and keep the hashtag name free of anything that gives away the plot. Schedule the announcement post in advance so it is in the feed when the episode starts. After the night, a moderator can pull the best comments into the episode topic in Jetonomy, where the discussion is kept for people who watch later. That split keeps the noisy part short-lived and the lasting part searchable.
Moderating a fandom
Fan communities are passionate, which makes heated arguments about rankings and endings routine. Plan for them.
- Jetonomy’s moderation queue is in the free plugin, along with flagging. Any signed-in member can flag a topic or reply, moderators work the queue from wp-admin or the front end, and space moderators can handle one space without dashboard access.
- Trust levels automatically give reliable members more freedom, so a brand-new account does not arrive with full privileges.
- Jetonomy’s anti-spam settings support invisible CAPTCHA (reCAPTCHA v3 or Cloudflare Turnstile), Akismet and rate limits for new members, which suits a fan forum that attracts drive-by link posting. The forum SEO and spam control guide covers the settings in more depth.
- BuddyNext reports, strikes and suspensions give you proportionate steps for repeat offenders, with an audit log of every moderation action.
Write down the escalation ladder and share it with every moderator so decisions look consistent. For help with choosing between a forum and a social-first layout, the forum picker compares the options, and private versus public community helps decide which rooms should be visible to search engines.
A seasonal rhythm
- Before the season: create the spaces, define prefixes, write the spoiler policy and pin it.
- Each week: schedule the next episode topic, close the topic from the previous window and pin the new one.
- Mid-season: start a monthly fan art album and a poll for the best episode so far.
- After the finale: move discussion into the “Finished and fair game” room and archive the airing space.
The photo-privacy settings used here are the same ones explained in the skincare community guide, where they matter more.
Frequently asked questions
Can members mark their own posts as spoilers?
Not with a dedicated control. The Spoilers content warning in BuddyNext is applied by moderators to reported posts. Members can pick a coloured prefix in Jetonomy, add the word to the title and post in the right space, but none of those hide the text.
Does Jetonomy have a spoiler tag in the editor?
No. The composer toolbar has bold, italic, inline code, code block, link, blockquote and image upload. Plan around structure and rules instead.
Can I schedule an episode thread to appear when the episode airs?
Yes. The Jetonomy composer lets you schedule a topic for a date and time in the site’s timezone. It publishes on the next queue run after that time, so it can be a minute or two late.
Is fan art hosting free?
MediaVerse free includes albums, privacy levels, reactions, comments, reporting and a storage limit per member that you can set. Pro adds cloud storage, extra layouts, stories and photo challenges.
Do I need BuddyNext if I only want a forum?
No. Jetonomy runs on its own. BuddyNext is worth adding when you want profiles, a feed and messages around the forum, and Jetonomy picks up its design tokens automatically.
Will it match my theme?
Jetonomy adopts the colours from Reign, BuddyX and BuddyX Pro, including dark mode, without custom CSS. See the Reign demos to preview layouts.