-
Notifications
You must be signed in to change notification settings - Fork 654
Docs update #502
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 update #502
Conversation
@gep13 @robdmoore thoughts on the docs updates. I like having them in the repo as people can PR. Later we can build a github.io page from that folder too. You can browse and have a read at https://github.com/JakeGinnivan/GitVersion/tree/DocsUpdate |
@JakeGinnivan so, does that mean we are not going to be using readme.io anymore? |
I have had a quick skim through this, but will need to dig into it deeper. From what I read, it looks good though! 👍 |
@JakeGinnivan did you see my question above? Cheers! |
Ah yeah. I think for the moment not using readme.io. Having docs outside the repo makes it hard to keep docs and pr's in sync. I also like having atom open just editing locally, it is easier than editing in the browser. |
My ideal scenario is having a deployment step which would push the docs into a new readme.io version. Then you take advantage of the versioned docs and can just build docs during a release. Then somehow having a process for updating the docs as well outside a release |
Totally agree, this would be ideal! |
Future Jake's problem :P |
Ported wiki docs and wrote a bunch of new docs