-
Notifications
You must be signed in to change notification settings - Fork 51
Add DocC documentation for swiftly #131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Create a plugin and tool that can generate a CLI reference for swiftly and generate the current latest document. Organize the help into a GSG (Getting Started Guide), a selection of HOWTOS, and Reference topics. Write an initial version of each. Create a Swift Package Index metadata file so that swiftly can be submitted there once the documentation is ready. Update the RELEASING.md file to check the documentation sanity and command-line reference, regenerating it if necessary.
@swift-server-bot test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to bring this plugin to argument parser for other users too!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we not able to use the standard docc plugin for generating documentation?
This one is highly specialized to suit swiftly at the moment. Perhaps it can be generalized to suit any project in the future. |
The docc plugin is being used here to generate the documentation. It appears to me that this might be the first time that someone has attempted to generate a command-line reference from the argument parser to docc. |
@swift-server-bot test this please |
@swift-ci test macOS |
Co-authored-by: Adam Fowler <adamfowler71@gmail.com>
@swift-ci test macOS |
Create a plugin and tool that can generate a CLI reference for swiftly and generate the current latest document.
Organize the help into a GSG (Getting Started Guide), a selection of HOWTOS, and Reference topics. Write an initial version of each.
Create a Swift Package Index metadata file so that swiftly can be submitted there once the documentation is ready.
Update the RELEASING.md file to check the documentation sanity and command-line reference, regenerating it if necessary.