Project Summary
Objective
Create a dynamic spoiler filter that works on both mobile and desktop, and can be easily added by contributors using the Visual or Source Editors.
Deliverables
- Spoiler filter template
- Guide to use
- Spoiler applied to 10 most trafficked pages.
Timeline
| Phase | Description of Work | Target Date | Status |
|---|---|---|---|
| Concept | Gather ideas, wants, and suggestions for the spoiler filter. Produce a final criteria list. | 02/16/24 | complete |
| Research | If unable to recruit someone with the right skills, research how to accomplish goal and what is feasible. | 02/20/24 | complete |
| Development | Begin creating a filter that satisfies as many criteria as possible. | 02/22/24 | complete |
| Launch | Release filter and a guide to using the filter. Implement on highest-trafficked pages. | 02/28/24 | complete |
Do you have the know-how to help with this project? Be our "Wiki Jesus"! Message Eekz directly to get started.
Phase 1. Concept (completed 02/16/24)
1-A. Ideas & Suggestions
Expand section to see our starting point.
- The basic spoiler filter. This template already exists in various wikis, but it's clunky and doesn't allow contributors to specify what is being spoiled. It collapses an entire section. After the user expands the section once, they will not need to expand it again on that page (in theory; not true in practice).
- Divide information into sections by book and collapse them automatically.
- The reddit spoiler filter. Basically, anything considered a spoiler could be blacked out. If the reader wants more information, they would need to highlight the text with a cursor. This is cumbersome for collaborators, annoying for readers, and - 3,300+ pages into the series - would black out most of our pages; we don't want to pursue this unless it is our only option.
- A checkbox system. Somehow, users could check off which books they have read, and would only see information pertaining to those books. They would have the option to view spoilers for other books. This idea was stolen from a comment on the DCC reddit and looks... difficult to create and institute, but it would be very cool.
- Coppermind's spoiler system. Coppermind has a much longer history, more active community, and a privately hosted website, so it is able to depend heavily on the time machine. Otherwise, "Spoiler Warnings" are slapped onto the top of every relevant page for six months after a book is released.
- The Portal Wiki Toggle. This is everything we want and wish we could do, but - once again - Portal is a privately hosted wiki with a skilled team at the helm.
Unfortunately, the reality is that we are restricted by the technical skill available to us, our $0 budget, and Fandom.com's interface.
1-B. Working Criteria List
Requirements:
- Must work on mobile as well as desktop; 80% of users access the wiki on their phones. Fandom mobile does not support mobile JS.
- Must be easy to use in Visual Editor. 92.4% of DCC Wiki edits are made in Visual Editor rather than Source Editor.
- No pop-ups when reading the wiki page.
Nice to Have:
- Top-level toggle by book. If not possible or too clunky, then hide all spoilers except race/class for books 3+.
- Text pertaining to unselected books is hidden or blacked out.
- Ideally, book selections are saved across the fanwiki or selection saves by page; you don't have to hit five toggles every time you visit Carl's page.
Phase 2. Research
- Existing Extensions / Scripts. Note: May not work on mobile.
- Extension:Spoilers at MediaWiki. Parser extension that adds a spoiler tag and blocks a wall of text. Actual usage looks like a lot to expect users to include.
- SpoilerAlert at the Developers Wiki. Depends on Javascript; will not work on mobile.
- Extension:Spoilers at MediaWiki. Parser extension that adds a spoiler tag and blocks a wall of text. Actual usage looks like a lot to expect users to include.
- Collapsible Elements.
- Results of testing on Katia's page:
- If more than one non-table element is collapsible, the Visual and Source Editors panic.
- Collapsible tables create inconsistent formatting. May be able to work around by using a template?
- Collapsible infoboxes only work as intended on desktop; they do not collapse on mobile.
- Results of testing on Katia's page:
- Tabber. Very neat idea and way to organize information; however, does not work in fandom.com mobile and does not provide an easy way to edit sections in Visual Editor.
- Spoiler Warning Template. As seen at many fanwikis, this would be a warning at the top of the page that warns readers of intended spoilers. For whatever reason (probably CSS related), notice templates do not appear on mobile.
Phase 3. Development
As of 02/20/24, we appear to have a functioning spoiler filter that hits all of our requirements (but none of the "nice to have"). Documentation and instructions to use it can be found at Template:Spoiler. It is in use on Katia Grim's page.
02/24/24. Problem with the spoiler warning: Does not allow wikitext formatting on first line. Why?
We are now working on a header for pages that are, by their very nature, spoilers.
02/26/24. Template:SpoilH now exists.
Phase 4. Launch
02/28/24. Both templates are fully operational and documented. A formal Spoiler Policy has been written, proofread, and posted.