doc: Update terminology 'Integrations' to 'Extensions'

[dmaskasky]

Related Issues or Discussions

Resolves #2169

Summary

• Replace instances of integrations with extensions throughout the website documentation.
• Update navigation, headers, and section titles accordingly.
• Ensure consistency in term usage across all documentation pages.

Check List

• yarn run prettier for formatting code and docs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
jotai	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2023 6:04am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 73f4bf9:

Sandbox	Source
React	Configuration
React TypeScript	Configuration
React Browserify	Configuration
React Snowpack	Configuration
Next.js	Configuration
Next.js with custom Babel config	Configuration
React with custom Babel config	Configuration

[dai-shi]

I didn't realize when looking at #2169, but this gives me feel "Ecosystem" is too broad. Because, "SWC", "Babel", "Devtools" in "Tools" can also be considered as ecosystem. So, maybe we want a narrower term.

[dmaskasky]

I didn't realize when looking at #2169, but this gives me feel "Ecosystem" is too broad. Because, "SWC", "Babel", "Devtools" in "Tools" can also be considered as ecosystem. So, maybe we want a narrower term.

Hmm, what should we use instead?

[sandren]

Hmm, what should we use instead?

Thanks for the PR! "Extensions" is the first thing that comes to mind, but I'll let others chime in with suggestions as well. 🙂

[dmaskasky]

Thanks for the PR! "Extensions" is the first thing that comes to mind, but I'll let others chime in with suggestions as well. 🙂

21 ideas:

1. Add Ons
2. Community Add Ons
3. Community Enhancements
4. Community Extensions
5. Community Modules
6. Community Packages
7. Community Plugins
8. Ecosystem
9. Enhancements
10. Extensions
11. Modules
12. Packages
13. Plugins
14. Third-Party
15. Third-Party Add Ons
16. Third-Party Ecosystem
17. Third-Party Enhancements
18. Third-Party Extensions
19. Third-Party Modules
20. Third-Party Packages
21. Third-Party Plugins

[sandren]

@dmaskasky Let's go with "Extensions". Thanks! 🙂

[dai-shi]

@sandren Is it possible to have a redirect (for the website) from integrations to extensions to avoid "404"?

[dmaskasky]

@sandren Is it possible to have a redirect (for the website) from integrations to extensions to avoid "404"?
How is this done?

[dmaskasky]

[dmaskasky]

[sandren]

How is this done?

Redirects are handled in gatsby-node.js:

createRedirect({
  fromPath: `/docs/integrations/*`,
  toPath: `/docs/extensions/*`,
  isPermanent: false,
});

[dmaskasky]

How is this done?

Redirects are handled in gatsby-node.js:

createRedirect({
  fromPath: `/docs/integrations/*`,
  toPath: `/docs/extensions/*`,
  isPermanent: false,
});

This didn't work for me locally. I have included this in the PR. Could you please test this?

[dmaskasky]

Also, I could use some advice with git.

I am unsure why GH is reporting a conflict with docs/integrations/scope.mdx. I have already rebased.

jotai jotai-ecosystem-docs $ git fetch && git rebase origin/main
Current branch jotai-ecosystem-docs is up to date.
jotai jotai-ecosystem-docs $ git fetch upstream && git rebase upstream/main
Current branch jotai-ecosystem-docs is up to date.
jotai jotai-ecosystem-docs $ pwd       
/Users/davidmaskasky/Code/jotai

[sandren]

This didn't work for me locally. I have included this in the PR. Could you please test this?

It's not working in the deploy preview either. I think we'll need to add an explicit redirect for each integration -> extension like the utils -> utilities redirects above.

[dmaskasky]

This didn't work for me locally. I have included this in the PR. Could you please test this?

It's not working in the deploy preview either. I think we'll need to add an explicit redirect for each integration -> extension like the utils -> utilities redirects above.

That sounds like an unnecessary maintenance burden. Wildcards should work, not sure why they don't though. I don't have a lot of experience with Gatsby.