-
Notifications
You must be signed in to change notification settings - Fork 257
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
0.2.0-beta manual #348
Comments
I'm down to help with this however I can. Just a few ideas/questions as well:
|
@neilwillgettoit I'm going to aim for mostly a top-level application usage specific overview for the first pass. Case-specific stuff like how-to guides will be handy once you can reference steps back to the manual pages instead of having to explain the entire process each time as well. I'll probably try to reference as much of the pothos guides as I can to fill in some parts of the build guides eventually; I definitely am duplicating some build instructions, etc. on some of my pages that would be better suited to the soapy module wikis. The manual this spec is for is actually issue #248 so check that out as a rough outline of what I'm planning. |
Just tinkering with http://cubicsdr.readthedocs.io/ at the moment :) |
Looks pretty good; I've set up a repository for it https://github.com/cjcliffe/CubicSDR-Manual which makes it nice and simple to manage contributions. |
Very nice Charles, good job. Read the docs should fit right into the workflow that is already applied; easy to contribute (pull requests). |
@neilwillgettoit thanks for your help; I've restructured the Index a bit and have been working on the overview for the Main Application Window; work-in-progress is at http://cubicsdr.readthedocs.io/en/latest/application-window.html |
See issue #248 for more information about the manual's content
Now using ReadTheDocs for generating the manual, thanks @neilwillgettoit for getting it rolling.
CubicSDR Manual Repository:
CubicSDR Manual Repository Output:
Checklist:
The text was updated successfully, but these errors were encountered: