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

Suggestion to add content #12

Open
gbraad opened this issue May 31, 2016 · 5 comments
Open

Suggestion to add content #12

gbraad opened this issue May 31, 2016 · 5 comments

Comments

@gbraad
Copy link

gbraad commented May 31, 2016

Some time ago I created a presentation that details some of the commands offered by iproute2.

https://gbraad.gitlab.io/tools-training/slides.html#/iproute2

Have a look and tell me what you think is valuable for me to propose as pull requests.

@dmbaturin
Copy link
Owner

Hi! Thanks, I'll have a look and get back to you.

@FilBot3
Copy link

FilBot3 commented Feb 5, 2017

Could this also be possibly transitioned into a GitBook? I think it would do really well at that.

@dmbaturin
Copy link
Owner

Gitbook? No. Just no. For starters, the "free for open source" plan allows no more than five collaborators. Second. I would rather not trust a closed cloud service if I want something to stay around even if I get eaten by a grue, with the current setup and workflow making mirrors of either the page or the git repo is trivial.

@gbraad
Copy link
Author

gbraad commented Feb 7, 2017

@dmbaturin It can be seen as a way to structure the archive. Adding a file called SUMMARY.md is all that is needed. My own knowledge-base project gets pushed to github pages, from https://gitlab.com/gbraad/knowledge-base/ as a CI runner.

Example SUMMARY.md: https://gitlab.com/gbraad/knowledge-base/blob/master/SUMMARY.md... and when run with something like https://github.com/gbraad/dockerfile-gitbook-server or https://github.com/getwarped/s2i-gitbook-server turns into http://gbraad.nl/knowledge-base/

Note: I think this issue can be closed... WDYT?

@gbraad
Copy link
Author

gbraad commented Feb 7, 2017

@predatorian3 I think the suggestion should first be; convert to markdown and let GitHub pages handle with publication. The current delivery of a HTML-file is not easy to deal with from a contribution standpoint, especially since HTML can be generated. Add a template file, let Jekyll handle the generation. This would also allow easier migration to a possible GitBook-structure... at the moment, the benefit is too little to consider this....

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

3 participants