Launch week is a weather event. A season is a weather event. A patch, an AMA, a press hit, a Discord raid of new accounts — weather. What remains when the sky clears is habit: a room that still moves on a Tuesday in the fifth month, a handful of people who answer strangers, a tree that does not grow a new empty node every time someone is bored.
This is post-hype design. It is not how to grow DAU (conversions and first screen). It is not how to run events (a date plus a leftover). It is not onboarding methods (doors for people who just arrived). Those still apply. This article is what you do when those articles worked for three weeks and then the graph looked like a cliff.
XenForo community sources we queried never used the phrase “hype.” They did say the thing that kills a room after a spike: deep, temporary, hyper-segmented nodes look empty and discourage the next post; prefixes inside a broad room beat a new forum; deleting a node deletes its threads. The rest is operational practice: cadence, regulars, archive versus delete, the courage to stop adding surface.
Name the fade you are in
Different cliffs, different jobs.
| Fade | What just ended | The hangover | The job |
|---|---|---|---|
| Post-launch | Founding week, first 50 accounts, press | Seed threads go quiet; founders perform less | Install a ritual and a reply budget that survive the founders’ adrenaline |
| Post-event | AMA, contest, stream | Notice still up; sticky still up; Discord channel still named after Thursday | Kill chrome the same day; keep the leftover; do not schedule another spike yet |
| Post-season | Expansion, sports season, academic term, game battle-pass | Seasonal node/prefix still pretending it is current | Flip the prefix to archive-as-filter; do not delete the year |
| Post-migration | You moved hosts or platforms | Veterans hunt for the last-post column; new people see a museum of imported titles | One live room, one ritual, stop importing furniture |
| Slow leak | Nothing dramatic | DAU/MAU slides for a quarter | Measure before you redecorate |
If you cannot name the row, look at the health panel for four weeks before you invent a season. A slow leak plus a new category is how you get two problems.
Game and RP communities live in the post-season row on a clock. The XenForo gaming cupboard is architecture. The Discourse gaming fit test is whether you should have been on this software. This article is the Tuesday after the patch hype thread dies.
What you are trying to keep (not “activity”)
Activity is a fog. Keep four things.
- A first screen that still says something moved. What’s New / Latest / New posts — not a tree of quiet children. The engagement article already made this the return visit.
- A reply a stranger can get. Median time-to-first-human-reply on new-member posts. If that number only worked during launch because you lived in the tab, it was never a habit.
- A reason to open the site that is not a campaign. A ritual, a watch on a room that actually moves, a question that might have a solution.
- A core of regulars who will still post if you take a week off. If the graph is you, you do not have a community. You have a blog with comments you write yourself.
If (4) is three people, design for three people plus strangers. Do not design for the launch-week peak. The peak is not coming back on command. Events can rent a night. Habits keep the week.
Cadence: a calendar you can staff in February
Hype is a burst. Cadence is a promise with a name on it.
Write a week that still works when you are tired.
| Slot | What it is | Who owns it | What it is not |
|---|---|---|---|
| Ritual | One thread a stranger can answer without lore (weekly or fortnightly) | A named person, personal account | An event, a contest, a notice every time |
| Inbox | First posts in Intro + Support (or your two live rooms) | The reply budget from onboarding | “We are always here” |
| Edition | Patch notes / ship post when you ship | Newsroom split | A daily blog you will skip |
| Housekeeping | Unstick, unfeature, kill notices, merge empty rooms | Whoever has ACP | A redesign |
That is the whole public calendar. If you want a monthly AMA, it is an event with a leftover, not a cadence. If you cannot staff the ritual and the inbox, cut the ritual first only if Support is the product; cut the extra events first if hangout is the product. Never cut the inbox. Unanswered first posts teach the next person the room is a museum.
How often is “enough.” There is no official number. Practice: a hobby hangout can live on one ritual and honest watches. A support site can live on no ritual if solutions still close. A game board in off-season can live on one weekly “what are you running” and a patch edition when there is a patch. Daily staff threads are how you burn the two people who actually log in.
Post as a person. XenForo community practice: the root Admin account stays for official/system posts. Cadence threads are conversation. Use a personal profile. Regulars will not disagree with the ban button. You need disagreement. That is how a Tuesday stays interesting.
Do not replace cadence with notifications. Watches, digests, and push amplify movement. After a fade, there is less movement. A digest of silence is how people unsubscribe. Fix the ritual, then ask them to watch that. Discourse may still be on Discourse ID without SMTP; do not invent a drip until mail exists.
Core regulars are the product you cannot buy
After hype, the graph is a handful of names. Treat those names as infrastructure.
Find them without a vendor score. Last four weeks, public posts, not staff, not the contest week. Sort. The top slice that still answers other people (not only starts threads) is the core. Discourse TL3 is a rolling 100-day Regular — useful as a hint, not as a hiring committee. XenForo reaction score and message count are global and gameable. Eyes beat trophies.
Give them work, not titles. The 30-day calendar already said this for month one. After a fade it is louder. FAQ thread ownership, greeting first posts, a tag tidy, “you host the ritual in August.” A moderator badge without a job is politics. A job without a badge is how you keep them.
Protect them from the nuclear badge. They should not have to argue with Admin. They should not be the dump for every brigade. When you are gone, they are the reply-time instrument.
Do not replace them with a contest. Contests attract entries. Regulars attract regulars. If you spend August judging screenshots, nobody hosts the ritual. The rewards article is how status and access work. After a fade, status that means “this person answers questions” is worth more than a shop.
Plan their vacation. If two of the three will be offline for a season reset, say so in public and shrink the promise (“inbox on weekdays only”). A surprise hole after a hyped patch is how people assume the board died.
If the core is zero, you are the core. Write that down. Then either accept a blog-with-comments, or spend the next month on inbox + one ritual and no growth campaign. Onboarding a flood onto an empty inbox is how you pay for ads to teach people you are dead.
Stop adding empty nodes
This is the reflex that makes a fade look worse.
Someone says “activity is down.” Someone else creates General / Off-season / Chat / Memes / Events / Archive 2026. The tree gets longer. Each child has one sticky and no last post. The first screen looks like a closed mall. XenForo community practice is explicit: deep segmentation overwhelms, misfiles threads, looks empty, and discourages participation. Broad rooms keep conversations stacked where movement is visible. Prefixes filter without a permission-cache rebuild.
Rules after a fade.
- New node requires a 30-day volume story you can point at in the current room (“these 40 threads would be easier to filter”). No story, no node.
- Temporary moods are prefixes.
S3,Holiday,Launch,Recap. When the mood ends, the prefix remains a filter. The node does not remain a building. - One obvious live room beats four quiet ones with prettier icons. Returning members should hit What’s New / Latest and see that room move.
- Do not create an “off-season lounge.” That is how you move the last three regulars out of the room strangers still land in.
Discourse equivalent: do not add a category because Latest “feels samey.” Add a tag. Eighty categories is the same mall.
IPS Clubs that isolate the remaining energy are the same mistake with a friendlier name.
If you already built the mall, the work is merge and redirect, not a new paint. The nodes article is the carpentry. Here you only need the courage to close doors.
Archive versus delete
Hype leaves artefacts. Treat them as a library, not as trash.
| Object | After the fade | Why |
|---|---|---|
| Event sticky / feature / notice | Remove the same day the event ends | Expired chrome trains people to ignore staff |
| AMA / contest / patch thread | Keep. Prefix Recap / Complete. Recap in post one |
Leftover is the product |
| Seasonal category you should not have created | Move threads to the broad room, then remove or unlink the node after a backup | Empty season node is a hallway |
| A node you delete in XenForo | Deletes the threads | Community sources: deletion is permanent for associated threads. Backup first. Deleting is not archiving |
| Old quiet threads in a live room | Leave them unless they are spam or rule-breaking | A long thread list is history. It is not clutter |
| Discord event channel | Archive or hide | Dead channels are empty nodes with emojis |
| Seed threads from launch that nobody owns | Close with a sentence, or staff them | Silent seed threads are decoration |
Archive as a filter, not as a basement. A prefix or a tag people can still search is an archive. A category named Archive that only staff remember is a basement. Guests who land in the basement from Google bounce. If you must have an archive node, noindex it or make it clearly historical — and still prefer prefixes.
Do not “start fresh” by wiping. Imported history is why veterans stay after a migration fade. A clean slate is a second launch without the hype. You will not get the press twice.
Unfeature on a calendar. XenForo 2.3 will not expire features for you. A featured launch thread in month five is a lie on the door.
What to stop doing (the fade diet)
Write this on the staff page the week you name the fade.
- Stop the second home. If Discord claimed the conversation during hype, take it back or admit Discord is home. Forum vs Discord is the meeting. A split room looks twice as dead.
- Stop the notice stack. One Block, or none. Launch leftovers are banner blindness.
- Stop the contest as life support. If the week after a contest returns to the old baseline, you rented reach. You already knew that. Do not rent every Friday.
- Stop turning off the sandbox to “make it easier.” TL0 and Established exist so the remaining staff are not a spam queue. A fade plus an open hose is how the last regulars leave.
- Stop restyling the header. The next member bounces on silence, not on the font. The calendar said that on day one. It is still true in month six.
- Stop measuring lifetime posts. The health panel is seven instruments against your last four weeks. The cliff will show up in DAU/MAU and reply time, not in total posts.
A 30-day reset (after you name the fade)
This is not the member onboarding calendar and not a launch checklist. It is a staff reset.
Days 1–3 — look, then subtract.
- Fill the metrics row. Annotate the hype that just ended.
- List every sticky, feature, notice, and event node. Kill anything whose stop date passed.
- List rooms with no non-staff post in 14 days. Merge or prefix; do not add a sibling.
- Name the core regulars (including you). Write who has inbox this month.
Days 4–14 — one live room, one ritual, inbox.
- Make the first screen that room’s movement (New posts / Latest / a short tree).
- Start or restart one ritual a stranger can answer. Personal account. No notice unless it is the first one after a long silence — then Floating, once.
- Answer every first post in the two live rooms. Template allowed.
- Explain watches once in the welcome. Auto-watch only that live room.
Days 15–30 — do not spike.
- No AMA, no contest, no new category. If a patch ships, use the newsroom split and stop performing after the three real questions.
- Ask one regular to host the next ritual. If they say no, you learned something cheaper than a plugin.
- Compare weeks 3–4 of the sheet to week 0. If reply time improved and new→first post did not get worse, hold. If everything still falls, your problem is discovery or a product that ended (the game shut down). Cadence will not resurrect a corpse.
If the game did shut down, say so. Archive as history. Do not run “engagement” on a grave.
Platform notes (habits, not tours)
XenForo. Forum list versus New posts as default: after a fade, New posts is kinder if the tree is a junk drawer. Prefixes over nodes. Promotions still run hourly for recently-active people — a New member banner still helps staff see who to answer, even in month six. Trophies will not restart a room. Stock will not schedule your ritual; a staff calendar will.
Discourse. Latest already is “what moved.” Do not disable TL0 to chase a flatter cliff. TL3 demotion after a quiet 100 days will surprise veterans who thought Regular was a medal — explain it once, or lock levels for people you cannot afford to demote. Data Explorer (if you have it) is how you see whether the cliff is readers or writers. Chat is not a ritual.
Discord in the mix. If the hype lived in a guild, the fade will look like a quiet forum even when voice is fine. Decide the home. Recap or stop calling the guild a “community forum.”
Worked shapes (not benchmarks)
Hobby board, launch fade. Fifty registrations in week one, eight first posts, then silence. Reset: kill the five seed threads nobody owns, one ritual on Wednesdays, inbox on those first posts, no Discord requirement. Measure four weeks. The success is two regulars who are not you, not a return to fifty.
Game board, season fade. Prefix S2 stays filterable. S3 starts in the same room when the new season is real. Weekly “what are you running” continues in off-season with a smaller promise. Patch editions only when there is a patch. Officers use personal accounts. The listing and whitelist stay — those are product, not hype.
Support site, launch fade after a product hunt. Registrations were tourists. Keep Solved, keep reply time, stop the launch notice, do not add a lounge. Tourists who stay will ask questions. The rest were weather.
FAQ
Should we email everyone “we miss you”?
One useful mail if you have a real ritual and mail actually delivers. A guilt trip is how you get spam complaints. The calendar already preferred one useful email over a drip novel.
What if regulars only want to talk about the old hype?
Let them, in the same live room, under a recap prefix. Also keep one prompt a new person can answer. A club handshake as the only thread is how the fade becomes a closed circle.
Can we archive the whole forum and start a new one?
Only if you are willing to throw away URLs and veterans. Usually you want a prefix and a honest first screen, not a second site.
Is a smaller DAU after a season a failure?
No. Compare to last off-season on your definitions. A smaller honest room is healthier than a peak you fake with contests.
Takeaways
- Name the fade: launch, event, season, migration, or leak. The job changes.
- Keep four things: a first screen that moves, a stranger’s reply, a non-campaign reason to open the site, and regulars who are not only you.
- Cadence is a ritual plus an inbox you can staff in February. Events are extra. Admin is not the host account.
- Regulars get work, not surprise badges. Contests do not replace them.
- Prefixes and archives-as-filters. No new empty nodes. Deleting a XenForo node deletes threads — that is not an archive.
- A 30-day staff reset is subtract, then one room, then no spike. Measure against your own last four weeks.
Hype is weather. Habits are climate. Build for Tuesday.