Skip to content

Commit 6ef28a5

Browse files
committed
fix: clean up code formatting and update dependencies in blog posts
1 parent e61d8aa commit 6ef28a5

File tree

4 files changed

+17
-19
lines changed

4 files changed

+17
-19
lines changed

apps/www/content/blog/installing-tailwind-css.mdx

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,6 @@ Alright, this next part is the most critical step of the entire process. Serious
9797

9898
Open up your `tailwind.config.js` file and find the `content` array. You need to add paths to every single file that might contain a Tailwind class—HTML files, JavaScript components, you name it.
9999

100-
101100
```ts
102101
/** @type {import('tailwindcss').Config} \*/
103102
export default {
@@ -176,9 +175,8 @@ The real key is modifying your `tailwind.config.js`. You need to point the `cont
176175

177176
```ts
178177
// tailwind.config.js
179-
/** @type {import('tailwindcss').Config} */
178+
/** @type {import('tailwindcss').Config} \*/
180179
export default {
181-
182180
content: ["./index.html", "./src/**/\*.{js,ts,jsx,tsx}"],
183181
theme: {
184182
extend: {},
@@ -201,7 +199,7 @@ The only significant difference is the `content` path in `tailwind.config.js`. Y
201199

202200
```ts
203201
// tailwind.config.js
204-
/** @type {import('tailwindcss').Config} */
202+
/** @type {import('tailwindcss').Config} \*/
205203
module.exports = {
206204
content: [
207205
"./pages/**/_.{js,ts,jsx,tsx,mdx}",
@@ -288,7 +286,6 @@ First, you'll need to install the package:
288286

289287
Then, just require it inside the `plugins` array in your config file.
290288

291-
292289
```ts
293290
// tailwind.config.js
294291
module.exports = {

apps/www/content/blog/next-js-getting-started.mdx

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,9 @@ Before you dive in, just make sure you have **Node.js version 18.17 or later** i
5555

5656
To get the ball rolling, navigate in your terminal to wherever you want your new project to live. Then, run this single command:
5757

58-
```bash
5958
npx create-next-app@latest
60-
```
6159

62-
This kicks off an interactive setup process that will walk you through a few questions. It's a great way to customize the project to your specific needs right from the get-go.
60+
This kicks off an interactive setup process that will walk you through a few questions. Its a great way to customize the project to your specific needs right from the get-go.
6361

6462
> Answering these prompts thoughtfully is your first big step. The choices you make here—like using TypeScript or setting up Tailwind CSS—will shape your development workflow from day one.
6563
@@ -164,7 +162,7 @@ Now that you have a couple of pages, you need a way for people to get between th
164162

165163
To connect your homepage to the about page, you'll import `Link` from `next/link` and use it almost exactly like a regular `<a>` tag. If you want to dive deeper into building a complete navigation bar, there are some great tutorials on building a [navbar in React.js](https://magicui.design/blog/navbar-in-react-js) that you can easily adapt.
166164

167-
Here's a quick example of how you could add a link to your `app/page.tsx`:
165+
Heres a quick example of how you could add a link to your `app/page.tsx`:
168166

169167
```tsx
170168
// app/page.tsx

apps/www/content/blog/tailwind-css-button.mdx

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -221,13 +221,16 @@ Here’s the basic skeleton:
221221
```tsx
222222
// A basic structure for a reusable Button component
223223
function Button({ children, variant = 'primary', size = 'md', ...props }) {
224-
// We'll add class logic here const baseClasses = 'font-semibold rounded-lg shadow-md focus:outline-none focus:ring-2 focus:ring-offset-2';
224+
// We'll add class logic here
225+
const baseClasses = 'font-semibold rounded-lg shadow-md focus:outline-none focus:ring-2 focus:ring-offset-2';
226+
225227
// The final className will be built conditionally
226-
return (
227-
<button className={...} {...props}>
228-
{children}
229-
</button>
230-
);
228+
return (
229+
230+
<button className={...} {...props}>
231+
{children}
232+
</button>
233+
);
231234
}
232235
```
233236

pnpm-lock.yaml

Lines changed: 4 additions & 4 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)