Preflight Checklist
Problem Description
There is currently no means by which a user can add their own custom conversion methods. In order to add functionality, they need to edit the BookPub source code itself.
Users need a way to add the conversions they need to fit their own publishing needs.
Proposed Solution
Add a folder "plugins" in the root of new bookpub projects where users can add their own cusotm conversion functions.
Plugins modules should include:
- a variable for the manuscript content
- a variable for options
- a convention for adding plugin options in the book.config.yml file
Alternatives Considered
Initially considered adding remark-directives and creating a folder called directives in the user's book project root. But it seemed a better option not to limit users to directives and unified only. They should be able to add any functionality they want, even if it is something outside the unified ecosystem.
Additional Information
No response
Can you help?
What aspects can you help with?
Contact Info 📧
No response
Preflight Checklist
Problem Description
There is currently no means by which a user can add their own custom conversion methods. In order to add functionality, they need to edit the BookPub source code itself.
Users need a way to add the conversions they need to fit their own publishing needs.
Proposed Solution
Add a folder "plugins" in the root of new bookpub projects where users can add their own cusotm conversion functions.
Plugins modules should include:
Alternatives Considered
Initially considered adding remark-directives and creating a folder called directives in the user's book project root. But it seemed a better option not to limit users to directives and unified only. They should be able to add any functionality they want, even if it is something outside the unified ecosystem.
Additional Information
No response
Can you help?
What aspects can you help with?
Contact Info 📧
No response