User:Raijinili/todo

Wiki settings

• Discord preview for wiki links sucks.

Write a style guide

A style guide should tell you:

• Page naming.
  • E.g. "Try to match name with FFTPatcher."
  • Namespacing.
    • (Not everyone knows how this works. Almost no one does, probably.)
• Page formatting and styling.
  • Sections.
• What info should be on the page.
• Categorizing.
  • When to spin up a new category.
  • Categories vs list pages.
• When to make templates and how to learn them.
• Table styling.
• Organization? (What do I mean by that?)
• Probably some tips like transclusion.
  • A table "template" to copy-paste, because people find tables hard.
• Mobile-friendly styling.
  • Check this for ASM pages, which tend to have long lines.

Here are some categories to make styles for:

• Disassembly
• ROM map
  • Fields (including FFTPatcher fields).
• Event instructions
• ASM patches

Names

• Me: "I propose descriptive names should include mostly-uniquely identifying info in the first 10 or so characters, so that you can see the prefixes in tabs and it'd mean something. Remember when mobile GitHub page titles all started with "GitHub ..."?"

ASM styling

• Try to match code output with psxfin?
• Xif: "personally the way I would do it is name all of the routine pages: Filename - Offset_Start"
  • Meaning, set a redirect from "BATTLE.BIN - 00183ba8" to "Set Only Action Taken".
• Xif: "all hex should be capitalized and 0x8 to indicate a memory address"
• Templatize each ASM line, so that we can style and anchor them. And re-read them with bot if need be.
  • E.g. {{mips|00188b64|27bdffe8|{{instr|addiu|r29|r29|0xffe8}}|Add two numbers}}
    instead of 00188b64: 27bdffe8 addiu r29,r29,0xffe8 Add two numbers
• Can make a template that takes an address and does a page lookup.
• Disasm pages should list and globals fields they touch, and wikilink to them.
  • Recursively?
• Tabs bad.
• For branches, there would be an in-page link to the jump point. Hovering over or clicking a branch instruction would highlight its target.

ROM map styling

• Pages for fields and flags should list locations where they are handled. E.g. Vertical Fixed should link to subroutines that use it, and how.

Table styling

• Borders. Have them.
• Probably want to specify a default class.
• V-align top. Works better with tall cells on thin screens.

Make a bot

np just do it

First, make a bot, and make it edit a page as a test.

Scrape

Scrape all pages. Alternatively, figure out how to download the page database and ask Xif for it.

Namespacing

I want to put pages under namespaces. For example,

• Figure out what namespaces we want.
• Figure out how to implement them. cf
  • Add them to namespace list. (Use ID=3000-4999, or the BlueSpice extension.)
  • Make them part of default search. cf

Other decisions to make

• Separate wiki for FFTA? I don't think there's overlap. And we can set up crosswiki linking so that you can type [[ffta:SomePage]].