Skip to content
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

Ansible docs sprawl #119

Closed
infovore opened this issue Sep 13, 2019 · 7 comments
Closed

Ansible docs sprawl #119

infovore opened this issue Sep 13, 2019 · 7 comments
Assignees
Labels

Comments

@infovore
Copy link
Contributor

@infovore infovore commented Sep 13, 2019

The Ansible documentation is getting really long.

This thread on lines is in part about a perceived issue that came down to

  • a change in default behaviour after a firmware update
  • ...that they couldn't find an explanation of how to alter in the documentation
  • ...despite it actually being documented.

Ansible now has... five apps, MIDI support, Teletype docs, USB disk mode docs, and further notes. This is a lot for one page, and the monome site's design means that headers aren't super-varied in their styling (despite header levels being well-used in the docs).

I propose that we break up Ansible into an 'index' page (with brief descriptions of the apps, and some global notes) as well as individual documentation pages for apps. This is also a good opportunity to review the docs properly, for inaccuracies, duplication, and also for consistency in terminology.

I'm happy to take the lead on this, but want to raise it with the community.

@dndrks dndrks self-assigned this Sep 13, 2019
@dndrks
Copy link
Collaborator

@dndrks dndrks commented Sep 13, 2019

@infovore , I just mentioned this to @tehn yesterday -- there was a Kria support request that made clear the need for some optimization. excellent timing and thank you for opening the issue!

I love the idea to split the apps into separate doc pages, which is also in line with a plan to create short video demonstrations of parameters/functions within each app.

happy to share the work if you're able, but can also totally take this on. I've already self-assigned, let me know!

@dndrks dndrks added the enhancement label Sep 13, 2019
@infovore
Copy link
Contributor Author

@infovore infovore commented Sep 13, 2019

I think I'd like to take a pass at this - I enjoyed working on the Ansible docs last time, and I wrote a pile of the docs for Ansible-Earthsea too. It's likely it's going to be a bit of a running branch whilst we fettle it - I don't think it's just a case of cutting it into six!

One question, which @tehn might be able to answer: is there an easy way of previewing how the docs will look in the monome site itself?

(one note: I am on vacation the next two weeks, but I might still do some prodding. but it becomes easier to work on this in October).

@infovore
Copy link
Contributor Author

@infovore infovore commented Sep 13, 2019

(might be worth kicking off a 'project' - there are some things where I'd like review etc of)

@dndrks dndrks added this to To do in ansible docs revamp Sep 13, 2019
@dndrks
Copy link
Collaborator

@dndrks dndrks commented Sep 13, 2019

sounds great! happy to do whatever's needed, just let me know :)
https://github.com/monome/docs/projects/1

@infovore
Copy link
Contributor Author

@infovore infovore commented Sep 13, 2019

Annoyingly, it looks like I can't add tickets to a project - I wasn't quite sure how that worked on repos I'm not a collaborator on. No worries, there's not a burning issue just yet. Although I've kicked off my own branch for now and my own project, and I'll manage it there and maybe just submit PRs. We'll see.

@tehn
Copy link
Member

@tehn tehn commented Sep 13, 2019

@infovore added you as a collaborator!

@tehn
Copy link
Member

@tehn tehn commented Sep 13, 2019

there currently is not a great way to preview the monome.org docs.

but, they do look pretty similar to basically any markdown render. so you can use MacDown or something similar

@tehn tehn closed this Nov 10, 2019
ansible docs revamp automation moved this from To do to Done Nov 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants