|Number of watchers on Github||2023|
|Number of open issues||30|
|Average time to close an issue||about 1 month|
|Average time to merge a PR||about 17 hours|
|Open pull requests||15+|
|Closed pull requests||8+|
|Last commit||over 1 year ago|
|Repo Created||over 3 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||cdmedia|
|Do you use cms.js? Leave a review!|
|View open issues (30)|
|View cms.js activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
UPDATES COMING SOON!
Check out a working demo here
CMS.js currently supports two website modes, Github and Server.
This is the default mode for CMS.js. Host your website on Github using Github Pages, similar to Jekyll.
Use server mode if you choose to self host your content. Apache and NGINX servers are supported. If using server mode, make sure the server's directory indexing feature is enabled.
htaccessis enabled OR
Options Indexesis set for your directory.
autoindex onis set for your directory
More info on server setup is available on the wiki
git clone https://github.com/cdmedia/cms.js.gitor download the latest release
js/config.jsto your liking
js/config.jsif using Github mode
gh-pages(Github's default branch for hosting)
In Github mode, CMS.js uses the Github API to get the content of your gh-pages repo and serve them as a full website.
In Server mode, CMS.js takes advantage of the Server's Directory Indexing feature. By allowing indexes, CMS.js sends an AJAX call to your specified folders and looks for Markdown files. After they are found, it takes care of everything else and delivers a full website.
Once CMS.js is installed and running, simply copy all of your posts from your Jekyll
_post folder to your designated CMS.js posts folder.
Copy all of your Markdown pages from your Jekyll projects root folder into your designated CMS.js pages folder.
You can find the list of contributors here.