-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[documentation update] Individual page audit #1220
Comments
I'm working on subtask 'testing'. |
Do I create a new PR for each subtask or should I create one PR when I'm done with all subtasks? |
Some of the pages are quite huge (like recipes). @dai-shi ultimately will be the one approving/merging them, so I'll leave it up to him (he's away for a few days, so there may be a delay over the weekend). |
I've worked on testing. Next, I'll work on autogenerating selectors, flux inspired practice, event handler in pre react 18, and immutable state and merging. I'll make a single PR for the changes I make to all five documents. |
Made a PR for the completed tasks here: #1231 Next, will be working on maps and sets usage, practice with no store actions, typescript, and updating nested state object values. Of course it will be in a separate PR. |
Yes, I will merge PRs. But if @chrisk-7777 approves PRs, it helps moving forward, so please feel free to do so. Also, I may explicitly request for reviews. |
Happy to review PRs. @Exalted100 I'll review later tonight 👍 |
#1231 Approved. Well written @Exalted100 |
Hi @chrisk-7777 and @dai-shi! I wanted to help with the documentation, but I wanted to ask you Chris to update the main comment if you find some time, so that it is clear which pages are left for audit. I also can review some future doc PRs if some help is still necessary. Cheers :) |
@sewera can do. I've had to be away for the last few weeks, but aiming to get things back on track this week. |
Thanks a lot, looking forward to be a part of this <3 |
Hi, just dropping in with a quick reminder :) |
Thanks @sewera ! As a starting point, can you review the integration section, including the following links:
Key things to look for:
In terms of working locally with the docs, I have a comment here that may help get started: #1033 (reply in thread) Feel free to split the above into 3 PR's or one, whatever is easiest for you. |
Thanks for the reply, really appreciate your guide, I'll start right away! |
- Make Zustand name always start from a capital letter, - Unify list formatting and description style, - Change minuses to em-dashes, - Change 3rd to third.
I managed to revise only the third-party libraries documentation page today. I opened a PR for it, so that you can start reviewing it right away @chrisk-7777 :) |
- fix case in naming, - check if the code snippets are up-to-date
- fix case in naming, - check if the code snippets are up-to-date
Hi @chrisk-7777, I saw that you've already been notified, but I'll gather all the information here:
Thanks for your help, it's a pleasure to collaborate with you :) |
- add cross-links - add line breaks for easier Markdown reading - unify Persist middleware spelling - change fishes to bears, because the plural of fish is fish, and it would be less readable - make sentences more concise
Hi @chrisk-7777 and @dai-shi! Please review it when you are free. Happy to be a part of it, cheers! :) |
* docs(#1220): revise persisting-store-data page - add cross-links - add line breaks for easier Markdown reading - unify Persist middleware spelling - change fishes to bears, because the plural of fish is fish, and it would be less readable - make sentences more concise * docs(#1220): make the sentences more concise * docs(#1220): unify formatting of methods
Thank you guys for collaboration and PR reviews, it's very fun working with you! |
Hi @chrisk-7777 and @dai-shi! The time has come for "v4 migrations" page. The PR is #1507. As usual, please review it when you are free. |
Thanks @sewera , really well written and explained. I haven't really been keeping on top of the docs audit and rollout as much as I would've liked. Mainly due to work commitments. If it's ok with Dai Shi, are you interested in becoming more of the "go to" person for the docs? I feel like you have a really good eye for detail and the overarching structure. |
* docs(#1220): rephrase introduction to v4 migration * docs(#1220): rephrase create function migration * docs(#1220): split migration for create function paragraph * docs(#1220): rename page to migrating to v4 * docs(#1220): restructure create function migration section * docs(#1220): restructure StateCreator migration section * docs(#1220): restructure PartialState migration section * docs(#1220): restructure and rephrase useStore function migration * docs(#1220): restructure all sections and reformat UseBoundStore and createContext * docs(#1220): fix applicable import for createContext * docs(#1220): rephrase persist middleware migration * docs(#1220): rephrase redux middleware migration * docs(#1220): simplify persist function migration
Sure, @chrisk-7777. However, I'm only available on Wednesdays, and I can dedicate up to 2 hours weekly. If it's fine with you, it's also fine with me. CC: @dai-shi |
Sounds reasonable. Let's cooperate together. |
From what I've seen so far, the documentation on the Pmndrs website |
I feel like the sites docs are now in a good enough state that we can close this issue, and continue to iterate on the docs as needed. |
That's exactly what I meant, I'm happy that we agree. |
Thanks you all for your contributions! |
Core conversation here: #1033
For each of the pages on the new documentation site, audit each page for clear, concise explanations, checking code snippets are correct, and conveys the correct information.
Blocked by #1215
Current list of pages, may change based on 1215 (above)
The text was updated successfully, but these errors were encountered: