react-ka-ching v0.23.0

react-ka-ching

This is the code to generate a NextJS React App using WordPress JSON API

What does this do?

I have been working on creating a complete web CMS archetecture using the greatest technologies on the web today. This will spin up a new NextJS React App complete with tooling for VSCode. It will then create a Wordpress CMS instance to manage products, images, blogs and all other CMS related data.

The WordPress installation uses WooCommerce under the hood to manage products. The NextJS App uses the WP-JSON API to get the data it needs to display on the frontend.

Check out the WordPress code here.

Check out the NextJS code here.

See a complete working demo here.

This is working and needs more 💓

If you would like to use this to boostrap your architecture you might need my help as the documentation is still lacking. I'm working on ironing out the user experience for the developers, and will have documenation very soon.

If you need a helping hand, please schedual some time on my calendly.

This code is open source so if you can make it better, please open a PR!

– Roe Greene

Running

To create a new app: npx react-ka-ching

To seed product data using the amazon affiliate api: npx react-ka-ching --seed

To skip questions and use default answers: npx react-ka-ching--skip

TODO

[] create function to map values to client package.json

[] create function to map wordpress envs in wp-config.php

[] create function to setup wordpress with initial data (plugins etc)

[] create function to deploy to production using aws and vercel

[] add ability to pause, delete and rerun seeds

[] Update wordpress

[] Set localhost to http://localhost:80 in the admin wp url

[] Make sure to set permalinks to the last option in the wp settings

[] Update the git url for IAGMFT (move to new repo change name/readme of project to react-ka-ching-next)

[] Merge server and client into 1 mono project with package json at the root

[] Remove todo section of IAGMFT project

[] Add docker tags to build commands so server doesnt keep having conflicts

[] Add env.example file so it doesnt get ignored

[] Name folders from client to project-name-client and project-name-server

[] Give option to not have wordpress and use express server instead

[] Map tokens to readme to autofill values in client server readmes

[] Delete the .git folder after pulling each repository

[] Run commands to automatically setup repostory if url is provided

git init
git remote add origin <repoURL>
git pull origin main
git add .
git commit -m "initial commit"
git push -u origin main