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

Add documentation #645

Open
madnight opened this issue May 17, 2017 · 7 comments
Open

Add documentation #645

madnight opened this issue May 17, 2017 · 7 comments
Labels

Comments

@madnight
Copy link

@madnight madnight commented May 17, 2017

you could start to copy some docs together like:
https://wiki.archlinux.org/index.php/Bspwm
https://github.com/IntrepidPig/bspwm-doc/blob/master/getting-started.md

@neeasade
Copy link
Contributor

@neeasade neeasade commented May 22, 2017

Is the end goal with this issue a user guide?

@madnight
Copy link
Author

@madnight madnight commented May 22, 2017

@neeasade anything like this https://i3wm.org/docs/

It don't have to be sooo nice documented (no need for screenshots and hundred of examples), but a basic version of that (10-20%) would be the required minimum. A simple list of all commands with a short desc (that is provided through the man page) is not enough.

I would start the documenation as gh-page branch on github allowing for free github hosting (bswpm.github.io) and collaborative documenation in markdown syntax.

As for example https://www.slant.co/versus/1290/6620/~i3_vs_bspwm many people like i3 because it has an excellent documenation, i3 lacks gaps, so people are willing to install a fork called i3-gaps instead of switching to bspwm that allows for even better gaps settings.

@madnight
Copy link
Author

@madnight madnight commented May 25, 2017

I created a basic example with mkdocs
The setup is very simple i called mkdocs new bspwm edited the mkdocs.yml to link into doc folder and executed mkdocs gh-deploy
madnight@dd62c15

Result: https://madnight.github.io/bspwm/

@jameskr97
Copy link

@jameskr97 jameskr97 commented Jul 16, 2017

@baskerville I wanted to add some wiki pages. I was going to start by moving things from the doc/ folder to the wiki, but one question I have is, what is the difference between a domain and a command? I looked through the man page, and they seem like two names referencing the same thing.

@baskerville
Copy link
Owner

@baskerville baskerville commented Jul 16, 2017

Yes: the two terms refer to the first argument given to bspc.

In the original spec, the first argument was called command.

But I recently introduced the term domain, because, in the following example: node --close, the command is --close, not node. So node is a collection of commands acting on similar objects, and I'm calling that a domain.

I think query, config, subscribe and quit can be considered commands, and everything else is a domain.

@badele
Copy link

@badele badele commented Mar 1, 2018

Hi,

I have begined a project that generate automatically a bspwm documentation. Actually, i have made a new project, i don't know if legitimate include in the main bspwm project.

You can see the animated result animated or the documentation result

The project available here

@phenax
Copy link

@phenax phenax commented Mar 19, 2020

+1
Really missing some good documentation for the config and all the bspc commands

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

Successfully merging a pull request may close this issue.

None yet
6 participants