rnice01 / ja_translations Goto Github PK

Update dialogue component to include:
Translated text (hide button/link if no translation provided)
Grammar notes, hide button/link if no grammar notes exist)

Maybe set a max height for scrollable text if the dialogue has too much japanese/english text?

• Update classes on Vue components to use Bootstrap 5 styles

Set up the app in heroku with provisioned DB and necessary buildpacks for the app.

• Set env variables for production DATABASE_URL, SECRET_KEY_BASE, GUARDIAN_SECRET_KEY

Segmenting should be extracted into it's own service.

Segmented text should include the furigana in Ruby markup

Segmenting should happen probably happen in the dialogue changeset.

They look like hot garbage right now. Need some sort of template for each page. Each page should have some descriptive text on it too.

On the game transcripts page, each game has an image column. Should be using that in the links.

• Swap out Tailwind with Boostrap

Users can have multiple decks
Each deck has a name and multiple flash cards

Each flash card has a single kanji or vocab, readings, meanings, context (if it was created from a segmented text, keep the sentence it was in), and optional user notes, SRS level, next review.

No bells and whistles like password resets or 2 factor.

• Unique email constraint with test

• Validate password complexity with tests

• Also need endpionts and forms for:

• Creating and updating chapters

• Creating and updating scenes

• Creating and updating dialogues

Use a tool like Axe to audit site and fix all web accessibility issues. Also should see if it can be added as part of the build process. That way moving forward with new features, the web accessibility issues can proactively be addressed.

Each deck should have the current reviews and lessons displayed to the user.

After #6 gets merged in, the Admin forms will need to be updated to use Bootstrap styles. Right now Phoenix has view helpers for form fields. Adding some Bootsrap specific view helpers might help having to keep writing the same classes to every label, input, and button.

• Add Bootstrap view helpers for input, label, and buttons. Something like bs_label, bs_text_input etc...

• Update current forms to use new view helpers

Right now the GameTranscript model has a string field for an image source. I'd like to have a separate model for saving other image information like alt text.

When the user selects the word it should be highlighted and shown in the sidebar component with data from a dictionary service (Jisho?).

Blocked by #1

On consecutive failed login attempts, the auth system should automatically reject further attempts for a certain period of time.

Create the styled Vue components for the main flash card quizzing system.

It would be nice to have Github actions up to validate PRs for linting, testing, etc... But getting the current tests in a working state for a basic Github Action is the goal.

Need to set up a service to automtically segment japanese dialogue and produce ruby markup.

Not sure if I should keep a copy of the original japanese text without the ruby markup or not.

Will also need to set up a mix task to update any existing japanese text in the dialgoues to include the ruby markup. Backup DB before you do this!!!!

This is copied from the Pow Auth hexdocs:

NIST 800-63b recommends that you reject passwords that are commonly-used, expected, or compromised. The guidelines explicitly mention the following methods to ensure strong passwords are used:

Passwords obtained from previous breach corpuses.
Dictionary words.
Repetitive or sequential characters (e.g. ‘aaaaaa’, ‘1234abcd’).
Context-specific words, such as the name of the service, the username, and derivatives thereof.