Difference between revisions of "Todo"
(Created page with "A list of things to do to improve the wiki. Items marked with {{Jewels}} are things we are targeting to get done before opening the wiki to the public. When an item is done,...") |
|||
Line 42: | Line 42: | ||
* {{Jewels}} Split Portal content to several child pages, keeping a summary in the Portal. Add a navigation pane for each page the Cards section. | * {{Jewels}} Split Portal content to several child pages, keeping a summary in the Portal. Add a navigation pane for each page the Cards section. | ||
* Fix expansion set symbols to make them a consistent size and with transparency instead of white BG | * Fix expansion set symbols to make them a consistent size and with transparency instead of white BG | ||
− | * | + | * Add template for card-level info (data will be pulled by bot) |
===Guides=== | ===Guides=== |
Revision as of 22:29, 3 January 2019
A list of things to do to improve the wiki.
Items marked with are things we are targeting to get done before opening the wiki to the public.
When an item is done, delete it from the list.
Events
- Add summary/overview of general event concepts, e.g.
- Typical event structure and nodes
- Player brackets
- Mastery tiers
- Reward schemes (progression, individual, coalition)
- Different event types (e.g. PvE vs PvP)
- Add at-a-glance info for all events to the Events Portal (e.g. a unified list with sortable info columns)
- Consider which content to collapse by default in all Event pages (e.g. deck lists, rewards, possible points)
- Move content from "Event" section of each Event page to a new standard infobox for at-a-glance info about the event
- Add a navigation pane to the bottom of each Event page (similar to the one for Planeswalkers)
- Create pages for events which aren't yet added
- Consider what images to add to each event page to improve event recognisability and visual appeal
- Restrict Contents to a lower level (e.g. 2) on each Events page
- Figure out how best to include event-specific or node-specific strategy content to each Event page
Story
- Add Portal and overview
- Add pages for Story at a top level (ORI, Training, BFZ, Heroic)
- Add sections to each Story page summarising each Story Chapter
Planeswalkers
- Add starting deck to each PW page
- Add lore to infobox for each PW (race, birthplace, allies, etc)
- Add concise game-oriented info to each PW page. E.g. how good the PW is; basic strategy guide for Loyalty abilities (which abilities to use when); what style of deck works best (control/aggro/...); whether the PW is required for specific events; any known bugs; etc (any other pertinent PW-specific info useful to players).
- Limit width of Planeswalkers navigation box, so all info is seen regardless of browser width
- Expand on further general planeswalkers concepts, e.g.
- Buying/levelling/resource costs
- Planeswalker decks and deck slots
- Event restrictions on planeswalkers
- Determine ratings for each planeswalker
Cards
- Add page for Holiday cards
- Add set-specific info to each Cards set page, e.g. notable cards, how the mechanics play, feel of power level, lore, etc
- Split Portal content to several child pages, keeping a summary in the Portal. Add a navigation pane for each page the Cards section.
- Fix expansion set symbols to make them a consistent size and with transparency instead of white BG
- Add template for card-level info (data will be pulled by bot)
Guides
- Consider what guides could be useful, e.g.
- How to choose gem match
- How the AI chooses a gem match
- How to build a deck
- How to spend resources efficiently
- Guide to Planeswalkers
- Guide to Card Sets
- Guide to Coalitions
- Add a Guides portal page showing existing and wanted guides
- Add or fix cross-links between reference pages and guide pages
Other/General
- Improve Main Page
- Add a panel with links to other useful mtgpq sites
- Beautify, remove placeholder text
- Review all content, make it more correct, complete, concise, or compelling
- Integration with mtgpq.info (especially for Cards)
- Investigate direct access for wiki developers to database dump from mtgpq.info (avoid having to pester Octal9 every time new content is added to mtgpq.info)
- Determine launch plan
- Identify minimum set of work to do before launch
- Decide how to launch (Cold turkey public? Get feedback from select invitees as a first stage?)
- Determine and assign enough admins amongst the active contributors