✨V1

.eslintignore

@@ -3,3 +3,9 @@ dist
 build
 .next
 artifacts
+.cache
+public
+
+# tmp
+examples/vue
+packages/vue

.eslintrc.yml

@@ -36,6 +36,7 @@ rules:
   react/prop-types: off
   react/display-name: off
   react/no-children-prop: off
+  react/react-in-jsx-scope: off
 
 settings:
   react: 

contributing.md

@@ -2,147 +2,7 @@
 
 Hi!  👋
 We’re excited that you’re interested in contributing!
-Take a moment to read the following guidelines.
-And thanks for contributing to **MDX**!  👏👌✨
 
-If you’re raising an issue, please understand that people involved with this
-project often do so for fun, next to their day job; you are not entitled to
-free customer service.
+[Read the guidelines][contributing]
 
-## Table of Contents
-
-*   [Questions](#questions)
-*   [Contributions](#contributions)
-    *   [Financial support](#financial-support)
-    *   [Improve documentation](#improve-documentation)
-    *   [Improve issues](#improve-issues)
-    *   [Give feedback on issues and pull requests](#give-feedback-on-issues-and-pull-requests)
-    *   [Write code](#write-code)
-*   [Running the tests](#running-the-tests)
-*   [Submitting an issue](#submitting-an-issue)
-*   [Submitting a pull request](#submitting-a-pull-request)
-*   [Project structure](#project-structure)
-*   [Releases](#releases)
-*   [Troubleshooting](#troubleshooting)
-*   [Resources](#resources)
-
-## Questions
-
-Please chat and ask questions on [spectrum][chat]!
-Jump in there and lurk, talk to us, and help others.
-
-## Contributions
-
-There’s several ways to contribute, not just by writing code.
-
-### Financial support
-
-It’s possible to support us financially by becoming a backer or sponsor of
-unified through [Open Collective][collective].
-With this support, we can pay for project leadership, finance non-coding work,
-or to do fun things for the community like getting stickers for contributors.
-You’ll be helping unified’s maintainers manage and improve existing projects,
-and additionally support our work to develop new and exciting projects, such
-as [micromark][].
-
-### Improve documentation
-
-As a user of this project you’re perfect for helping us improve our docs.
-Typo corrections, error fixes, better explanations, new examples, etcetera.
-Anything!
-
-### Improve issues
-
-Some issues lack information, aren’t reproducible, or are just incorrect.
-Help make them easier to resolve.
-
-### Give feedback on issues and pull requests
-
-We’re always looking for more opinions on discussions in the issue tracker.
-
-### Write code
-
-Code contributions are very welcome.  It’s often good to first create an issue
-to report a bug or suggest a new feature before creating a pull request to
-prevent you from doing unnecessary work.
-
-## Running the tests
-
-1.  `yarn`
-2.  `yarn bootstrap`
-3.  `yarn test`
-
-Tests for an individual package can be run as a yarn workspace:
-`yarn workspace remark-mdx test`.  To see what packages ar available to test
-you can list out all workspaces with `yarn workspaces info`.
-
-## Submitting an issue
-
-*   The issue tracker is for issues.  Use chat for support
-*   Search the issue tracker (including closed issues) before opening a new
-    issue
-*   Ensure you’re using the latest version of our packages
-*   Use a clear and descriptive title
-*   Include as much information as possible: steps to reproduce the issue,
-    error message, version, operating system, etcetera
-*   The more time you put into an issue, the better we will be able to help you
-*   The best issue report is a [failing test][unit-test] proving it
-
-## Submitting a pull request
-
-*   Non-trivial changes are often best discussed in an issue first, to prevent
-    you from doing unnecessary work
-*   For ambitious tasks, you should try to get your work in front of the
-    community for feedback as soon as possible
-*   New features should be accompanied with tests and documentation
-*   Don’t include unrelated changes
-*   Test before submitting code by running `yarn test`
-*   Write a convincing description of why we should land your pull request:
-    it’s your job to convince us
-
-## Project structure
-
-MDX is a monorepo that uses [lerna][].
-
-*   All packages are found in `./packages`
-*   All documentation is found in `./docs` and can be viewed with `yarn docs -- -o`
-*   There’s an `./examples` directory where examples for different tools and
-    frameworks
-
-## Releases
-
-In order to release a new version you can follow these steps:
-
-*   Draft a release for the next version (vX.X.X)
-*   Release a prerelease
-    *   `yarn lerna publish`
-    *   Select prepatch/preminor/premajor
-    *   Sanity check in a project or two with the prerelease
-*   `yarn lerna publish`
-*   Publish release on GitHub
-
-## Troubleshooting
-
-If you’re having issues installing locally you might need to run
-`yarn lerna exec yarn install` instead of `yarn bootstrap`
-([issue][lerna-install]).
-
-## Resources
-
-*   [Good first issues in the MDX repository](https://github.com/mdx-js/mdx/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
-*   [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
-*   [Making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190)
-*   [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
-*   [GitHub Help](https://help.github.com)
-
-[unit-test]: https://twitter.com/sindresorhus/status/579306280495357953
-
-[chat]: https://spectrum.chat/mdx
-
-[collective]: https://opencollective.com/unified
-
-[micromark]: https://github.com/micromark/micromark
-
-[lerna]: https://lernajs.io
-
-[lerna-install]: https://github.com/lerna/lerna/issues/1457
+[contributing]: https://mdxjs.com/contributing

docs/.eslintignore

@@ -0,0 +1,4 @@
+dist
+node_modules
+public
+.cache

docs/.gitignore

@@ -0,0 +1,2 @@
+.cache
+public