Skip to content

Commit c97f928

Browse files
committed
docs: update docs
1 parent 3d5104e commit c97f928

14 files changed

+540
-91
lines changed

docs/cookbook/integrating-shadcn-ui.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,13 +132,14 @@ Now you can import and use your new button component from `@/components/ui/butto
132132
> [!NOTE]
133133
> Check out the [`shadcn/ui` components gallery](https://ui.shadcn.com/docs/components/accordion) to explore all the beautiful components at your disposal.
134134
135-
136135
## Troubleshooting
137136

138137
If you're using `vite` and see this error `No Tailwind CSS configuration found at path....` (but do have a `tailwind.config.js`) ensure you've imported the CSS properly.
138+
139139
```
140140
@tailwind base;
141141
@tailwind components;
142142
@tailwind utilities;
143143
```
144+
144145
Reference: [Link to Common Github Issue](https://github.com/shadcn-ui/ui/issues/4677)

docs/guide/code-splitting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Code splitting breaks apart the various pages of your application into smaller b
44

55
While code splitting is helpful for very large projects, it does require extra requests when visiting new pages. Generally speaking, if you're able to use a single bundle, your app is going to feel snappier.
66

7-
To enable code splitting you'll need to tweak the resolve callback in your `createInertiaApp()` configuration, and how you do this is different depending on which bundler you're using.
7+
To enable code splitting, you will need to tweak the `resolve` callback in your `createInertiaApp()` configuration, and how you do this is different depending on which bundler you're using.
88

99
## Using Vite
1010

docs/guide/error-handling.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -131,13 +131,13 @@ export default function ErrorPage({ status }) {
131131
```svelte
132132
<script>
133133
let { status } = $props()
134-
const titles = {
134+
const title = {
135135
503: '503: Service Unavailable',
136136
500: '500: Server Error',
137137
404: '404: Page Not Found',
138138
403: '403: Forbidden',
139139
}
140-
const descriptions = {
140+
const description = {
141141
503: 'Sorry, we are doing some maintenance. Please check back soon.',
142142
500: 'Whoops, something went wrong on our servers.',
143143
404: 'Sorry, the page you are looking for could not be found.',
@@ -146,7 +146,7 @@ export default function ErrorPage({ status }) {
146146
</script>
147147
148148
<div>
149-
<h1>{titles[status]}</h1>
149+
<h1>{title[status]}</h1>
150150
<div>{description[status]}</div>
151151
</div>
152152
```

0 commit comments

Comments
 (0)