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

GitBook for this repository #52

Closed
cabreraalex opened this issue Apr 20, 2014 · 3 comments
Closed

GitBook for this repository #52

cabreraalex opened this issue Apr 20, 2014 · 3 comments

Comments

@cabreraalex
Copy link
Member

Recently a couple developers created Gitbook, an easy application which converts GitHub repositories into modern html websites. I recently set it up for the WIP CTF Resources, and I think it provides another way to read and make use of these great write ups.

@mathiasbynens has expressed that he likes the structure of the repository as folders, as it represents the culture of CTFs and is very intuitive and simple. The best part of creating a Gitbook for the repository is that the regular master branch would remain the same and function as it does now.

Since this repository is very large and will only continue to grow, I think it would be best to only have the most recent 3 or 4 CTFs presented in the book. That way the most visited write-ups can be found in an eye-pleasing layout, while if someone wants to see old write-ups they can look in the repository itself as they do now.

The only issue I see as of now is the build series for updating the book. So far I have had to rebuild the whole book and import the SUMARRY.md every time there is a change. This is a very tedious process, but once an easier method is found it would a very simple process to have the book updated from changes in the master branch repository.

@pawlos
Copy link
Contributor

pawlos commented Jul 12, 2014

I'm all for the idea! Any progress?

@cabreraalex
Copy link
Member Author

Hey, sorry for the very, very late response.

I've been looking back at this idea, but I think that at this point there are way too many challenges to be able to make a coherent book from. I've drifted towards having more of an INDEX structure as in issue #147

@mathiasbynens
Copy link
Member

Agreed. Still not a fan of bookifying this repo, but another index file would be nice, assuming someone wants to step up to maintain it.

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

3 participants