Skip to content

Conversation

@vinnymac
Copy link
Contributor

@vinnymac vinnymac commented Jun 28, 2017

The goal here is to improve documentation. Both the documentation and the user experience around that documentation require changes.

New Documentation Demo

@vinnymac vinnymac changed the title Docs Site fix #152 improve documentation Jun 28, 2017
@yangmillstheory yangmillstheory self-requested a review June 28, 2017 20:00
@yangmillstheory
Copy link
Contributor

Are those checkboxes still outstanding? Let me know when I should start review (might be not be until this weekend on my end).

@yangmillstheory
Copy link
Contributor

Also is there a URL where I can see the docs site?

@vinnymac
Copy link
Contributor Author

vinnymac commented Jun 28, 2017

@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 redux-actions.js.org setup.

vinnymac added 6 commits June 29, 2017 14:27
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
@vinnymac
Copy link
Contributor Author

vinnymac commented Jul 3, 2017

@yangmillstheory https://redux-actions.js.org/

I think the DNS still needs to be configured though.

@yangmillstheory
Copy link
Contributor

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?

@vinnymac
Copy link
Contributor Author

vinnymac commented Jul 3, 2017

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.

@yangmillstheory
Copy link
Contributor

No problem; this is a huge win for the project, thanks for taking the initiative.

@yangmillstheory
Copy link
Contributor

Does the Edit functionality work now?

@@ -0,0 +1,3 @@
.token.operator {
background: none;
}
Copy link
Contributor

@yangmillstheory yangmillstheory Jul 3, 2017

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.js
  • use-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"
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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)?

Copy link
Contributor Author

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.

Copy link
Contributor

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.

@yangmillstheory
Copy link
Contributor

@vinnymac
Copy link
Contributor Author

vinnymac commented Jul 3, 2017

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.

@yangmillstheory
Copy link
Contributor

yangmillstheory commented Jul 3, 2017 via email

@yangmillstheory yangmillstheory merged commit a99796b into redux-utilities:master Jul 3, 2017
@yangmillstheory
Copy link
Contributor

Hm, some of the links are broken - try clicking around on the documentation site from the home page.

@yangmillstheory
Copy link
Contributor

@vinnymac I just pushed the fixes to master; how can I push the changes to your gitbook?

@vinnymac
Copy link
Contributor Author

vinnymac commented Jul 3, 2017

@yangmillstheory somehow the links were pointing to /api instead of /docs/api. Not sure what happened exactly, but I ended up updating vinnymac/redux-actions/tree/master to the latest and pointing gitbook at that branch and it seems to have fixed the issue for me.

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 acdlite/redux-actions in the list on the settings page. If you navigate here can you try to link it to this repository instead of mine? May be a permissions thing.

EDIT
Oh weird, so I guess I didn't fix it. If you go directly to the documentation site the links work fine. But for some reason if you use the links in the main README.md on the bottom it throws the whole thing off. Maybe we should try updating those links to be absolute paths.

EDIT 2
Yea if you look at how redux-saga does it, they point directly to the html file on the docs site, and not the relative markdown. I'll make a new PR to fix it.

@yangmillstheory
Copy link
Contributor

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 vinnymac deleted the docs branch July 3, 2017 18:05
@yangmillstheory
Copy link
Contributor

@vinnymac for now, is there a place others can submit documentation PRs to to update the redux-actions.js.org?

@timche
Copy link
Member

timche commented Jul 8, 2017

@yangmillstheory try to contact him on Twitter. I assume he has muted this repo.

@vinnymac
Copy link
Contributor Author

vinnymac commented Jul 8, 2017

@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.

@yangmillstheory
Copy link
Contributor

Will do tim, I actually emailed him at the address on his profile.

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

Successfully merging this pull request may close these issues.

3 participants