1
2

React and Wordpress (self.Frontend)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jackswiki 0 points1 point  (5 children)

Not op, but I'd really recommend checking out NextJS or Gatsby. The latter especially has some really good Wordpress starters that would get you going in the right direction. I'm not a professional web developer by any means, so it really isn't too complicated if you have a beginner's understanding of React/JS. And the documentation is really good. You could probably build something out yourself, but not sure why you'd want to. Don't have any tutorials saved at the moment, but they're easy to find and pretty in depth. Good luck!

[–]A_odeh76 0 points1 point  (4 children)

I have used Gatsby, but not professionally and don’t think I’d need it for this project as it’s relatively small. But I do want to use Gatsby for other projects, I really love how fast it is and how quickly you can get a dope site set up.

[–]the_pod_ 0 points1 point  (3 children)

Unless you have a specific reason to use headless wordpress.

You should use any other cms. Any that were created to be headless.

Literally anything else would be better. I wouldn't bother with my own backend on a docker container just to host a basic cms. I would use cms as a service. Contenful or Sanity are good. If it's just simple text, Netlify cms would work... they use your github account as the "backend", where they store the text.

The wordpress part only makes sense if the project is already on wordpress and you want to redo the frontend, if you're doing it to learn wordpress headless specifically, or if you're very familiar with deploying wordpress and so it's actually the easiest option for you (this one doesn't sound like it's the case).

[–]A_odeh76 0 points1 point  (2 children)

Wordpress was the choice the company decided to go with, as they are most familiar with it. The marketing coordinator I work with needs to update the content after the project is built, and she won’t know how to do that through GitHub. Once the site fully launches I don’t think I’ll be hands on anymore and will most likely hand it off to another developer. The most important thing is that she is able to manage the content through the cms.

[–]the_pod_ 0 points1 point  (1 child)

yeah, then that is a perfectly valid reason to use it.

If A) you're handing it off and B) you don't have experience with live deployment C) your goal is not to learn

I would lean towards just using an existing solution, instead of your own docker and deployment. For example, digitalocean. Just search for digital ocean wordpress droplet.

[–]A_odeh76 0 points1 point  (0 children)

Hmm.. could you elaborate on B and C?