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

Migrate wiki to main repo #730

Open
ringods opened this issue Mar 12, 2020 · 10 comments
Open

Migrate wiki to main repo #730

ringods opened this issue Mar 12, 2020 · 10 comments

Comments

@ringods
Copy link

ringods commented Mar 12, 2020

On one hand, Github wikis are a great thing. But on the other hand, one of it's drawbacks is that only repo maintainers have update access to the wiki.

In open source, contributions should also work for documentation. As a result, my request would be that one of the maintainers migrate all the wiki content into the main repo, e.g. in a docs folder.

Once the documentation is there, contributions to this documentation would follow the usual Pull Request pattern.

@RobLoach
Copy link
Collaborator

I'd be down. We could even publish rendered docs over with githubpages at http://twigjs.github.io/twig.js/ .

@ajiho
Copy link

ajiho commented Jun 23, 2024

Is there any progress on this issue? Perhaps I can help with this. I am familiar with using vitepress to generate beautiful documents, but my native language is not English. However, I can help generate a Chinese translation template so that you can transfer it to English yourself when the time comes?

@willrowe
Copy link
Collaborator

@ajiho contributions are welcomed. I think the plan is to have it published to github pages.

@ajiho
Copy link

ajiho commented Jun 24, 2024

@willrowe Of course, the deployment method can be chosen freely. I just want to get your opinion on whether to choose vitepress. I want to get your approval because there are too many tools for generating static documents. However, I personally highly recommend vitepress. If you want to see the document effect, you can check it out https://vitepress.dev/

@willrowe
Copy link
Collaborator

@ajiho I'd prefer vitepress since I'm familiar with Vue and Vite. Any thoughts @RobLoach?

@RobLoach
Copy link
Collaborator

I worry about spending more time on making/maintaining a docs site than writing the actual docs. The less code/dependencies the better.

@ajiho
Copy link

ajiho commented Jun 25, 2024

@RobLoach Don't worry about this, when using viteperss, you just need to focus on writing MD files. A good document can add points to the project, as I have reviewed previous issues and found that someone has already complained about the current document

@RobLoach
Copy link
Collaborator

Sounds good with me 😁

@willrowe
Copy link
Collaborator

@ajiho that's great that it will run on MD files. I think you're good to go ahead then.

@ajiho
Copy link

ajiho commented Aug 8, 2024

@willrowe @RobLoach

I took some time and completed it

see: #898

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

No branches or pull requests

4 participants