* Final draft of getting started
* Final draft of introduction page
* Update menu and tab styling.
* update vscode recommended extension list to include markdown
* formatting
* minor language/tone update
* Add a note about meta capabilities
* refine intro of getting started guide
* Add prettier formatting for MDX files.
* Refine getting started page. Factor out code and text fragments which are useful on other pages.
* fix link styling in admonition blocks
* write the depenedency management how-to guide
* Darken the background for light-mode inline "code" blocks
* docs(changeset): Another round of additions and refinments to the documentation website.
* further refine light-mode code-box shadows
* Add missing "tool for that" link
* Update type-safety to show new "moduleSuffixes" option in version 4.7.
* Minor tweaks to dependency-management guide. Remove unneeded includes. Text polish. Fix link to PR page in rnx-kit.
* Add a guide on bundling. Include placeholder pages for some tools which the bundling guide links to.
* Add placeholder pages to left nav.
* Fix tree shaking references. Don't use the hyphen.
* docs(changeset): Fix references to tree shaking. Remove the hyphen.
* docs(changeset): Add bundling guide. Polish existing web pages. Add placeholder pages for some tools packages (needed by bundling guide).
* remove old change file
* Start with all side-bar categories expanded to make content more discoverable.
* Remove warning banner
* Add arch overview page. Add dep-check arch page (material from dep-check README and DESIGN files). Add empty dep-check tool page, since it is referenced in dep-check arch page.
* Make the code of conduct more approachable by using sentences instead of bullet points.
* Copy and polish the text from Contributing.md to the website. Once the site goes live, the contributing page will be a mostly-empty redirect to the site. The site has better rendering capabilities, and will generate a side-nav rather than relying on a TOC at the top of the document.
* Add a resources page. Also add an "image with text" for that page. Fix link styling so its less restrictive. Add twitter logo.
* fix changeset
* Remove hyphen from pull request.
* Remove links which don't add value to the current article/guide (e.g. they can be googled easily, as needed). Keep links to content that is not covered but critically important. Also, keep links that refer to the rnx-kit repo.
* Remove unneeded outbound links
* PR feedback
* Remove old changesets
* Re-add changefiles
* update change files
* use code-block titles instead of top-line comments in dependency management arch doc
* Create a docusaurus plugin which lets us process markdown files in the monorepo, outside of the docsite project. Create an MDX plugin to remove ranges of markdown based on start/end comments, and add that plugin to the docusaurus plugin.
* Add a website page for each publish package's README. Exclude the badges and title. Replace the title with the package name, but without @rnx-kit (which crowds out the left nav).
* Change README-include approach from using JSX imports to using a remark plugin.
* Fix plugin paths. Update contributing so it appears in both the normal location in the source tree and on the web site.
* Change styling for selected left-nav items. Stop using bold as it changes the text-width significantly, causing a shift in the word-wrapping.
* Update the tools and architecture overview pages. Move all tools pages from a 'packages' parent dir to a 'tools' parent dir.
* Refine resources page. Add discord profile link
* Tweak the text at the top of the getting started page
* Add the first blog post announcing the launch
* docs(changeset): Website and README updates
* Change file
* Update docsite/src/components/Image.tsx
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
- `change` remains mostly the same. The difference now is that we select
the packages that should have the same change log entry. Where we used
to specify `--type none`, we can do `yarn change --empty` instead.
- `publish:beachball` was split into `version:changesets` (for bumping
version numbers) and `publish:changesets` (actually publishing).
Rather than having to run `yarn build` or `yarn build-scope` from
workspace root, we can now run `yarn build --dependencies` within any
package. This allows us to stay within the package we're currently
working on.
* Update top-level README
* Fix link
* fix link
* Fix type
* Update language regarding status of rnx-kit and our support statement.
* Update config package docs
* Update READMEs using automation
* Remove parameters which have no effect in Metro.
* fix typos
* Write a CLI readme file. Update RN CLI docs. Remove unused CLI options.
* update generated tables in readme
* fix typo
* add notes on contributing and releasing
* fix dep-check generated package versions
Tommy Nguyen
Sparsha Saha
Doston Nabotov
Adam Foxman
Lorenzo Sciandra
Adam Foxman