zhanknight / tacopoetry Goto Github PK

Content-viewing pages have a weird masonry layout
Scaling/Responsiveness issues
Navbar is hideous

All content in stored in the database as a string. Since some of the content requires special formatting (haikus, etc), the application will need some means to store/detect/utilize formatting cues in that string.

The application should have dedicated models for posting/creating/updating authors and content.
Once created, these models will need to be added to all of the create and update endpoints. Mapping will need to be added as well.

When a user loads any page, the content is requested from the API.
While the front end waits for that response, the page shows the 'uh oh! no content yet' message.
We should distinguish between receiving an empty response from the API and waiting/loading,

Tailwind is currently used via the CDN. This is okay for testing and dev, but should be swapped to an actual installation.

The home or index page should load either a randomly selected content item or a 'content of the day'.
Right now the site just loads into the full list of musings.

Add auth
Restrict API access to App itself
Rate limit?