You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/blog/2024-05-30-prettier-plugin-collapse-whitespace/index.mdx
+2-2
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Now our Prettier plugin will handle this for you automatically, so you don't nee
34
34
35
35
## Removing duplicate classes
36
36
37
-
Our [VS Code extension](https://tailwindcss.com/docs/editor-setup#intelli-sense-for-vs-code) has warned you about duplicate class names for a long time, but now our Prettier plugin can remove those duplicate classes for you automatically.
37
+
Our [VS Code extension](https://v3.tailwindcss.com//docs/editor-setup#intelli-sense-for-vs-code) has warned you about duplicate class names for a long time, but now our Prettier plugin can remove those duplicate classes for you automatically.
38
38
39
39
<DuplicationDemo />
40
40
@@ -46,4 +46,4 @@ To start playing with these improvements in your own projects, just install the
46
46
$ npm i prettier-plugin-tailwindcss@latest
47
47
```
48
48
49
-
If you run into any issues, let us know on [GitHub](https://github.com/tailwindlabs/prettier-plugin-tailwindcss/)!
49
+
If you run into any issues, let us know on [GitHub](https://github.com/tailwindlabs/prettier-plugin-tailwindcss/)!
Copy file name to clipboardExpand all lines: src/pages/blog/building-the-tailwind-blog/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -258,7 +258,7 @@ There's an interesting library by Hashicorp designed to make it possible to trea
258
258
259
259
## Wrapping up
260
260
261
-
Overall, building this little site with Next.js was a fun learning experience. I'm always surprised at how complicated seemingly simple things end up being with a lot of these tools, but I'm very bullish on the future of Next.js and looking forward to building the next iteration of [tailwindcss.com](https://tailwindcss.com) with it in the months to come.
261
+
Overall, building this little site with Next.js was a fun learning experience. I'm always surprised at how complicated seemingly simple things end up being with a lot of these tools, but I'm very bullish on the future of Next.js and looking forward to building the next iteration of [tailwindcss.com](https://v3.tailwindcss.com/) with it in the months to come.
262
262
263
263
If you're interested in checking out the codebase for this blog or even submitting a pull request to simplify any of the things I mentioned above, [check out the repository on GitHub](https://github.com/tailwindcss/blog).
Copy file name to clipboardExpand all lines: src/pages/blog/hiring-a-design-engineer-and-staff-engineer/index.mdx
+2-2
Original file line number
Diff line number
Diff line change
@@ -45,8 +45,8 @@ Here are some real examples of projects you would have worked on in the last few
45
45
46
46
-**Design and build the [Tailwind Connect](https://connect.tailwindcss.com/) microsite** — including coming up with a unique Markdown-driven badge design experience.
47
47
-**Craft the [first components](https://catalyst.tailwindui.com/docs/dialog) for Catalyst** — our first fully-componentized React UI kit.
48
-
-**Build a tool for capturing videos for our [Showcase](https://tailwindcss.com/showcase) site** — to automate creating preview videos that feel like a real person scrolling through a site.
49
-
-**Build [interactive demos](https://tailwindcss.com/docs/height#dynamic-viewport-height) to explain dynamic viewport units** — to include in the documentation along with the release of Tailwind CSS v3.4.
48
+
-**Build a tool for capturing videos for our [Showcase](https://v3.tailwindcss.com//showcase) site** — to automate creating preview videos that feel like a real person scrolling through a site.
49
+
-**Build [interactive demos](https://v3.tailwindcss.com//docs/height#dynamic-viewport-height) to explain dynamic viewport units** — to include in the documentation along with the release of Tailwind CSS v3.4.
50
50
51
51
After you start, you'd work on upcoming projects like:
Copy file name to clipboardExpand all lines: src/pages/blog/tailwindcss-v3-4/index.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -421,7 +421,7 @@ To learn more about all this forced colors stuff, I recommend reading ["Forced c
421
421
422
422
---
423
423
424
-
If you've been paying close attention, you might be wondering about [Oxide](https://youtu.be/CLkxRnRQtDE?t=2146), the engine improvements we previewed at [Tailwind Connect](https://tailwindcss.com/blog/2023-07-18-tailwind-connect-2023-recap) this summer.
424
+
If you've been paying close attention, you might be wondering about [Oxide](https://youtu.be/CLkxRnRQtDE?t=2146), the engine improvements we previewed at [Tailwind Connect](https://v3.tailwindcss.com//blog/2023-07-18-tailwind-connect-2023-recap) this summer.
425
425
426
426
We'd originally slated those improvements for v3.4, but we have a few things still to iron out and so many of these other improvements had been piling up that we felt it made sense to get it all out the door instead of holding it back. The Oxide stuff is still coming, and will be the headlining improvement for the next Tailwind CSS release in the new year.
Copy file name to clipboardExpand all lines: src/pages/blog/tailwindcss-v4-beta/index.mdx
+3-3
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,13 @@ export const meta = {
12
12
13
13
{/*excerpt*/}
14
14
15
-
About eight months ago we [open-sourced our progress](https://tailwindcss.com/blog/tailwindcss-v4-alpha) on Tailwind CSS v4.0. Hundreds of hours of fixing bugs, soul-crushing backward compatibility work, and troubleshooting Windows CI failures later, I'm excited to finally tag the first public beta release.
15
+
About eight months ago we [open-sourced our progress](https://v3.tailwindcss.com//blog/tailwindcss-v4-alpha) on Tailwind CSS v4.0. Hundreds of hours of fixing bugs, soul-crushing backward compatibility work, and troubleshooting Windows CI failures later, I'm excited to finally tag the first public beta release.
16
16
17
17
{/*/excerpt*/}
18
18
19
19

20
20
21
-
About eight months ago we [open-sourced our progress](https://tailwindcss.com/blog/tailwindcss-v4-alpha) on Tailwind CSS v4.0. Hundreds of hours of fixing bugs, soul-crushing backward compatibility work, and troubleshooting Windows CI failures later, I'm excited to finally tag the first public beta release.
21
+
About eight months ago we [open-sourced our progress](https://v3.tailwindcss.com//blog/tailwindcss-v4-alpha) on Tailwind CSS v4.0. Hundreds of hours of fixing bugs, soul-crushing backward compatibility work, and troubleshooting Windows CI failures later, I'm excited to finally tag the first public beta release.
22
22
23
23
As I talked about when we published the first alpha, Tailwind CSS v4.0 is an all-new engine built for performance, and designed for the modern web.
24
24
@@ -31,4 +31,4 @@ There's so much more to say, but everything you need to get started is in the ne
31
31
32
32
[Get started with Tailwind CSS v4.0 Beta 1 →](/docs/v4-beta)
33
33
34
-
Start building and help us bullet-proof this thing for the stable release early in the new year.
34
+
Start building and help us bullet-proof this thing for the stable release early in the new year.
Copy file name to clipboardExpand all lines: src/pages/careers/design-engineer/index.mdx
+2-2
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,9 @@ Here are some real examples of projects you would have worked on in the last few
32
32
-**Design and build the [Tailwind Connect](https://connect.tailwindcss.com/) microsite** — including coming up with a unique Markdown-driven [badge design](https://res.cloudinary.com/tailwind-labs/image/upload/w_1536/connect/tailwind-connect-2_qrjpj0.jpg) experience.
33
33
-**Craft the [first components](https://catalyst.tailwindui.com/docs/dialog) for Catalyst** — our first fully-componentized React UI kit.
34
34
-**Build out our recent [Studio template](https://studio.tailwindui.com/)** — a new agency website template we designed, built with Next.js and Framer Motion.
35
-
-**Build a tool for capturing videos for our [Showcase](https://tailwindcss.com/showcase) site** — to automate creating preview videos that feel like a real person scrolling through a site.
35
+
-**Build a tool for capturing videos for our [Showcase](https://v3.tailwindcss.com//showcase) site** — to automate creating preview videos that feel like a real person scrolling through a site.
36
36
-**Redesign and build the [Headless UI documentation site](https://twitter.com/steveschoger/status/1745816291351425068)** — rethinking the overall branding and making the site feel more modern and consistent.
37
-
-**Build [interactive demos](https://tailwindcss.com/docs/height#dynamic-viewport-height) to explain dynamic viewport units** — to include in the documentation along with the release of Tailwind CSS v3.4.
37
+
-**Build [interactive demos](https://v3.tailwindcss.com//docs/height#dynamic-viewport-height) to explain dynamic viewport units** — to include in the documentation along with the release of Tailwind CSS v3.4.
38
38
-**Create [custom installation graphics](https://twitter.com/steveschoger/status/1697352379694240029) for the Catalyst documentation** — that feel like a screenshot but with more control over highlighting what's important for the reader.
39
39
40
40
After you start, you'd work on upcoming projects like:
Copy file name to clipboardExpand all lines: src/pages/careers/staff-software-engineer/index.mdx
+2-2
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ We're a small multidisciplinary team and you'd have a wide variety of responsibi
28
28
Here are some real examples of projects you would have worked on in the last few months:
29
29
30
30
-**Create a [Rust library](https://github.com/tailwindlabs/tailwindcss/blob/0ee3508179966a767b7802a7262bb9d4ce2221da/oxide/crates/core/src/lib.rs) for extracting utility class names** — a tool that can scan an entire directory of template files as fast as possible and extract potential class names in parallel.
31
-
-**Add support for [composing variants](https://tailwindcss.com/blog/tailwindcss-v4-alpha#composable-variants) in Tailwind CSS** — make it possible to author classes like `group-has-peer-focus:underline` without an explicit `group-has-peer-focus` variant.
31
+
-**Add support for [composing variants](https://v3.tailwindcss.com//blog/tailwindcss-v4-alpha#composable-variants) in Tailwind CSS** — make it possible to author classes like `group-has-peer-focus:underline` without an explicit `group-has-peer-focus` variant.
32
32
-**Write a [fast CSS parser](https://github.com/tailwindlabs/tailwindcss/blob/0ee3508179966a767b7802a7262bb9d4ce2221da/packages/tailwindcss/src/css-parser.ts) in TypeScript** — to parse only the exact amount of detail needed by Tailwind's internals, looking for domain-specific shortcuts to make it significantly faster than existing libraries for our needs.
33
33
-**Fix an issue with [scroll-locking](https://github.com/tailwindlabs/headlessui/pull/2891) in Headless UI** — to make sure scrollable elements in dialogs can still be scrolled on iOS.
34
34
-**Set up [GitHub Actions workflows](https://github.com/tailwindlabs/tailwindcss/blob/0ee3508179966a767b7802a7262bb9d4ce2221da/.github/workflows/release-oxide.yml) for compiling our Rust libraries** — configure our release pipeline to properly build and distribute our native packages for each supported platform.
@@ -41,7 +41,7 @@ Here are some real examples of projects you would have worked on in the last few
41
41
After you start, you'd work on upcoming projects like:
42
42
43
43
-**Develop a Tailwind CSS bundler plugin for Next.js** — to generate your CSS using the module graph instead of scanning the file system, working with our contacts at Vercel to get it right.
44
-
-**Create a JavaScript library for running Tailwind CSS v4.0 in the browser** — an updated version of our [Play CDN](https://tailwindcss.com/docs/installation/play-cdn) library that uses our new engine under the hood, with a focus on making it as small as possible.
44
+
-**Create a JavaScript library for running Tailwind CSS v4.0 in the browser** — an updated version of our [Play CDN](https://v3.tailwindcss.com//docs/installation/play-cdn) library that uses our new engine under the hood, with a focus on making it as small as possible.
45
45
-**Design a set of IDE integration APIs for Tailwind CSS** — first-class, stable, documented APIs that editor teams like JetBrains can rely on to add things like completions, lint warnings, class sorting, and more to their tools.
46
46
-**Design, build, and document a Tooltip component for Headless UI** — making sure it's fully accessible, with a flexible but delightful API.
47
47
-**Build a backwards compatibility layer for Tailwind CSS v4.0** — re-introduce support for JavaScript configuration files, explore codemod tooling, and make sure existing community plugins are as compatible as possible with the new engine.
0 commit comments