Please describe your proposed solution.
We are targetting, in particular, users and projects that want to build on Cardano but have almost no development skills to implement their solutions. CardanoPress bridges this gap immensely and documentation to guide the users through the process will see more use the plugin along with use of Cardano.
We have partial documentation to help new users install and configure the CardanoPress plugin as of now but more is required to explain its functionality and examples of implementing the various features for Cardano-based projects.
Our current documentation and knowledge base can be found on our website:
Creating more details instructions on how to implement all the features and various use cases is required to help users implement and customise their solutions.
A competent WordPress developer would be able to build and extend all that we have created with the limited documentation we have provided, but many don't know what WordPress is, nor do they know where to start.
This set of documentation will take any user from a novice to a competent builder with the CardanoPress plugin.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
Providing documentation and instructions for users will help them implement their projects.
As a development tool for builders, we'll see more NFT projects, stake pool operators and other projects building on Cardano take up the plugin to create innovative websites around the Cardano blockchain.
We want our documentation to make it as easy as possible for anyone to pick up our plugin and start building.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
Ideally, we should be creating the documentation based on the stable version of the core plugins and themes. Currently, the core plugin is still in BETA.
Creating documentation against the BETA version will require rework to keep them up to date.
To help mitigate the risk of excessive work, it may be best to complete the documentation fully after the stable version of the plugin is released.