If #6 created a Data format different from the MVP, update the RTK fill button to use the new data format.
Additionally, update the hardcoded data to fit the new format.

Also, add GitHub action to format check PRs

Run a JS script.
Keep the search bar up top.
Keep the stories

Everything else should be on the table for removal via the JS Script.
The goal is to keep the page focused on stories alone.

Update code. Separate out into different files.
Move the code for the Webview as well.

Add a sample set of Kanji data to the support_files directory. Also, add the stroke order images inside this directory. Images should use a naming convention that'll allow easy lookup for any given kanji.
Additionally, extend the RTK fill functionality.
It should copy the stroker order image to the collection.media directory.

Add functionality to the Stories button.
By default, hide the stories webview.
The button must say "show stories" or something similar.

Add tooling or data for kanji based on rtk 6th edition
For each kanji, add:

1. Kanji Character
2. Heisig number
3. Keyword
4. Stroke Order

Extend the functionality triggered by clicking the RTK fill button. If the Koohie stories webview is being displayed, load the page for the kanji identified by the "Number" field.