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

Convert repo to use Markdown #6

Open
adrianmcli opened this issue Feb 17, 2017 · 7 comments
Open

Convert repo to use Markdown #6

adrianmcli opened this issue Feb 17, 2017 · 7 comments

Comments

@adrianmcli
Copy link

adrianmcli commented Feb 17, 2017

@kennetpostigo I wouldn't mind helping you do this, but I'm not sure where to start. Can you give me a direction?

@kennetpostigo
Copy link
Owner

kennetpostigo commented Feb 17, 2017

Hey @adrianmcli , so the goal is to move everything over to gatsby. Which will allow us to use actual markdown but still be able to use react and mix both flavors together markdown for static content and use react components for dynamic content. The main blocker is that gatsby 1.0 is not done yet. 1.0 is an overhaul and large improvement over the current gatsby. It supports many of the features I am looking for:

  1. Easy and quick editing
  2. Offline reading
  3. Code splitting routes for small payloads
  4. Really fast pageloads
  5. Easy interop with react (maybe even rehydrate)
  6. Easier format for people to edit and add to the guide.

We can currently use gatsby 1.0 if you npm install -g gatsby@next however you would have to fork gatsbygram to use it and strip it down to a basic state that we can build on. I just haven't had the time to do this because of school and work. So using gatsby would be the start. I have all the content on gitbook.io in markdown format currently so it would literally be copy and paste when transitioning to gatsby and making 1.0 work for us is the main work that needs to be done.

@adrianmcli
Copy link
Author

Interesting. I can certainly try to strip down Gatsbygram. I suppose you are talking about this: https://github.com/saiikunst/gatsbyjs/tree/1.0/examples/gatsbygram

My only other question is whether or not we want to do this now, since they are still in alpha (I'd feel more comfortable if it was beta). Since you have all the Markdown ready-to-go, maybe my time would be better used going through the existing docs and marking typos and other issues.

@kennetpostigo
Copy link
Owner

@adrianmcli yea thats the one.

Yea definitely you can do that as well, just give me your email and I'll give you write permissions on the gitbook. Make sure you have a gitbook account tho

@adrianmcli
Copy link
Author

@kennetpostigo sure, the email under my GH profile is tied to a gitbook account.

@kennetpostigo
Copy link
Owner

check your email when you get a chance

@kennetpostigo
Copy link
Owner

kennetpostigo commented Mar 22, 2017

@adrianmcli hey so rdn has been made public it's not done but you can contribute to the content and functionality. There are issues open that are blockers to it going online. Let me know if you are still interested in helping out http://github.com/kennetpostigo/rdn

@adrianmcli
Copy link
Author

adrianmcli commented Mar 22, 2017 via email

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