revamp oxlint

[Boshen]

• revamp sidebar
• revamp content

[netlify]

✅ Deploy Preview for oxc-project ready!

Name	Link
🔨 Latest commit	da0a016
🔍 Latest deploy log	https://app.netlify.com/projects/oxc-project/deploys/6954ec745c01fd000877a98e
😎 Deploy Preview	https://deploy-preview-745--oxc-project.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[connorshea]

I had some notes I wrote a little bit ago about a migrate-from-eslint page, if this is any use to you:

This is intended for existing JavaScript/TypeScript projects that currently use ESLint and want to move to Oxlint to get overall better performance.

Cover the following main topics:

- Use @oxlint/migrate to migrate your ESLint flat config to an oxlint config with all supported rules ported over. 
    - If you use tseslint, ensure you pass the `--type-aware` flag.
    - If you use plugins not supported natively in oxlint, use the `--js-plugins` flag.
- If you're not on a flat file ESLint config, you may need to manually convert your config file.
- Alternatively, use oxlint-eslint-plugin to disable rules already supported by oxlint, and run both in CI until all rules you need have been ported to oxlint.
- Similar misc notes to the prettier migration doc: Update relevant contribution docs, agents.md, CI configs, VS Code repo settings, recommended editor extensions, etc.

[connorshea]

I also have some notes for a "known differences with ESLint" page, if you think that's worth adding.

Differences to note in this page include:

• Some disable directive differences (cannot configure rules to use different config options via code comments, cannot adjust severity level via code comments).
• No flat file config support.
• Not all rules are supported natively yet, but many are and porting is continuing to happen pretty quickly.
• Glob differences, for how globs get resolved if there are rule config options that take glob arguments. Also impacts glob patterns for the files field on overrides in the oxlint config.
• Regex differences due to using Rust instead of JS. Some rules may have behavioral differences if they have regex config options and are configured with fairly complex regex patterns.
• CLI differences: passing globs for that should be linted cannot be done consistently as there's no support for passing a string glob for oxlint to evaluate currently.
  • The glob pattern gets evaluated by your shell if you don't put it inside quotation marks, and so the resulting files that get linted may differ across platforms/shells.
  • Ignore patterns should generally be specified in an ignore file or the Oxlint config, rather than specifying what files to lint via an allowlist glob pattern in the CLI command.
• Only supports linting JS/TS/JSX for now, limited support for Vue/Astro/etc. and only in <script> tags.
• For JS Plugins, see the dedicated JS Plugins page for any differences specific to JS Plugins.
• Type-aware lint rules only support projects that have been updated for compatibility with TS7, see the type-aware page for details.
• No bulk suppression support currently.
• There may be behavioral differences in the import plugin rules, depending on the way you have configured import resolution for the ESLint import plugin.
• Not all settings have been implemented for the native plugins. If you have settings that modify behavior for specific ESLint plugins/their rules, you may see differences in lint violations on your project. We'd like to support most settings from the original plugins, so please open an issue if any missing settings are important for you.

[Boshen]

@connorshea notes taken. I removed migration and comparison pages from this PR.