Writerside supports generating API docs from OpenAPI and Swagger specifications.
There are two main problems that documentation authors may have with API docs:
Generated API documentation is usually a separate website from the rest of your documentation. This can lead to difficulties in maintaining a cohesive and integrated documentation set that provides a holistic view of your product or service.
When trying to integrate API documentation with the rest of your content, this usually requires manual editing to enhance the autogenerated reference with manually written parts.
To address these issues, Writerside offers a solution that combines the benefits of automatic API documentation generation from OpenAPI and Swagger specifications with a seamless integration into your overall document content.
note
Be aware of the following limitations in the current implementation:
Only the following component types are supported: schemas, parameters, and responses. If you need support for other types, comment or create a subtask of WRS-2998.
Markdown is supported only for descriptions of endpoints. Markdown descriptions for objects and responses are not supported yet. See WRS-3507.
OpenAPI specifications can be quite complex. If you notice that something important for you is not supported, look for a relevant ticket in our issue tracker and vote for it or create a new feature request.
Writerside provides several built-in project templates including a template with a sample API documentation project.
Create a new API documentation project
Writerside provides a built-in template with a sample API documentation project that you can use as an example or starting point.
In the Welcome to Writerside dialog, click New Project.
If you already have a project open, select File | New Project from the main menu.
In the New Project wizard, select API Docs.
Specify the name and location for your new project and click Create.