Skip to content

Commit a9dddb4

Browse files
committed
Expand intellisense page to general purpose editor support page
1 parent c1b7c71 commit a9dddb4

File tree

4 files changed

+35
-17
lines changed

4 files changed

+35
-17
lines changed

redirects.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -217,5 +217,6 @@
217217
"source": "/docs/typography-plugin",
218218
"destination": "https://github.com/tailwindlabs/tailwindcss-typography",
219219
"permanent": false
220-
}
220+
},
221+
{ "source": "/docs/intellisense", "destination": "/docs/editor-support", "permanent": false }
221222
]

src/navs/documentation.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ export const documentationNav = {
1313
href: 'https://github.com/tailwindlabs/tailwindcss/releases',
1414
},
1515
pages['upgrading-to-v2'],
16+
pages['editor-support'],
1617
pages['using-with-preprocessors'],
1718
pages['optimizing-for-production'],
1819
pages['browser-support'],
19-
pages['intellisense'],
2020
],
2121
'Core Concepts': [
2222
pages['utility-first'],

src/pages/docs/editor-support.mdx

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Editor Support
3+
description: Plugins and configuration settings that can improve the developer experience when working with Tailwind CSS.
4+
---
5+
6+
## Syntax support
7+
8+
Tailwind CSS uses a lot of custom CSS at-rules like `@tailwind`, `@apply`, and `@screen`, and in many editors this can trigger warnings or errors where these rules aren't recognized.
9+
10+
The solution to this is almost always to install a plugin for your editor/IDE for PostCSS language support instead of regular CSS. For example, VS Code has a [PostCSS Language Support](https://marketplace.visualstudio.com/items?itemName=csstools.postcss) plugin you can use that works great with Tailwind CSS.
11+
12+
In some cases, you may need to disable native CSS linting/validations if your editor is very strict about the syntax it expects in your CSS files.
13+
14+
15+
## IntelliSense for VS Code
16+
17+
The official [Tailwind CSS IntelliSense](https://marketplace.visualstudio.com/items?itemName=bradlc.vscode-tailwindcss) extension for Visual Studio Code enhances the Tailwind development experience by providing users with advanced features such as autocomplete, syntax highlighting, and linting.
18+
19+
<img src={require('@/img/intellisense.png').default} alt="" width={1344} height={672} />
20+
21+
- **Autocomplete**. Intelligent suggestions for class names, as well as [CSS functions and directives](/docs/functions-and-directives).
22+
- **Linting**. Highlights errors and potential bugs in both your CSS and your markup.
23+
- **Hover Previews**. See the complete CSS for a Tailwind class name by hovering over it.
24+
- **Syntax Highlighting**. Provides syntax definitions so that Tailwind features are highlighted correctly.
25+
26+
Check out the project [on GitHub](https://github.com/tailwindcss/intellisense) to learn more, or [add it to Visual Studio Code](vscode:extension/bradlc.vscode-tailwindcss) to get started now.
27+
28+
## JetBrains IDEs
29+
30+
JetBrains IDEs like WebStorm, PhpStorm, and others include support for intelligent Tailwind CSS completions in your HTML and when using `@apply`.
31+
32+
[Learn more about Tailwind CSS support in JetBrains IDEs &rarr;](https://www.jetbrains.com/help/webstorm/tailwind-css.html)

src/pages/docs/intellisense.mdx

Lines changed: 0 additions & 15 deletions
This file was deleted.

0 commit comments

Comments
 (0)