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

command list redundancy #42

Open
rabbah opened this issue Jan 14, 2021 · 3 comments
Open

command list redundancy #42

rabbah opened this issue Jan 14, 2021 · 3 comments

Comments

@rabbah
Copy link
Contributor

rabbah commented Jan 14, 2021

there’s some redundancy between https://docs.nimbella.com/commands and https://docs.nimbella.com/command-summary.

@rabbah
Copy link
Contributor Author

rabbah commented Jan 14, 2021

also Nim should be nim or Nimbella CLI in the left nav bar although the heading might just be better called Commands.

@joshuaauerbachwatson
Copy link
Contributor

there’s some redundancy between https://docs.nimbella.com/commands and https://docs.nimbella.com/command-summary.

I noticed that. The first is stale and represents a way that first I, and then Nancy in her rewrite, thought to present the command set of nim in a more friendly way. The second is less stale (I probably should regenerate it but it's nearly correct). Also less friendly.

IMO we should, for now, connect only the command-summary to the sidebar toc. Though less friendly, it's at least complete-ish as a reference. The commands doc could be morphed into a better "overview of nim" kind of doc that does not attempt to list any commands completely (because that tends to go stale instantly).

I assume there is no invariant that says that every document in the repo has to be connected to the TOC. That would make it too hard to revise things. Once commands is detatched from the TOC, I can work on it (and other documents that represent the breakup of nim.html) to be more appropriate and the reconnect to the TOC (in a PR of course, because I suspect that the structure of the PR will be a discussion point for all of us for a long while ... it's inherently hard to get that right).

@rabbah
Copy link
Contributor Author

rabbah commented Jan 14, 2021

I assume there is no invariant that says that every document in the repo has to be connected to the TOC.

There isn't. There are orphaned files (place holders now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants