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

Move documentation to readthedocs.org #1

Open
KoditkarVedant opened this issue Jun 13, 2018 · 11 comments
Open

Move documentation to readthedocs.org #1

KoditkarVedant opened this issue Jun 13, 2018 · 11 comments

Comments

@KoditkarVedant
Copy link

Hello @joemcbride,

I've gone through the graphql-dotnet document but I feel the current document doesn't look good. I think we should move our documentation to https://readthedocs.org/

If you say yes, I would like to work on this.

@joemcbride
Copy link
Member

I have been looking at either https://vuepress.vuejs.org/ or https://www.gatsbyjs.org/ as an alternative. Vuepress looks a bit easier to use out of the box, though I prefer React and I like that Gatsby is React+GraphQL.

This repo is the statically generated site, the actual docs currently live here: https://github.com/graphql-dotnet/graphql-dotnet/tree/master/docs , which is using st-docs. Admittedly I'm a bit adverse to readthedocs due to the python dependency.

The docs can get a quick facelift with just a little bit of html + css tweaks with the existing files if that is currently your main concern?

@KoditkarVedant
Copy link
Author

KoditkarVedant commented Jun 14, 2018

The alternatives are good. Yup, we can get a quick facelift with ccs tweaks but we need to maintain it. Why invest time in it as we get all this handled for us out of the box. What do you think?

We can use the https://www.gatsbyjs.org/. I didn't have a liking for readthdocs it just that I only aware of that.

@joemcbride
Copy link
Member

With Gatsby you still have to "bring your own" html + css, so that would still be work that has to be done.

https://medium.com/squadlytics/how-we-switched-to-documentation-as-code-with-gatsby-js-and-netlify-part-1-2-1f57ad732a05

@KoditkarVedant
Copy link
Author

Oh. I thought Gatsby must be providing some default document template which we could use.

@joemcbride
Copy link
Member

@joemcbride
Copy link
Member

Image preview:

newdocs

@joemcbride
Copy link
Member

And the new docs are live! They still need some re-org, but at least they look tons better. At least I think so. https://graphql-dotnet.github.io/

@KoditkarVedant
Copy link
Author

@joemcbride, Docs look Awesome!. I tried to run the docs2 on my local machine but facing some problems, I think now it should work. Let me know if I can help.

@KoditkarVedant
Copy link
Author

I am seeing this error when I try to run docs locally

image

@joemcbride
Copy link
Member

joemcbride commented Jul 28, 2018

Not sure what that error means. Seems pretty generic.

Are you running on macOS or Windows?

Run gatsby info or gatsby info --clipboard in the gatsby project directory and paste its contents here.
Not working? You may need to update your global gatsby-cli - npm install -g gatsby-cli

Here’s a few people with the same issue:
gatsbyjs/gatsby#3183

@KoditkarVedant
Copy link
Author

I am running on Windows. I will look into those options.

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

2 participants