You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: