metallifax / bjjt-blog-frontend Goto Github PK

A blog should be able to create, read, update, and delete blog posts. This issue will keep track of the implementation of the CRUD features that will serve as a base for features added later.

• #2
• #3
• #4
• #5

refer to Metallifax/bjjt-blog-backend#2

Should be able to pull the available blog post data into the editor that the user can then edit and update.

Currently, if the user leaves the Router context (refereshes the page), the state resets and the user is logged out, requiring user to sign in each time. Will research solutions later.

Should have its own component for this and doesn't require user information yet, just basic functionality.

• #21
• #22
• #23

Will be used for both the signup and login process later

Documenting this error for later, happens on both my Mac and Ubuntu machine. It would be nice to docker compose in local development but not necessary. Wish list item.

bjjt-blog-frontend-ui-1  | Starting the development server...
bjjt-blog-frontend-ui-1  | 
bjjt-blog-frontend-ui-1  | Failed to compile.
bjjt-blog-frontend-ui-1  | 
bjjt-blog-frontend-ui-1  | EACCES: permission denied, mkdir '/usr/src/app/node_modules/.cache'
bjjt-blog-frontend-ui-1  | assets by path static/js/*.js 5.96 MiB
bjjt-blog-frontend-ui-1  |   asset static/js/bundle.js 5.95 MiB [emitted] (name: main) 1 related asset
bjjt-blog-frontend-ui-1  |   asset static/js/node_modules_web-vitals_dist_web-vitals_js.chunk.js 6.93 KiB [emitted] 1 related asset
bjjt-blog-frontend-ui-1  | asset index.html 1.67 KiB [emitted]
bjjt-blog-frontend-ui-1  | asset asset-manifest.json 458 bytes [emitted]
bjjt-blog-frontend-ui-1  | orphan modules 219 KiB [orphan] 170 modules
bjjt-blog-frontend-ui-1  | runtime modules 31.8 KiB 16 modules
bjjt-blog-frontend-ui-1  | modules by path ./node_modules/ 4.21 MiB 925 modules
bjjt-blog-frontend-ui-1  | modules by path ./src/ 610 KiB
bjjt-blog-frontend-ui-1  |   modules by path ./src/components/ 597 KiB 25 modules
bjjt-blog-frontend-ui-1  |   modules by path ./src/*.js 4.84 KiB 3 modules
bjjt-blog-frontend-ui-1  |   modules by path ./src/*.scss 3.56 KiB 2 modules
bjjt-blog-frontend-ui-1  |   ./src/App.jsx 2.74 KiB [built] [code generated]
bjjt-blog-frontend-ui-1  |   ./src/features/editor/editorSlice.js 1.75 KiB [built] [code generated]
bjjt-blog-frontend-ui-1  | asset modules 4.4 KiB
bjjt-blog-frontend-ui-1  |   data:image/svg+xml,%3csvg xmlns=%27.. 281 bytes [built] [code generated]
bjjt-blog-frontend-ui-1  |   data:image/svg+xml,%3csvg xmlns=%27.. 279 bytes [built] [code generated]
bjjt-blog-frontend-ui-1  |   data:image/svg+xml,%3csvg xmlns=%27.. 161 bytes [built] [code generated]
bjjt-blog-frontend-ui-1  |   data:image/svg+xml,%3csvg xmlns=%27.. 271 bytes [built] [code generated]
bjjt-blog-frontend-ui-1  |   + 12 modules
bjjt-blog-frontend-ui-1  | 
bjjt-blog-frontend-ui-1  | ERROR in EACCES: permission denied, mkdir '/usr/src/app/node_modules/.cache'
bjjt-blog-frontend-ui-1  | 
bjjt-blog-frontend-ui-1  | webpack 5.72.0 compiled with 1 error in 61293 ms

Create React App is notoriously bad at SEO. It might be a good idea to come up with a better solution or migrate to something like NextJS or Gatsby that uses the current UI while making use of the current back end.

The less I have to fiddle with SEO stuff, such as accessibility, the happier I will be. The dream is to be able to use things such as tags, titles, page content to create metadata.

As far as goals go, this would happen after the CRUD for blog posts are completed.

Talk about the use case, the minimum viable product (MVP), and the purpose of it. This might be a good place to start talking about the finished product/consider making it a production app that is indexed on Google to be used by others.

The problem right now is the fact that the README shows a very old, very non functional version of the app, whereas we're closer to a functioning blogging system currently.

When a good time would be to implement this: when the CRUD operations are finished for the blog posts.

Should save to an in memory array of objects, something simple for now.

Ties in with Metallifax/bjjt-blog-backend#5.

The backend is in a state where it is testable and able to be used to implement a rudimentary login/logout and authorization system. Since it uses JWTs as the authentication, it's about time to implement UI for:

• #16
• #17
• #18
• #19

Implementation Rules

• All should be done using Redux Thunk via Redux Toolkit
• User should NOT be able to do ANY of these operations without a valid JWT token created by the server (though READ is probably taken care of due to the login system).
• A User should not be able to delete or update another users post (obvious authorization stuff)
• Should start small, things like pagination or load on scroll for the read part should be taken care of later and dubbed as a new feature.

CRUD Operations

• #30
• #31
• #32
• #33

using this blog post as a guide

This should be a simple icon that just removes the blog post, ask "are you sure?" in a modal, and delete if yes. Again, not looking at user based deletion yet. Basic functionality first.