---
# System prepended metadata

title: Wiki Content Ideas

---

# Wiki Content Ideas

Pages will be split into Namespaces (kind of like folders), so this should basically be a plan for which categories we want to go for

These sections are in the format of: Namespace => What questions should be answered in that namespace.

From that, the idea of a namespace can come from two directions:
* We can have a namespace for X => what questions can be answered there?
* A lot of people ask about X => what namespace could they look up the answer in?

## Gameplay

* What is X?
* How does feature X work?

This namespace should be mainly focused on players - general information that the average player would care about, easy to understand, not too much detail.

Detailed ideas: List AC types and how to build for them on Appeal Chance page, types of Skills and how they work (Vo Gain+ vs Appeal+, SP Overcharge, cleanseable vs. non-cleansable...)

## Guides

* How do I X?

Detailed ideas: Starter Guide ("Road to Advanced"), and where to go from there ("Road to Advanced+"), ask guide creators about possibly transferring their guide to the wiki (Teambuilding Guide, SBL MVP Guide etc... and just link them instead if they don't want to)

## Events

* How does event X work?
* Where is reward X in event Y?

Detailed ideas: Story event reward list, ItEx shop prices, DLP floor notes

## Calculations

* How is X calculated?

For micro-optimizing players or tool/site creators. Exact formulae for things discussed in the Gameplay namespace.

## Calculations/Research

* How can I trust the formula for X?

Sub-namespace of Calculations, with the proofs, collected confirmed values and other stuff that helped discover the formulae from Calculations and can be reproduced to prove they are correct.

## Tools

* Is there something that can help me with X?

Links to existing tools or sites for certain common tasks. We'd probably add links to sites like Kirara, the Note Map DB, the SP Power Calc, that kind of stuff?

Detailed ideas: Free Loveca sheet, ItEx sheet, SP Power calc, Event calcs

## Internal

* I am already datamining, is there a summary of what I can find where?

**This namespace should not be a how-to-datamine**, since that's probably the fastest way to get a Klab DMCA. It should just be some kind of notepad so dataminers or tool creators can quickly look up the IDs used in the databases to research things.

Limiting this to the trusted editor role is probably a good idea.

## Cards

* Is Card X good?
* Should I upgrade Card X?

Kind of like Rev's card reviews - list strengths and weaknesses, what songs or gimmicks they excel at etc.

Only list some basic information, link to kirara for details

Can have card thumbnails linking to these pages from other namespaces

## Songs

* How should I approach Song X?
* What strategies are there to clear/S rank X?

Common strategies and things to watch out for, and listings or cards (or types of cards) that fit for a song's gimmicks. (For example, YnT Challenge => list Zombie Setup, DR Setup etc... as possible approaches, and which cards are very useful for each)

Can also list Story Stage alternatives, or group approaches by aim (clearing, S ranking, voltage ranking etc), but there'd probably be some overlap

Alternatively: in the style of the song section on the OtamuGames site when it was still up - anyone can add their team, what worked for them, what the scored, any comments... a collection of teams that players can try to reproduce to match what they are aiming for

## Schedule

* What cards are left in this rotation?
* How likely is a Fes/Party/Event of X?
* How long has it been since X's last UR?

Not a namespace probably, just a standalone page.

## Story

* What happened in event/chapter X?
* Where can I read X?

Sub-namespaces for main/event stories. Only very short summaries per episode, and linking to a YouTube video of the story (both GL and JP if possible)

# Ideas for the Future

* Edit permissions change: Every registered account can edit, but it will just be queued as a suggestion. Mods will have to approve. Accounts can be made into trusted editors to skip the suggestion step.
* Translation support
* Automated updates via Aran (bot)