Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.

Conversation

jeremistadler
Copy link
Contributor

@jeremistadler jeremistadler commented Jan 24, 2017

The README is becoming a bit crouded so I took the matter in hand 😄

Any other layout ideas?
Should we use the wiki instead?
All feedback is welcome! 🌮

@msftclas
Copy link

Hi @jeremistadler, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@msftgits
Copy link

Hi, I am closing and re-opening this PR to bump the CLA bot. Sorry for the inconvenience!

@msftgits msftgits closed this Jan 24, 2017
@msftgits msftgits reopened this Jan 24, 2017
@msftclas
Copy link

Hi @jeremistadler, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.

TTYL, MSBOT;

@jeremistadler
Copy link
Contributor Author

@geof90 @lostintangent @itsananderson
Have any spare time for this? 😄

@panarasi
Copy link

Hey @jeremistadler Thanks for the Pull request. We were tied up with fixing 0.40 bugs - I think this looks good.

@Silhouettes I want to merge this PR. Github also now allows gh-pages for the docs folder, so this could also help in automatically updating code-push docs.

@richardhuaaa
Copy link
Contributor

richardhuaaa commented Jan 26, 2017

@panarasi @jeremistadler - I've been meaning to go through this, I just wanted to figure out how the main website will reflect these changes (http://microsoft.github.io/code-push/docs/react-native.html), seeing as currently it's also a monolith, and yes it would be nice to have an auto-updating solution. Will give this some thought but also open to ideas! Tagging @buptkang also as this will be related to your work.

@jeremistadler
Copy link
Contributor Author

@panarasi @Silhouettes Thanks, I guess this PR will brake the site if merged as of now.

Considered other solutions such as gitbook or readthedocs?

@richardhuaaa
Copy link
Contributor

Thanks for the tip, we'll check it out! @buptkang has agreed to look at this as part of his work to synchronize the website with the GitHub docs. I've assigned this to him, and he will likely need approximately one week as he just needs to finish what he's currently working on.

Thanks so much for this @jeremistadler, this is a very thoughtful and useful contribution. Please let us know if you'd like us to get this done sooner.

Copy link
Contributor

@richardhuaaa richardhuaaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pending @buptkang's investigation into synchronizing the main website's docs with those on GitHub

@buptkang
Copy link
Contributor

buptkang commented Feb 9, 2017

I approved this document split PR. I have put the gulp script in the website repo to automatically synchronize the document change from this repo.

@buptkang buptkang merged commit bdf10ee into microsoft:master Feb 9, 2017
@richardhuaaa
Copy link
Contributor

Thank you @jeremistadler :)

@richardhuaaa
Copy link
Contributor

@buptkang - you might need to check if there have been any changes to the README since this PR was submitted, because they may not be reflected here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants