Bones CMS is an easy to use content management system that can be customized and plugged into an existing website. It serves as an alternative to Wordpress or other paid services for a small business to include a blog on their website, which can help to drive traffic from search engines. This project is currently in development with the basic structure of accounts and posts in place.
This repo contains only the frontend code which makes calls to a completely separate backend API.
Bones frontend uses Vite for the React setup. The index.html file references main.jsx which in turn references App.jsx which contains the navbar and uses React Router to route to the particular pages and blog posts. The 'authenticated' state keeps track of whether a user is signed in or not. The frontend makes calls to the backend to retrieve session data and posts as well as to create, edit, and delete posts.
If you would like to install Bones frontend locally, make sure you first have Node.js installed on your system, which includes npm. You should also have a Github account so that you can fork the repo from this page and then clone your fork to your local system.
git clone https://github.com/YOUR-USERNAME/YOUR-FORKED-REPOSITORY-NAMEThen you should install all dependencies locally.
npm installNow make sure that you also have the React backend installed separately, and follow the installation instructions there, including setup for a Mongo database.
You will want to create a local .env file, filling in the values with your own. In development, your base url should be at your local host and any port you specified for the backend, otherwise 3000 by default. Additionally, please note that the backend endpoints are all at the root /api.
## .env file
## base url may look something like this- http://localhost:3000/api
VITE_API_BASE_URL=YOUR-BACKEND-ADDRESS-PLUS-/APITo host the frontend locally, you should launch it using npm.
npm run devNote the address and port of your hosted frontend, as you will need to plug that into the .env file on the backend for CORS reasons.
Features I would like to add:
- comments
- account roles
- an admin page
- customization options
- account verification by email
Currently Bones includes a navbar that I might like to get rid of except for on the admin page, such that the posts could easily fit into an existing website and it's structure and themes. It's nice to have in development though. I'm still envisioning how to best implement Bones with this kind of flexibility.
This version of Bones has been entirely created by me thus far, although a previous version using Express and EJS templates was created with assistance from @betodute. Thanks Beto!
If anyone is interested in contributing to this project, let's start with a conversation and then we could proceed to making an issue and I'd be happy to accept pull requests that fit well with the project!
Reach out to me at [email protected] with any questions, ideas, etc.!