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

docs(manual): Initial draft of the user manual #16

Draft
wants to merge 18 commits into
base: master
Choose a base branch
from
Draft

docs(manual): Initial draft of the user manual #16

wants to merge 18 commits into from

Conversation

akirak
Copy link
Member

@akirak akirak commented Jan 30, 2022

No description provided.

@akirak
Copy link
Member Author

akirak commented May 7, 2022

I have added some contents, but documentation still has a lower priority.

@akirak akirak force-pushed the doc branch 2 times, most recently from df6aa92 to 90fede3 Compare May 7, 2022 05:30
@brsvh
Copy link

brsvh commented Jan 4, 2024

Is this PR work still going on?

@akirak
Copy link
Member Author

akirak commented Jan 4, 2024

Is this PR work still going on?

I'm thinking of discarding this PR. Now I generally don't like the idea of containing documentation in the repository as the source code, especially for Nix projects. That way, the user would have to update the flake input every time the documentation is updated, which is undesirable.

Instead, my plan is as follows:

  • Create a separate repository for the user documentation, to which a broader audience can contribute. Hyprland Wiki is a source of inspiration.
  • Containing only ADRs in the source repository.

@brsvh
Copy link

brsvh commented Jan 4, 2024

Your considerations sound quite reasonable.

I've recently been using Twist to manage my configurations and have recommended it to my friends. To some extent, I always get lost in the source code, which is quite annoying. I noticed that you already have a github.io site, perhaps you could consider setting up a documentation entry for Twist there.

@akirak
Copy link
Member Author

akirak commented Jan 4, 2024

To some extent, I always get lost in the source code, which is quite annoying.

@terlar currently maintains a working configuration built with twist, which you could use as a reference. Sorry for not putting an effort on the documentation side. If you have any question, please ask at Discussions.

I noticed that you already have a github.io site, perhaps you could consider setting up a documentation entry for Twist there.

I am still thinking about how to integrate documentation with the website. Some decisions would be involved.

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

Successfully merging this pull request may close these issues.

2 participants