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: packages/docs/src/routes/(routes)/docs/intro/+page.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,11 +41,11 @@ daisyUI uses the Tailwind CSS plugin API to extend the available Tailwind CSS cl
41
41
## What's the difference between daisyUI and Tailwind CSS?
42
42
43
43
Tailwind CSS provides low-level utility classes, which usually include only one CSS rule.
44
-
daisyUI classes are a combination of multiple CSS rule that are named semantically for each part of the UI.
44
+
daisyUI classes are a combination of multiple CSS rule that are named semantically for each part of the UI.
45
45
46
-
For example Tailwind CSS class names decide if padding should be 4px or 8px. daisyUI class names decide if a HTML element should look like a "card", a "button", a "toggle", etc, just like what we would call them semantically in a design system.
46
+
For example Tailwind CSS class names decide if padding should be 4px or 8px. daisyUI class names decide if a HTML element should look like a `card`, a `button`, a `toggle`, etc, just like what we would call them semantically in a design system.
47
47
48
-
This makes it easier to design interfaces with less code and more consistency. For example if you want to make a card using Tailwind CSS you would have to write one or multiple utility class names for each single CSS rule. Doing this over and over again for each element, for each page, for each project is time consuming and hard to manage. It also makes it harder to maintain your code as you have to always figure out what part of the code is responsible for what part of the UI.
48
+
This makes it easier to design interfaces with less code and more consistency. For example if you want to make a card using Tailwind CSS you would have to write one or multiple utility class names for each single CSS rule. Doing this over and over again for each element, for each page, for each project is time consuming and hard to manage. It also makes it harder to maintain your code as you have to always figure out what part of the code is responsible for what part of the UI.
49
49
50
50
daisyUI solves this problem by providing higher level class names that are named based on the UI parts. For example to make a card, we simply use the `card` class name and daisyUI gives you all the necessary CSS rules to make a card. Then if you need additional customization, you can add Tailwind CSS utility classes to the element to make it look the way you want.
51
51
@@ -55,17 +55,17 @@ daisyUI is not a replacement for Tailwind CSS, it's a plugin that makes Tailwind
55
55
56
56
Yes! It's utility-first, not utility-only.
57
57
58
-
daisyUI is built on top of Tailwind CSS's component API. Tailwind CSS as a library provides utility classes and suggests using utility classes for maximum flexibility and customization. However that means slower development and more code to write.
59
-
That's why many people find it hard to use Tailwind CSS for designing interfaces. It takes a professional designer to make design decisions for many details of the UI to make them look good. It also takes a lot of time to write all the utility class names for each part of the UI. Even copying and pasting those huge chunks of utility class names is not helpful, as it makes the codebase hard to read and maintain.
58
+
daisyUI is built on top of Tailwind CSS's component API. Tailwind CSS as a library provides utility classes and suggests using utility classes for maximum flexibility and customization. However that's means slower development and more code to write.
59
+
That's why many people find it hard to use Tailwind CSS for designing interfaces. It takes a professional designer to make design decisions for many details of the UI to make them look good. It also takes a lot of time to write all the utility class names for each part of the UI. Even copying and pasting those huge chunks of utility class names is not helpful, as it makes the codebase hard to read and maintain.
60
60
61
61
Imagine one side of the spectrum is maximum customization and flexibility and you should make design decisions for every single detail. On the other side of the spectrum is maximum development speed and less code to write, but you have no control over the design. daisyUI and Tailwind CSS together give you the best of both worlds.
62
62
Use daisyUI class names to write less code and develop faster, and use Tailwind CSS utility classes to customize the design when you need to.
63
63
64
64
Is it full circle?
65
-
If you've been using Bootstrap many years ago, you may think it doesn't make sense to go back to using components.
65
+
If you've been using Bootstrap many years ago, you may think it doesn't make sense to go back to using components.
66
66
67
67
But here's the catch: The problem with Bootstrap was not class names! Bootstrap class names were actually really fast to work with. The problem was lack of customization and flexibility. At some point every Bootstrap website looked the same unless you open a CSS file and write tons of custom CSS.
68
-
Tailwind CSS solves this problem of customization and flexibility but the cost is slower development and more code to write! You wanted customization and flexibility? Good luck making design decisions for every single pixel in your page! Not a practical approach, right?
68
+
Tailwind CSS solves this problem of customization and flexibility but the cost is slower development and more code to write! You wanted customization and flexibility? Good luck making design decisions for every single pixel in your page! Not a practical approach, right?
69
69
70
70
We need customization development speed at the same time. daisyUI is here to make this possible.
Copy file name to clipboardExpand all lines: packages/docs/src/translation/ar.json
+4-3Lines changed: 4 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -485,7 +485,7 @@
485
485
"Want to swim in the ocean of thousands of class names and never find your way out.": "Want to swim in the ocean of thousands of class names and never find your way out.",
486
486
"Want to make your codebase a mess and spend hours figuring out what part of the code is responsible for what part of the UI.": "Want to make your codebase a mess and spend hours figuring out what part of the code is responsible for what part of the UI.",
487
487
"Want to waste your time and money re-inventing the wheel instead of shipping your actual project.": "Want to waste your time and money re-inventing the wheel instead of shipping your actual project.",
488
-
"For example Tailwind CSS class names decide if padding should be 4px or 8px. daisyUI class names decide if a HTML element should look like a \"card\", a \"button\", a \"toggle\", etc, just like what we would call them semantically in a design system.": "For example Tailwind CSS class names decide if padding should be 4px or 8px. daisyUI class names decide if a HTML element should look like a \"card\", a \"button\", a \"toggle\", etc, just like what we would call them semantically in a design system.",
488
+
"For example Tailwind CSS class names decide if padding should be 4px or 8px. daisyUI class names decide if a HTML element should look like a `card`, a `button`, a `toggle`, etc, just like what we would call them semantically in a design system.": "For example Tailwind CSS class names decide if padding should be 4px or 8px. daisyUI class names decide if a HTML element should look like a `card`, a `button`, a `toggle`, etc, just like what we would call them semantically in a design system.",
489
489
"This makes it easier to design interfaces with less code and more consistency. For example if you want to make a card using Tailwind CSS you would have to write one or multiple utility class names for each single CSS rule. Doing this over and over again for each element, for each page, for each project is time consuming and hard to manage. It also makes it harder to maintain your code as you have to always figure out what part of the code is responsible for what part of the UI.": "This makes it easier to design interfaces with less code and more consistency. For example if you want to make a card using Tailwind CSS you would have to write one or multiple utility class names for each single CSS rule. Doing this over and over again for each element, for each page, for each project is time consuming and hard to manage. It also makes it harder to maintain your code as you have to always figure out what part of the code is responsible for what part of the UI.",
490
490
"daisyUI is not a replacement for Tailwind CSS, it's a plugin that makes Tailwind CSS more powerful and easier to use.": "daisyUI is not a replacement for Tailwind CSS, it's a plugin that makes Tailwind CSS more powerful and easier to use.",
491
491
"Yes! It's utility-first, not utility-only.": "Yes! It's utility-first, not utility-only.",
@@ -925,7 +925,6 @@
925
925
"A hidden checkbox can control the state of modal and labels can toggle the checkbox so we can open/close the modal.": "A hidden checkbox can control the state of modal and labels can toggle the checkbox so we can open/close the modal.",
926
926
"open modal": "open modal",
927
927
"is required for responsivness of the dock in iOS.": "is required for responsivness of the dock in iOS.",
928
-
"don't re-invent <br/>the wheel <br/>every time": "لا تعد اختراع <br/>العجلة كل مرة",
929
928
"Put Tailwind CSS and daisyUI in your CSS file at `src/` (and remove old styles).": "Put Tailwind CSS and daisyUI in your CSS file at `src/` (and remove old styles).",
930
929
"Install WordPress according to the [Official WordPress guide](https://wordpress.org/download/).": "Install WordPress according to the [Official WordPress guide](https://wordpress.org/download/).",
931
930
"In this guide, we will use the [WindPress](https://wind.press) plugin to install Tailwind CSS and daisyUI in a WordPress project.": "In this guide, we will use the [WindPress](https://wind.press) plugin to install Tailwind CSS and daisyUI in a WordPress project.",
@@ -1156,5 +1155,7 @@
1156
1155
"When modal is closed, the page will scroll to the top because of the anchor link.": "When modal is closed, the page will scroll to the top because of the anchor link.",
1157
1156
"Anchor links might not work well on some SPA frameworks. If there are problems, use the other methods": "Anchor links might not work well on some SPA frameworks. If there are problems, use the other methods",
1158
1157
"The `hr` tag at the beginning or end of each item, displays a line to connect items.": "The `hr` tag at the beginning or end of each item, displays a line to connect items.",
1159
-
"Inbox": "Inbox"
1158
+
"Inbox": "Inbox",
1159
+
"In chat window type this and write your prompt": "In chat window type this and write your prompt",
1160
+
"don't re-invent <br/>the wheel <br/>every time": "لا تعد اختراع <br/>العجلة كل مرة"
0 commit comments