nomercy235 / cyoa-frontend Goto Github PK

It might be a good idea to have a common modal which can be used everywhere. Maybe also a common formik modal? Maybe the form modals should use the withFormik HOC?

It should be reset to Rigamo | Choose your own Adventure.

Acceptance criteria:

• The name of the app in the Dockerfiles should reflect the reality
• The NginX frontend proxy should redirect all api.cyoatta.xyz requests to cyoatta.xyz:4209 so that the app no longer needs to know about the port
• Explore the possibility of improving the backend deployment

Also, think of a way to fix the flickering caused by showing errors in the form.

The color should be stored on the backend because it should be used for flashing the attribute when a change occurs in its value. Same goes for the text color.

For instance, the collections table, where "Default" is shown, has uneven rows due to the missing actions for the default row. The td element where the name is wrote should have a min-height of X (possibly 73px) to avoid visual glitches.

There are pages which don't handle 404s and end up staying in a blank state if the user modifies the URL.

If an important attribute drops its value below 0, the associated ending is no longer played.

The user should also be able to view the author's profile when clicking on them from a story

It looks like the click event goes through the modal and activates the list element, which in turn generates some events (reloading the sequences and others). This breaks the edit for good and looks weird on delete.

• Sequence view - container should have 100% height and the sequences tables should have a top margin on small screens.

Try this one: https://github.com/pubkey/broadcast-channel

It should be represented through a graph where:

• the nodes are the sequences of the story
• the vertices are the options that navigate from sequence to sequence

The save forms can use the same exiting modal, but they won't be saved immediately on close. The save can either be done in the background using web sockets or when the user clicks the save button.

Because the quick filter expands when selected and then the advanced filters are hard to click on.