Announcing the creation of a simple-to-use CMS engine built on top of the Safenetwork.
I’ve begun the development of a React/Node CMS engine styled around Wordpress - I’m aware of the already existing Safepress project, however I’m wary that it’s been in development for a few years now.
The project will allow the following:
- Creation of a host / safe network domain for your blog
- Creation, updating and deleting of posts (stored as MutableData objects)
- Creating a custom template to wrap the posts
- (or) Selecting between a few simple pre-made (but customisable templates)
Should the user decide to create their own template, they will only have to create HTML, JS and CSS, the conversion process from flat content to the compiled template file will be performed automatically when publishing your template (including linting, error checking, etc, to ensure no PUTs are wasted.)
The home page of your blog will be a post listing page which will have to be updated every time a new post is created (or an old post deleting). As such, the PUT cost of actions on posts will be as follows:
- Creation: 2 PUTS
- Editing: 1 PUT
- Deletion; 2 PUTS
The PUT cost of actions on templates will be as follows:
- Creation: 1 PUT
- Editing: 1 PUT
Persistence and efficiency
To reduce the number of PUTS required (and the read strain on the SAFE network) the posts & templates will be persisted simultaneously to the editor’s local file system, allowing posts to be in a “draft” state where the user can edit and view their own posts, reducing the edit cost from (1 PUT per modification) to (1 PUT for publishing).
The fantastic Safe NodeJS app library will be used for persisting MutableData objects to the SAFE network.
The first release candidates with this core functionality (code on Github, executables) will be available by the end of February.
Shane Armstrong (@shane)
Software engineer with 6 years experience of building massively scale-able web applications in Rust and PHP5/7.
Andy Alban (@AndyAlban)
Frontend software developer with experience building React applications.
Thank you for reading.