docs: update abstract
This commit is contained in:
parent
0a87e15195
commit
bbbc308446
|
@ -105,20 +105,14 @@ meta:
|
||||||
type: "image/png"
|
type: "image/png"
|
||||||
---
|
---
|
||||||
|
|
||||||
An introduction to utility class and component based styling, and how to soar
|
An introduction to utility class and component-based styling, and how to soar with [Tailwind CSS][1].
|
||||||
with [Tailwind CSS][1].
|
|
||||||
|
|
||||||
Things we’ll cover:
|
Things we'll cover:
|
||||||
|
|
||||||
- Advantages and disadvantages to utility based styling and Tailwind.
|
- Advantages and disadvantages to utility-based styling and Tailwind CSS.
|
||||||
- How to install Tailwind and add it to your build process using tools such as Symfony Encore and Laravel Mix.
|
- How to add Tailwind CSS to your project and configure and customise it.
|
||||||
- How to configure and customise Tailwind for your project.
|
- How to avoid duplication by moving repeating classes into re-usable components for better maintainability.
|
||||||
- How to promote repeating classes into re-usable components for better maintainability.
|
- How to extend Tailwind CSS and add extra classes with community-written plugins.
|
||||||
- Strategies to control the file size, and using external tools like PurgeCSS.
|
- How to write and test your own custom project-specific plugins.
|
||||||
|
|
||||||
Also, if time allows:
|
|
||||||
|
|
||||||
- How to extend Tailwind and add extra classes with community written plugins.
|
|
||||||
- How to write and test your own custom plugins.
|
|
||||||
|
|
||||||
[1]: https://tailwindcss.com
|
[1]: https://tailwindcss.com
|
||||||
|
|
Loading…
Reference in a new issue