-
Notifications
You must be signed in to change notification settings - Fork 799
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
[WIP] GitHub Pages: Getting Started, Migrating, etc. #260
Conversation
I (mistakenly) put a lot of stuff in the |
@hedgerh I merged in the stuff that I mistakenly put in the non-gh-pages docs, and that @tsaiDavid helped with, to |
Sounds good. I'm going to spend some time on the docs now. |
I'm filling out step 1/3 now. |
@tsaiDavid Has any of your work been lost, or is what is available here up to date? |
@hedgerh - Pinged you on gitter - but I just spun up jekyll. Since the docs aren't going to be in plain markdown, the 'jsx' syntax highlighting is not going to work properly. But it looks like everything else is there! |
@tsaiDavid, oh yes, sorry, I meant to mention that I had to @tsaiDavid, @hedgerh, I also enabled GFM for the markdown engine and as you saw, in the latest version of the engine we can do GFM style code fences, so no more missioning with the long jekyll syntax for that. The CSS is a bit different though. I might have to take a step back until next week, but I'll follow the progress and chip in where I can. jekyll drove me crazy today :D |
Hey @hedgerh, @tsaiDavid, can you give an update on anything you guys discussed and/or are working on? Let's try finish this up in the next few days if possible, now that we're already in beta. |
…UIDE @tsaiDavid / @hedgerh, hope this doesn't affect anything you haven't commited yet, just trying to get things ready for an initial publish. I can't remember which of you did the webpack config with your comments, but yes, I agree, better to not be overbearing; so I removed comment and left things identifiable but minimal.
@gaearon, what are your thought on the current state of the docs or in particular the getstarted guide? I setup a preview of the branch at http://rhl-docs.gadi.cc:4000/react-hot-loader/getstarted/ and of course you can comment on the lines here. Maybe better to get the guide online and do further work later? The two "XXX" sections could be cleaned up quite easily (when do you plan to merge the |
Hi, thanks for your work! I’ll take a look when I get some time but likely not earlier than next weekend. |
getstarted.md
Outdated
|
||
This tutorial assumes that you already have a working Webpack configuration and `WebpackDevServer` compiles and serves your code. If youʼd rather play with a ready-made example, try <a href="https://github.com/gaearon/react-hot-boilerplate" target="_blank">react-hot-boilerplate</a>. | ||
## Boilerplate Example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this heading is a little confusing, since the first sentence introduces the getting started content, but this paragraph is actually about the boilerplate. I think "Introduction" would be great, or something that essentially says "Want a quick start? Try the boilerplate." in a clearer voice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. If you're already working on this, feel free to just change it. Don't forget to pull in the changes from the other PR first though.
getstarted.md
Outdated
|
||
**XXX cleanup, details** | ||
If you only render on the client, this is the easier option and quicker to setup. The key aspect of this configuration is that when creating a `new WebpackDevServer`, you need to specify `hot: true` as an option. For example, you can add an entirely new file called `server.js` and simply include the [server provided in the boilerplate](https://github.com/gaearon/react-hot-boilerplate/blob/master/server.js){:target="_blank"}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, you can add an entirely new file called
server.js
and simply include the server provided in the boilerplate.
At first, I didn't realize you meant to just copy the boilerplate's server.js
into my project. Maybe we could rewrite this paragraph to:
If you're only rendering on the client side, this is the easier option, and quicker to setup. You can simply copy the
server.js
from the boilerplate into your project. The key aspect of this configuration is that when creating anew WebpackDevServer
, you need to specifyhot: true
as an option.
and then maybe just include the server.js
code as a codeblock. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. I actually thought you wrote this :D All the Webpack stuff is either you, @tsaiDavid, left over from before, or just me summarizing what was already there. In general I might be a bit useless for the Webpack stuff, since I don't use or know Webpack. So consider all your views on the Webpack stuff as absolute :)
Grammar fixes.
@gaddic @tsaiDavid Been pretty busy, but took some time to review the Getting Started guide. It's looking great! I made some typo fixes in another PR and left some line comments. I think something weird happened and I commented on a specific commit for a few different comments :O Another thing I noticed is that the links are kind of hard to distinguish from regular text. I completely missed the links to the boilerplate's |
@hedgerh, great stuff! Yeah it's pretty hectic doing this amongst other work but I think we're doing a great job :) Yeah it did say one was on an outdated diff... if you left a github tab open, sometimes they don't update... when I do this I've gotten into the habit of ctrl-R before commenting. Agree. Links should be real links, not formatted as code. As per other comment, if you're working on this now, feel free to fix (I switched the other links to markdown for consistency), otherwise we'll do it. Here are the two issues that either of us can check off when done :)
|
@gadicc I'm working on this now. I can take care of both of these. :D |
Did a lot of work on the |
This hasn't been worked on in 10 months, and I'm thinking that we probably won't need a separate website for docs. The surface API of RHL is pretty small, and markdown files in the repository are more suitable IMO. Also, we already cover most of the copy in this PR. Let me know if anyone disagrees, otherwise we can close this. |
4089a9b
to
ad9d620
Compare
Hi all, this PR is tracking all current work on the docs for gh-pages (that will replace http://gaearon.github.io/react-hot-loader/).
Additional PRs are welcome against the
gh-pages-next
branch, which will be squashed before the final merge. Please mention this issue (#260) in your PR so everyone involved in docs will be notified.See also https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/.
(This is the continuation of #255)
See also #257 for the non-gh-pages docs that live in the repo.