-
Notifications
You must be signed in to change notification settings - Fork 294
fix #152 improve documentation #222
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
Conversation
Auto commit by GitBook Editor
Auto commit by GitBook Editor
Auto commit by GitBook Editor
Auto commit by GitBook Editor
Auto commit by GitBook Editor
|
Are those checkboxes still outstanding? Let me know when I should start review (might be not be until this weekend on my end). |
|
Also is there a URL where I can see the docs site? |
Auto commit by GitBook Editor
|
@yangmillstheory yea this is just a starting point for the PR. Nowhere near finished. Here is where you can find the new docs site. Once I am close to finished I guess we will have to discuss getting |
Auto commit by GitBook Editor
Auto commit by GitBook Editor
Auto commit by GitBook Editor
Auto commit by GitBook Editor
Auto commit by GitBook Editor
|
@yangmillstheory https://redux-actions.js.org/ I think the DNS still needs to be configured though. |
|
What do you mean that the DNS still needs to be configured? js-org/js.org#1333 looks like it created the CNAME to your gitbook URL. Later we can self-host the site using GitHub Pages (I emailed @acdlite and CC'ed you). For now, thanks for hosting. I can take another look tonight; is there anything else you would like to include? |
|
Gitbook was giving me an error when I configured it. But maybe you are right. In my experience you usually have to wait a little while for the records to update, so I figure that is why gitbook is upset. Doing one last look over can't hurt. Thanks for all the help by the way. It has been greatly appreciated. |
|
No problem; this is a huge win for the project, thanks for taking the initiative. |
|
Does the Edit functionality work now? |
build/gitbook.css
Outdated
| @@ -0,0 +1,3 @@ | |||
| .token.operator { | |||
| background: none; | |||
| } | |||
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.
Should this folder be checked in? Actually this directory is checked in. But why is this file here - locally this directory contains just a couple of files for me:
preset-es2015.jsuse-lodash-es.js
| "docs:prepare": "gitbook install", | ||
| "docs:build": "npm run docs:prepare && gitbook build -g acdlite/redux-actions", | ||
| "docs:watch": "npm run docs:prepare && gitbook serve", | ||
| "docs:publish": "npm run docs:clean && npm run docs:build && cp CNAME _book && cd _book && git init && git commit --allow-empty -m 'update book' && git checkout -b gh-pages && touch .nojekyll && git add . && git commit -am 'update book' && git push git@github.com:acdlite/redux-actions gh-pages --force" |
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.
Does this need to be run separately from npm publish? Can we use the postpublish hook to run this?
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.
Well I guess technically just because you are releasing a new version of the library on npm doesn't necessarily mean you are releasing new documentation. If you want it to be part of that process though I don't see why it couldn't be added to postpublish. I added that more for convenience in case you wanted it on gh-pages like we planned.
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.
OK it's up to you, we can leave it out for now. By the way, how will this work if I want to publish new documentation, since it's hosted in your gitbook URL? Do we need to grant access to developers of this repo until @acdlite sets up pushing to GitHub pages (I don't have access to the repository settings)?
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 have given both you and @acdlite full administrative privileges over the gitbook. We will likely want to get it done the other way asap so others can be able to contribute without requiring access.
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 agree; it's up to him to respond to the email at this point.
|
@vinnymac just a couple of questions: |
|
The Edit functionality is pointing to |
|
OK, will merge by midnight.
On Sun, Jul 2, 2017 at 8:51 PM Vincent Taverna ***@***.***> wrote:
The Edit functionality is pointing to master right now, so that won't
work unless we merged it to master. I could have it point to my fork, but I
don't think that is what we want. So we either merge it to master or we
merge it to a separate branch and link to that one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#222 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACmkd39wil6S6NUrlwoucuzVUG7JyKIUks5sKGVUgaJpZM4OIC86>
.
--
Victor Alvarez
|
|
Hm, some of the links are broken - try clicking around on the documentation site from the home page. |
|
@vinnymac I just pushed the fixes to |
|
@yangmillstheory somehow the links were pointing to I could always transfer ownership of the entire gitbook to you. But I can't seem to find a way to switch from one repository to another because I don't see EDIT EDIT 2 |
|
Thanks. I can't connect your GitBook to this repo (don't have access to the settings page, and the integration is configured there). I guess we'll just have to wait for a response from @acdlite. It's the holiday after all though. So it looks like the current fix is to fix it your repo, and merge the changes back here (won't do anything but keep things in sync). |
|
@vinnymac for now, is there a place others can submit documentation PRs to to update the redux-actions.js.org? |
|
@yangmillstheory try to contact him on Twitter. I assume he has muted this repo. |
|
@yangmillstheory if you make a PR to the master branch of vinnymac/redux-actions it will automatically update the docs once merged. Until acdlite responds I guess that is just how it will have to be done. |
|
Will do tim, I actually emailed him at the address on his profile. |
The goal here is to improve documentation. Both the documentation and the user experience around that documentation require changes.
redux-actions.js.orgNew Documentation Demo