├── .eslintignore
├── .eslintrc.js
├── .github
└── ISSUE_TEMPLATE
│ ├── bug_report.md
│ ├── custom.md
│ └── feature_request.md
├── .gitignore
├── .npmignore
├── .prettierrc
├── .vscode
└── settings.json
├── BUILD-TOOLS.md
├── CONTRIBUTING.md
├── LICENSE.md
├── README.md
├── config.yml
├── content
├── _index.html
├── components
│ ├── accordion.md
│ ├── alerts.md
│ ├── avatar.md
│ ├── badge.md
│ ├── banner.md
│ ├── bottom-navigation.md
│ ├── breadcrumb.md
│ ├── button-group.md
│ ├── buttons.md
│ ├── card.md
│ ├── carousel.md
│ ├── chat-bubble.md
│ ├── clipboard.md
│ ├── datepicker.md
│ ├── device-mockups.md
│ ├── drawer.md
│ ├── dropdowns.md
│ ├── footer.md
│ ├── forms.md
│ ├── gallery.md
│ ├── indicators.md
│ ├── jumbotron.md
│ ├── kbd.md
│ ├── list-group.md
│ ├── mega-menu.md
│ ├── modal.md
│ ├── navbar.md
│ ├── pagination.md
│ ├── popover.md
│ ├── progress.md
│ ├── rating.md
│ ├── sidebar.md
│ ├── skeleton.md
│ ├── speed-dial.md
│ ├── spinner.md
│ ├── stepper.md
│ ├── tables.md
│ ├── tabs.md
│ ├── timeline.md
│ ├── toast.md
│ ├── tooltips.md
│ ├── typography.md
│ └── video.md
├── customize
│ ├── _index.html
│ ├── colors.md
│ ├── configuration.md
│ ├── dark-mode.md
│ ├── icons.md
│ ├── optimization.md
│ ├── rtl.md
│ └── theming.md
├── forms
│ ├── checkbox.md
│ ├── file-input.md
│ ├── floating-label.md
│ ├── input-field.md
│ ├── number-input.md
│ ├── phone-input.md
│ ├── radio.md
│ ├── range.md
│ ├── search-input.md
│ ├── select.md
│ ├── textarea.md
│ ├── timepicker.md
│ └── toggle.md
├── getting-started
│ ├── _index.html
│ ├── angular.md
│ ├── astro.md
│ ├── blazor.md
│ ├── build-tools.md
│ ├── changelog.md
│ ├── django.md
│ ├── flask.md
│ ├── gatsby.md
│ ├── hugo.md
│ ├── introduction.md
│ ├── javascript.md
│ ├── laravel.md
│ ├── license.md
│ ├── llm.md
│ ├── meteor-js.md
│ ├── next-js.md
│ ├── nuxt-js.md
│ ├── phoenix.md
│ ├── quickstart.md
│ ├── qwik.md
│ ├── rails.md
│ ├── react.md
│ ├── remix.md
│ ├── solid-js.md
│ ├── svelte.md
│ ├── symfony.md
│ ├── typescript.md
│ └── vue.md
├── plugins
│ ├── charts.md
│ ├── datatables.md
│ ├── datepicker.md
│ └── wysiwyg.md
└── typography
│ ├── blockquote.md
│ ├── headings.md
│ ├── hr.md
│ ├── images.md
│ ├── links.md
│ ├── lists.md
│ ├── paragraphs.md
│ ├── text-decoration.md
│ └── text.md
├── data
├── colors.yml
└── sidebar.yml
├── layouts
├── _default
│ ├── 404.html
│ ├── _markup
│ │ └── render-heading.html
│ ├── baseof.html
│ ├── dashboard.html
│ ├── home.html
│ └── redirect.html
├── alias.html
├── partials
│ ├── analytics.html
│ ├── favicons.html
│ ├── footer.html
│ ├── header.html
│ ├── navbar.html
│ ├── redirect.html
│ ├── scripts.html
│ ├── sidebar.html
│ ├── social.html
│ └── stylesheet.html
├── robots.txt
├── shortcodes
│ ├── current_version.html
│ ├── example.html
│ ├── markdown.html
│ ├── param.html
│ ├── partial.html
│ ├── placeholder.html
│ ├── preview.html
│ ├── requires_angular.html
│ ├── requires_blazor.html
│ ├── requires_django.html
│ ├── requires_flask.html
│ ├── requires_hugo.html
│ ├── requires_js.html
│ ├── requires_laravel.html
│ ├── requires_nextjs.html
│ ├── requires_nuxtjs.html
│ ├── requires_react.html
│ ├── requires_ruby.html
│ ├── requires_svelte.html
│ ├── requires_symfony.html
│ ├── requires_tw3.html
│ ├── requires_tw4.html
│ ├── requires_typescript
│ └── requires_vue.html
└── sitemap.xml
├── llms-full.txt
├── llms.txt
├── package-lock.json
├── package.json
├── plugin-windicss.js
├── plugin.d.ts
├── plugin.js
├── postcss.config.js
├── safelist.txt
├── src
├── components
│ ├── accordion
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── carousel
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── clipboard
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── collapse
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── datepicker
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── dial
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── dismiss
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── drawer
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── dropdown
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── index.ts
│ ├── input-counter
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── modal
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── popover
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ ├── tabs
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
│ └── tooltip
│ │ ├── index.ts
│ │ ├── interface.ts
│ │ └── types.ts
├── config
│ └── global.ts
├── docs.js
├── dom
│ ├── events.ts
│ ├── instances.ts
│ └── types.ts
├── flowbite.css
├── index.phoenix.ts
├── index.ts
├── index.turbo.ts
├── index.umd.ts
├── main.css
├── themes
│ └── default.css
└── types
│ └── declarations.ts
├── static
├── android-chrome-192x192.png
├── android-chrome-512x512.png
├── android-icon-144x144.png
├── android-icon-192x192.png
├── android-icon-36x36.png
├── android-icon-48x48.png
├── android-icon-72x72.png
├── android-icon-96x96.png
├── apple-icon-114x114.png
├── apple-icon-120x120.png
├── apple-icon-144x144.png
├── apple-icon-152x152.png
├── apple-icon-180x180.png
├── apple-icon-57x57.png
├── apple-icon-60x60.png
├── apple-icon-72x72.png
├── apple-icon-76x76.png
├── apple-icon-precomposed.png
├── apple-icon.png
├── apple-touch-icon.png
├── browserconfig.xml
├── favicon-16x16.png
├── favicon-32x32.png
├── favicon-96x96.png
├── favicon.ico
├── images
│ ├── blog
│ │ ├── image-1.jpg
│ │ ├── image-2.jpg
│ │ ├── image-3.jpg
│ │ ├── image-4.jpg
│ │ └── image-7.jpg
│ ├── book-dark.svg
│ ├── book-light.svg
│ ├── carousel
│ │ ├── carousel-1.svg
│ │ ├── carousel-2.svg
│ │ ├── carousel-3.svg
│ │ ├── carousel-4.svg
│ │ └── carousel-5.svg
│ ├── chatbubble
│ │ └── calendar.png
│ ├── dashboard-overview.png
│ ├── examples
│ │ ├── image-1.jpg
│ │ ├── image-1@2x.jpg
│ │ ├── image-2.jpg
│ │ ├── image-2@2x.jpg
│ │ ├── image-3.jpg
│ │ ├── image-3@2x.jpg
│ │ ├── image-4.jpg
│ │ ├── image-4@2x.jpg
│ │ └── image-5.jpg
│ ├── gradients
│ │ ├── mesh-gradient-1.png
│ │ ├── mesh-gradient-2.png
│ │ ├── mesh-gradient-3.png
│ │ ├── mesh-gradient-4.png
│ │ └── mesh-gradient-5.png
│ ├── logo.svg
│ ├── misc
│ │ └── flowbite-yt-screenshot.png
│ ├── og-image.png
│ ├── people
│ │ ├── profile-picture-1.jpg
│ │ ├── profile-picture-2.jpg
│ │ ├── profile-picture-3.jpg
│ │ ├── profile-picture-4.jpg
│ │ └── profile-picture-5.jpg
│ ├── popovers
│ │ └── italy.png
│ ├── products
│ │ ├── apple-watch.png
│ │ ├── imac.png
│ │ └── iphone-12.png
│ └── themesberg.svg
├── manifest.json
├── ms-icon-144x144.png
├── ms-icon-150x150.png
├── ms-icon-310x310.png
├── ms-icon-70x70.png
├── mstile-150x150.png
├── safari-pinned-tab.svg
├── site.webmanifest
├── sw.js
└── videos
│ └── flowbite.mp4
├── syntax.css
├── tailwind.config.js
├── tsconfig.json
└── webpack.config.js
/.eslintignore:
--------------------------------------------------------------------------------
1 | *.md
2 | .gitignore
3 | build/
4 | dist/
5 | lib/
--------------------------------------------------------------------------------
/.eslintrc.js:
--------------------------------------------------------------------------------
1 | module.exports = {
2 | root: true,
3 | parser: '@typescript-eslint/parser',
4 | plugins: ['@typescript-eslint'],
5 | env: {
6 | node: true,
7 | browser: true,
8 | es6: true,
9 | },
10 | extends: [
11 | 'eslint:recommended',
12 | 'plugin:@typescript-eslint/eslint-recommended',
13 | 'plugin:@typescript-eslint/recommended',
14 | 'plugin:prettier/recommended',
15 | ],
16 | };
17 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/custom.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Custom issue template
3 | about: Describe this issue template's purpose here.
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 |
11 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | node_modules/
2 | dist/
3 | lib/
4 | build/
5 | _gh_pages/
6 | static/*.css
7 | static/*.js
8 | !static/sw.js
9 | static/*.map
10 | .DS_Store
11 | yarn-error.log
12 | /.idea
13 | .hugo_build.lock
14 |
--------------------------------------------------------------------------------
/.npmignore:
--------------------------------------------------------------------------------
1 | _gh_pages/
2 | assets/
3 | build/
4 | content/
5 | data/
6 | layouts/
7 | node_modules/
8 | resources/
9 | static/
10 | src/docs.js
11 | src/main.css
12 | config.yml
13 | yarn-error.log
14 | syntax.css
15 | BUILD-TOOLS.md
--------------------------------------------------------------------------------
/.prettierrc:
--------------------------------------------------------------------------------
1 | {
2 | "singleQuote": true,
3 | "eslintIntegration": true,
4 | "tabWidth": 4,
5 | "plugins": [
6 | "prettier-plugin-tailwindcss"
7 | ]
8 | }
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "editor.codeActionsOnSave": {
3 | "source.fixAll.eslint": "explicit"
4 | }
5 | }
6 |
--------------------------------------------------------------------------------
/BUILD-TOOLS.md:
--------------------------------------------------------------------------------
1 | ## FlowBite Documentation
2 |
3 | These are the source files for the Flowbite Tailwind CSS components library.
4 |
5 | ### Getting started
6 |
7 | 1. Make sure you have Node and NPM installed
8 | 2. Run `yarn install`
9 | 3. Run `yarn start` to start developing
10 |
11 | ## Building the docs website
12 |
13 | Make sure to switch `enabled` to `true` in the `tailwind.config.js` file when building for docs to purge the extra CSS. (doesn't work with the process env for some reason).
14 |
15 | Run `yarn build` to build the static HTML files that will be uploaded to FlowBite. The static HTML files can be found in the `_gh_pages/` folder then moved to the `static/docs` folder from the main FlowBite Gatsby repo.
16 |
17 | ## Building for NPM registry
18 |
19 | Make sure that purge is NOT enabled in `tailwind.config.js` (this needs to be fixed with env variables).
20 |
21 | Run `npm run build:npm` and then `npm publish` to release a new version. Make sure you also change the version.
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing guide
2 |
3 | ## What do I need to know to help?
4 |
5 | If you are looking to help to with a code contribution our project uses JavaScript and Tailwind CSS. If you don't feel ready to make a code contribution yet, no problem!
6 |
7 | If you are interested in making a code contribution and would like to learn more about the technologies that we use, check out the list below.
8 |
9 | - [Learn JavaScript - Full Course for Beginners](https://www.youtube.com/watch?v=PkZNo7MFNFg)
10 | - [Tailwind CSS](https://tailwindcss.com/)
11 |
12 | ## How do I make a contribution?
13 |
14 | Never made an open source contribution before? Wondering how contributions work in the in our project? Here's a quick rundown!
15 |
16 | 1. [Find an issue](https://github.com/themesberg/flowbite/issues) that you are interested in addressing or a feature that you would like to add.
17 | 2. Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under `your-GitHub-username/repository-name`.
18 | 3. Clone the repository to your local machine using `git clone https://github.com/github-username/repository-name.git`.
19 | 4. Create a new branch for your fix using `git checkout -b branch-name-here`.
20 | 5. Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
21 | 6. Use `git add insert-paths-of-changed-files-here` to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.
22 | 7. Use `git commit` to store the contents of the index with a descriptive message. Use [conventional commits](https://www.conventionalcommits.org/) to create a nice message.
23 | 8. Push the changes to the remote repository using `git push origin branch-name-here`.
24 | 9. Submit a pull request to the upstream repository.
25 | 10. Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so `"Added more log outputting to resolve #4352"`.
26 | 11. In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
27 | 12. Wait for the pull request to be reviewed by a maintainer.
28 | 13. Make changes to the pull request if the reviewing maintainer recommends them.
29 | 14. Celebrate your success after your pull request is merged! 🎉 🎉
30 |
31 | ## Where can I go for help?
32 |
33 | If you need help, you can ask questions please, [join us at our Discord Community](https://discord.gg/S6J9pUmj2t).
34 |
35 | ## What does the Code of Conduct mean for me?
36 |
37 | Our Code of Conduct means that you are responsible for treating everyone on the project with respect and courtesy regardless of their identity. If you are the victim of any inappropriate behavior or comments as described in our Code of Conduct, we are here for you and will do the best to ensure that the abuser is reprimanded appropriately, per our code.
38 |
39 | ## Code of conduct
40 |
41 | For more information [check this file](CODE_OF_CONDUCT.md).
42 |
--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2023 Bergside Inc.
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/config.yml:
--------------------------------------------------------------------------------
1 | languageCode: "en"
2 | title: "Flowbite"
3 | baseURL: "https://flowbite.com/docs/"
4 | enableInlineShortcodes: true
5 |
6 | params:
7 | homepage: "https://flowbite.com"
8 | current_version: 3.1.2
9 | authors: Themesberg
10 | social_image_path: /docs/images/og-image.png
11 |
12 | markup:
13 | goldmark:
14 | renderer:
15 | unsafe: true
16 | highlight:
17 | noClasses: false
18 | style: colorful
19 | tableOfContents:
20 | startLevel: 2
21 | endLevel: 6
22 |
23 | buildDrafts: true
24 | buildFuture: true
25 |
26 | enableRobotsTXT: true
27 | metaDataFormat: "yaml"
28 | disableKinds: ["404", "taxonomy", "taxonomyTerm", "RSS"]
29 |
30 | publishDir: "_gh_pages"
31 |
--------------------------------------------------------------------------------
/content/_index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: redirect
3 | sitemap_exclude: true
4 | redirect: "/docs/getting-started/introduction/"
5 | ---
--------------------------------------------------------------------------------
/content/components/progress.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS Progress Bar - Flowbite
4 | description: Use the progress bar component to show the completion rate of a data indicator or use it as a loader element
5 | group: components
6 | toc: true
7 |
8 | previous: Popover
9 | previousLink: components/popover/
10 | next: Rating
11 | nextLink: components/rating/
12 | ---
13 |
14 | The progress bar component can be used as an indicator to show the completion rate of data sets or it can be used as an animated loader component. There are multiple sizes, colors, and styles available.
15 |
16 | ## Default progress bar
17 |
18 | Use the following example of a progress bar element to show a completion rate of 45% by using an inline style and the utility classes from Tailwind CSS.
19 |
20 | {{< example id="default-progress-example" github="components/progress.md" show_dark=true >}}
21 |
22 |
23 |
24 | {{< /example >}}
25 |
26 | ## Sizes
27 |
28 | You can also use different sizes by using various sizing utility classes from Flowbite and Tailwind CSS.
29 |
30 | {{< example id="progress-sizes-example" github="components/progress.md" show_dark=true >}}
31 |
Small
32 |
33 |
34 |
35 |
Default
36 |
37 |
38 |
39 |
Large
40 |
41 |
42 |
43 |
Extra Large
44 |
45 |
46 |
47 | {{< /example >}}
48 |
49 | ## With label inside
50 |
51 | Here is an example of using a progress bar with the label inside the bar.
52 |
53 | {{< example id="progress-label-example" github="components/progress.md" show_dark=true >}}
54 |
55 |
45%
56 |
57 | {{< /example >}}
58 |
59 | ## With label outside
60 |
61 | And this is an example of using a progress bar outside the bar.
62 |
63 | {{< example id="progress-label-outside-example" github="components/progress.md" show_dark=true >}}
64 |
65 | Flowbite
66 | 45%
67 |
68 |
69 |
70 |
71 | {{< /example >}}
72 |
73 | ## Colors
74 |
75 | You can also apply any color using the `bg-{color}` utility classes from Tailwind CSS and Flowbite.
76 |
77 | {{< example id="progress-colors-example" github="components/progress.md" show_dark=true >}}
78 |
Dark
79 |
80 |
81 |
82 |
Blue
83 |
84 |
85 |
86 |
Red
87 |
88 |
89 |
90 |
Green
91 |
92 |
93 |
94 |
Yellow
95 |
96 |
97 |
98 |
Indigo
99 |
100 |
101 |
102 |
Purple
103 |
104 |
105 |
106 | {{< /example >}}
107 |
--------------------------------------------------------------------------------
/content/components/video.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS Video - Flowbite
4 | description: Use the video component to configure an embedded video player using native HTML 5 functionality based on the utility classes from Tailwind CSS
5 | group: components
6 | toc: true
7 |
8 | previous: Typography
9 | previousLink: components/typography/
10 | next: Input field
11 | nextLink: forms/input-field/
12 | ---
13 |
14 | Get started with the video component to embed internal video source into a native HTML 5 video player and set custom options such as autoplay or muted to enhance the user experience.
15 |
16 | ## Video player
17 |
18 | Use this example to create a native browser video player and apply the `w-full` utility class from Tailwind CSS to span the full width of the parent container.
19 |
20 | {{< example id="default-video-example" github="typography/video.md" show_dark=true >}}
21 |
25 | {{< /example >}}
26 |
27 | ## Autoplay
28 |
29 | Use the `autoplay` attribute on the video component to automatically start the video when the page has been loaded.
30 |
31 | {{< example id="video-autoplay-example" github="typography/video.md" show_dark=true >}}
32 |
36 | {{< /example >}}
37 |
38 | ## Muted
39 |
40 | Use the `muted` attribute together with the `autoplay` option to start the video while the sound is muted.
41 |
42 | {{< example id="video-muted-example" github="typography/video.md" show_dark=true >}}
43 |
47 | {{< /example >}}
48 |
49 | ## Sizes
50 |
51 | Set the width and height of the video component using the `w-{size}` and `h-{size}` utility classes from Tailwind CSS.
52 |
53 | ### Width
54 |
55 | Use the `w-{size}` class to set the width of the video component.
56 |
57 | {{< example id="video-width-example" github="typography/video.md" show_dark=true >}}
58 |
62 | {{< /example >}}
63 |
64 | ### Height
65 |
66 | Use the `h-{size}` class to set the height of the video player.
67 |
68 | {{< example id="video-height-example" github="typography/video.md" show_dark=true >}}
69 |
73 | {{< /example >}}
74 |
75 | ### Responsive
76 |
77 | Use the following example to make the video responsive across all devices and viewports.
78 |
79 | {{< example id="video-responsive-example" github="typography/video.md" show_dark=true >}}
80 |
84 | {{< /example >}}
85 |
86 | ## Custom styles
87 |
88 | Customize the video player appearance using the utility classes from Tailwind CSS such as `rounded-{size}` or `border` to set rounded-sm corners and border.
89 |
90 | {{< example id="video-customize-example" github="typography/video.md" show_dark=true >}}
91 |
95 | {{< /example >}}
--------------------------------------------------------------------------------
/content/customize/_index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: redirect
3 | sitemap_exclude: true
4 | redirect: "/docs/customize/configuration/"
5 | ---
--------------------------------------------------------------------------------
/content/customize/optimization.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS Optimization - Flowbite
4 | description: Optimize your project for production use by setting up Flowbite and Tailwind CSS using our guide
5 | group: customize
6 | toc: true
7 |
8 | previous: Icons
9 | previousLink: customize/icons/
10 | next: Accordion
11 | nextLink: components/accordion/
12 | ---
13 |
14 | The default JavaScript development build of Flowbite and Tailwind CSS is roughly 310kB uncompressed, 136kB when minified via CDN.
15 |
16 | Although working with the CDN can be quick and effective, it is not the most efficient way of working with Tailwind CSS and Flowbite. You should definitely check our [quickstart guide](https://flowbite.com/docs/getting-started/quickstart/) and set up Tailwind CSS in your local environment so that the only the CSS being used in your templates will be added to the final CSS file.
17 |
18 | ## Remove unused CSS
19 |
20 | Since Tailwind v4 you no longer need to set the content paths for your templating files.
21 |
22 | However, you might want to set custom sources for where the engine should look for utility classes.
23 |
24 | ```css
25 | @import "tailwindcss";
26 |
27 | @source "../node_modules/flowbite";
28 | ```
29 |
30 | ## Build for production
31 |
32 | When building your CSS, make sure that you set `NODE_ENV` to `production`.
33 |
34 | The command that you have to run in your terminal for production build would be:
35 |
36 | ```javascript
37 | NODE_ENV=production npx @tailwindcss/cli -i input.css -o output.css
38 | ```
39 |
40 | This command will create an `output.css` file that you will include in your templating files.
--------------------------------------------------------------------------------
/content/customize/rtl.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS RTL (Right-To-Left) - Flowbite
4 | description: Learn how to setup and configure bidirectional text formats (RTL and LTR) in your project using native Tailwind CSS variants and the Flowbite UI components
5 | group: customize
6 | toc: true
7 |
8 | previous: Icons
9 | previousLink: customize/icons/
10 | next: Optimization
11 | nextLink: customize/optimization/
12 | ---
13 |
14 | RTL (right-to-left) is a bidirectional text format used for languages that are written from right to left such as Arabic, Hebrew, Persian, Urdu, and Yiddish. A rough estimate would be around over 500 million people that use RTL languages and it's one of the fastest growing populations on the internet.
15 |
16 | All of the UI components from Flowbite support RTL by primarily using the logical properties and values from CSS such as `ms-0` instead of `ml-0` or `pe-5` instead of `pr-5`. This feature requires Tailwind CSS v3.3.0 or higher and Flowbite v2.1.0 or higher.
17 |
18 | In this guide you will learn how to setup and configure bidirectional text formats (RTL and LTR) in your project using Tailwind CSS variants and the Flowbite UI components by changing the `dir` attribute on the `` element.
19 |
20 | ## Setting up RTL
21 |
22 | Before you start, make sure you have installed the latest version of [Tailwind CSS](https://tailwindcss.com/docs/installation) and [Flowbite](https://flowbite.com/docs/getting-started/quickstart/).
23 |
24 | 1. Add the `dir` attribute to the `` element in your `index.html` file:
25 |
26 | ```html
27 |
28 |
29 |
30 |
31 |
32 | ```
33 |
34 | By default, when switching from LTR to RTL the direction, spacing, and positioning of all the UI components from Flowbite will be mirrored as we used logical properties and RTL variants from Tailwind CSS.
35 |
36 | You can also use our RTL button to switch between LTR and RTL when previewing our UI components:
37 |
38 | {{< example id="default-navbar-example" bodyClass="!p-0" github="components/navbar.md" show_dark=true iframeHeight="300" >}}
39 |
40 |
73 | {{< /example >}}
74 |
75 | ## Using RTL variants
76 |
77 | If you need to add RTL variants to your own custom components, you can use the `rtl:` prefix.
78 |
79 | For example, if you want to add a margin to the left side of an element in LTR mode, you would use `ml-2`.
80 |
81 | In RTL mode, you would use `rtl:ml-2` instead.
82 |
83 | ```html
84 |
85 |
86 |
87 | ```
88 |
89 | However, we do recommend that you use logical properties for margins, paddings, borders, and rounded-sm corners because the HTML markup will be cleaner and contain less utility-classes, which is always a good thing when it comes to Tailwind CSS.
90 |
91 | ## UI components
92 |
93 | As mentioned before, all of the UI components from Flowbite support RTL by default and all of the examples from the documentation will render correctly whenever you set the `dir` attribute to `rtl` on the `` element. Check out all our UI components and examples from the [official documentation](https://flowbite.com/docs/getting-started/introduction/).
--------------------------------------------------------------------------------
/content/forms/file-input.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS File Input - Flowbite
4 | description: Get started with the file input component to let the user to upload one or more files from their device storage based on multiple styles and sizes
5 | group: forms
6 | toc: true
7 | requires_js: true
8 |
9 | previous: Input Field
10 | previousLink: forms/input-field/
11 | next: Search Input
12 | nextLink: forms/search-input/
13 | ---
14 |
15 | The file input component can be used to upload one or more files from the device storage of the user available in multiple sizes, styles, and variants and built with the utility-first classes from Tailwind CSS including support for dark mode.
16 |
17 | Make sure that you have included Flowbite as a plugin inside your Tailwind CSS project to apply all the necessary styles for the file input component.
18 |
19 | ## File upload example
20 |
21 | Get started with a simple file input component to let users upload one single file.
22 |
23 | {{< example id="default-file-upload-example" github="forms/file-input.md" show_dark=true >}}
24 |
25 |
26 | {{< /example >}}
27 |
28 | ## Helper text
29 |
30 | Add a descriptive helper text to inform users the allowed extensions and sizes of the files.
31 |
32 | {{< example id="file-upload-helper-example" github="forms/file-input.md" show_dark=true >}}
33 |
34 |
35 |
SVG, PNG, JPG or GIF (MAX. 800x400px).
36 | {{< /example >}}
37 |
38 | ## Multiple files
39 |
40 | Apply the `multiple` attribute to the file input component to allow more files to be uploaded.
41 |
42 | {{< example id="file-upload-multiple-example" github="forms/file-input.md" show_dark=true >}}
43 |
44 |
45 | {{< /example >}}
46 |
47 | ## Sizes
48 |
49 | Choose from the small, default, and large file input sizing options.
50 |
51 | {{< example id="file-upload-sizes-example" github="forms/file-input.md" show_dark=true >}}
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 | {{< /example >}}
61 |
62 | ## Dropzone
63 |
64 | The dropzone file input component can be used to upload one or more files by clicking anywhere in the area.
65 |
66 | {{< example id="file-upload-dropzone-example" github="forms/file-input.md" show_dark=true >}}
67 |
68 |
78 |
79 | {{< /example >}}
--------------------------------------------------------------------------------
/content/forms/range.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS Range Slider - Flowbite
4 | description: Get started with the range component to receive a number from the user anywhere from 1 to 100 by sliding form control horizontally based on multiple options
5 | group: forms
6 | toc: true
7 | requires_js: true
8 |
9 | previous: Toggle
10 | previousLink: forms/toggle/
11 | next: Floating Label
12 | nextLink: forms/floating-label/
13 | ---
14 |
15 | The range component can be used as an input field to get a number from the user based on your custom selection (ie. from 1 to 100) by using a sliding animation.
16 |
17 | The examples on this page are all coded with Tailwind CSS and requires you to install Flowbite as a plugin inside your project to obtain all the necessary stylings.
18 |
19 | ## Range slider example
20 |
21 | Get started with this default example with values from 1 to 100 and the default value of 50.
22 |
23 | {{< example id="default-range-example" github="forms/range.md" show_dark=true >}}
24 |
25 |
26 | {{< /example >}}
27 |
28 | ## Disabled state
29 |
30 | Apply the `disabled` class to disallow the users from further selecting values.
31 |
32 | {{< example id="range-disabled-example" github="forms/range.md" show_dark=true >}}
33 |
34 |
35 | {{< /example >}}
36 |
37 | ## Min and max
38 |
39 | Use the min and max attributes on the range component to set the limits of the range values.
40 |
41 | {{< example id="range-minmax-example" github="forms/range.md" show_dark=true >}}
42 |
43 |
44 | {{< /example >}}
45 |
46 | ## Steps
47 |
48 | Use the step attribute on the range component to set the increment with which the values will change.
49 |
50 | {{< example id="range-steps-example" github="forms/range.md" show_dark=true >}}
51 |
52 |
53 | {{< /example >}}
54 |
55 | ## Sizes
56 |
57 | Apply the small, default, and large sizes for the range component by applying the `range-sm` and `range-lg` utility classes from Flowbite and Tailwind CSS.
58 |
59 | {{< example id="range-sizes-example" github="forms/range.md" show_dark=true >}}
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 | {{< /example >}}
69 |
70 | ## Labels
71 |
72 | Use the following example to add labels to each value milestone of the range slider component.
73 |
74 | {{< example id="range-labels-example" github="forms/range.md" show_dark=true >}}
75 |
76 |
77 |
78 | Min ($100)
79 | $500
80 | $1000
81 | Max ($1500)
82 |
83 | {{< /example >}}
84 |
--------------------------------------------------------------------------------
/content/getting-started/_index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: redirect
3 | sitemap_exclude: true
4 | redirect: "/docs/getting-started/introduction/"
5 | ---
--------------------------------------------------------------------------------
/content/getting-started/build-tools.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: redirect
3 | sitemap_exclude: true
4 | redirect: "/docs/getting-started/quickstart/"
5 | ---
--------------------------------------------------------------------------------
/content/getting-started/laravel.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS Laravel - Flowbite
4 | description: Learn how to install Tailwind CSS with Flowbite in a Laravel PHP project and start building modern websites with the most popular PHP framework in the world
5 | group: getting-started
6 | toc: true
7 | requires_laravel: true
8 |
9 | previous: Qwik
10 | previousLink: getting-started/qwik/
11 | next: Symfony
12 | nextLink: getting-started/symfony/
13 | ---
14 |
15 | Laravel is the most popular free and open-source PHP web framework that helps you build modern web applications and API's based on a model-view-controller (MVC) programming architecture. It's an iteration of the [Symfony](https://flowbite.com/docs/getting-started/symfony/) framework and it's being used by millions of developers and companies around the world.
16 |
17 | Check out this guide to learn how to set up a new Laravel project together with Tailwind CSS and the UI components from Flowbite to enhance your front-end development workflow.
18 |
19 | ## Create a Laravel app
20 |
21 | Make sure that you have Composer and Node.js installed locally on your computer.
22 |
23 | Follow the next steps to install Tailwind CSS and Flowbite with Laravel Mix.
24 |
25 | 1. Require the Laravel Installer globally using Composer:
26 |
27 | ```bash
28 | composer global require laravel/installer
29 | ```
30 |
31 | Make sure to place the vendor bin directory in your PATH. Here's how you can do it based on each OS:
32 |
33 | - macOS: `export PATH="$PATH:$HOME/.composer/vendor/bin"`
34 | - Windows: `set PATH=%PATH%;%USERPROFILE%\AppData\Roaming\Composer\vendor\bin`
35 | - Linux: `export PATH="~/.config/composer/vendor/bin:$PATH"`
36 |
37 | 2. Create a new project using Laravel's CLI:
38 |
39 | ```bash
40 | laravel new flowbite-app
41 | cd flowbite-app
42 | ```
43 |
44 | Start the development server using the following command:
45 |
46 | ```bash
47 | composer run dev
48 | ```
49 |
50 | You can now access the Laravel application on `http://localhost:8000`.
51 |
52 | This command will initialize a blank Laravel project that you can get started with.
53 |
54 | ## Install Tailwind CSS
55 |
56 | Since Laravel 12, the latest version of Tailwind v4 will be installed by default, so if you have that version or later then you can skip this step and proceed with installing Flowbite.
57 |
58 | 1. Install Tailwind CSS using NPM:
59 |
60 | ```javascript
61 | npm install tailwindcss @tailwindcss/vite --save-dev
62 | ```
63 |
64 | 2. Configure the `vite.config.ts` file by importing the Tailwind plugin:
65 |
66 | ```javascript
67 | import { defineConfig } from 'vite'
68 | import tailwindcss from '@tailwindcss/vite'
69 | export default defineConfig({
70 | plugins: [
71 | tailwindcss(),
72 | // …
73 | ],
74 | })
75 | ```
76 |
77 | 3. Import the main Tailwind directive inside your `app.css` CSS file:
78 |
79 | ```css
80 | @import "tailwindcss";
81 | ```
82 |
83 | 5. Run the build process for Vite using `npm run dev`. Use `npm run build` for production builds.
84 |
85 | ## Install Flowbite
86 |
87 | [Flowbite](https://flowbite.com) is a popular and open-source UI component library built on top of the Tailwind CSS framework that allows you to choose from a wide range of UI components such as modals, drawers, buttons, dropdowns, datepickers, and more to make your development workflow faster and more efficient.
88 |
89 | Follow the next steps to install Flowbite using NPM.
90 |
91 | 1. Install Flowbite as a dependency using NPM by running the following command:
92 |
93 | ```bash
94 | npm install flowbite --save
95 | ```
96 |
97 | 2. Import the default theme variables from Flowbite inside your main `app.css` CSS file:
98 |
99 | ```css
100 | @import "flowbite/src/themes/default";
101 | ```
102 |
103 | 3. Import the Flowbite plugin file in your CSS:
104 |
105 | ```css
106 | @plugin "flowbite/plugin";
107 | ```
108 |
109 | 4. Configure the source files of Flowbite in your CSS:
110 |
111 | ```css
112 | @source "../../node_modules/flowbite";
113 | ```
114 |
115 | 5. Add the Flowbite JS script inside your main `app.blade.php` layout file:
116 |
117 | ```html
118 |
119 | @yield('content')
120 |
121 |
122 |
123 | ```
124 |
125 | This will have the JavaScript loaded in all the files that extend this main layout.
126 |
127 | ## UI components
128 |
129 | Now that you have successfully installed the project you can start using the UI components from Flowbite and Tailwind CSS to develop modern websites and web applications.
130 |
131 | We recommend exploring the components using the search bar navigation (`cmd` or `ctrl` + `k`) or by browsing the components section of the sidebar on the left side of this page.
132 |
133 | ## Laravel starter project
134 |
135 | Download or clone the [Flowbite Laravel](https://github.com/themesberg/tailwind-laravel-starter) Github boilerplate repository to get access to a project that already has Laravel, Tailwind CSS, and Flowbite set up for development.
136 |
137 | For even more resources and UI components you can check out [Flowbite Pro](https://flowbite.com/pro/).
--------------------------------------------------------------------------------
/content/getting-started/license.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Flowbite - License
4 | description: Learn more about the licensing terms for Flowbite and Tailwind CSS
5 | group: getting-started
6 | toc: true
7 |
8 | previous: LLM
9 | previousLink: getting-started/llm/
10 | next: Changelog
11 | nextLink: getting-started/changelog/
12 | ---
13 |
14 | ## Copyright
15 |
16 | The Flowbite name and logos are trademarks of Bergside Inc. Learn more about the [Flowbite Brand Guideline](https://flowbite.com/brand/).
17 |
18 | ## Released code
19 |
20 | The released code is licensed under the [MIT license](https://github.com/themesberg/flowbite/blob/main/README.md).
21 |
22 | Copyright (c) Themesberg (Bergside Inc.)
23 |
24 | Permission is hereby granted, free of charge, to any person obtaining a copy
25 | of this software and associated documentation files (the "Software"), to deal
26 | in the Software without restriction, including without limitation the rights
27 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
28 | copies of the Software, and to permit persons to whom the Software is
29 | furnished to do so, subject to the following conditions:
30 |
31 | The above copyright notice and this permission notice shall be included in all
32 | copies or substantial portions of the Software.
33 |
34 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
35 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
36 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
37 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
38 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
39 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
40 | SOFTWARE.
41 |
42 | ## Documentation
43 |
44 | The docs code is licensed under the [CC BY 3.0](https://creativecommons.org/licenses/by/3.0/).
45 |
46 | Attribution: the documentation code was initially forked from [Bootstrap](https://github.com/twbs/bootstrap) created by the [Bootstrap authors](https://github.com/twbs/bootstrap/graphs/contributors) and [Twitter Inc.](https://twitter.com/) and changes have been made since then to adapt to the Tailwind CSS and Flowbite ecosystem and technologies.
47 |
48 | ## Pro version
49 |
50 | The pro version is licensed under the [EULA](https://flowbite.com/license/) from our website.
--------------------------------------------------------------------------------
/content/getting-started/llm.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS AI and LLM - Flowbite
4 | description: Learn how to integrate Flowbite and Tailwind CSS with any LLM interface such as OpenAI, Anthropic, or Gemini to leverage the power of AI and LLMs in your web applications
5 | group: getting-started
6 | toc: true
7 |
8 | previous: TypeScript
9 | previousLink: getting-started/typescript/
10 | next: License
11 | nextLink: getting-started/license/
12 | ---
13 |
14 | You can use Flowbite and Tailwind CSS together to generate UIs and integrate them into your own tech stack using LLMs and AI tools such as Windsurf or Cursor based on AI models from OpenAI, Anthropic, Gemini and more. We provide a basic `llms.txt` based on the [LLMs standard](https://llmstxt.org/) that you can use to feed data.
15 |
16 | LLMs and AI integration tools are now a standard way of working in the web industry and it can drastically improve your workflow and productivity. We recommend using our UI library and resources as a stable base for your AI integration.
17 |
18 | AI still has shortcomings and limitations and it is not a replacement for human work. However, that doesn't mean you can't leverage it to generate UIs and components faster and more efficiently.
19 |
20 | ## API routes for LLMs
21 |
22 | The LLMs files are hosted on the following routes on Flowbite:
23 |
24 | - `https://raw.githubusercontent.com/themesberg/flowbite/refs/heads/main/llms.txt` - this is the main file that you can use to feed data to your AI tools
25 | - `https://raw.githubusercontent.com/themesberg/flowbite/refs/heads/main/llms-full.txt` - this is the full file that is much larger and contains more data
26 |
27 | On a general level, the first file should be enough for LLMs that are able to parse the web.
28 |
29 | ## Markdown files
30 |
31 | Our documentation is hosted on GitHub and you can parse the markdown files directly too:
32 |
33 | - `https://github.com/themesberg/flowbite/blob/main/content/components/accordion.md` - this is an example of a documentation file for the accordion component
34 | - `https://github.com/themesberg/flowbite/blob/main/content/getting-started/angular.md` - this is a documentation file for the Angular integration guide
35 |
36 | We recommend checking out the [content folder](https://github.com/themesberg/flowbite/tree/main/content) from GitHub to view all documentation files.
37 |
38 | ## Implementation examples
39 |
40 | You can use the following code examples to implement LLMs in your web application:
41 |
42 | ```javascript
43 | async function getLLMData() {
44 | const response = await fetch('https://raw.githubusercontent.com/themesberg/flowbite/refs/heads/main/llms.txt');
45 | const data = await response.text();
46 | return data;
47 | }
48 |
49 | console.log(await getLLMData());
50 | ```
51 |
52 | ## Flowbite AI
53 |
54 | We are currently working on a Flowbite AI feature that will allow you to generate UIs and components using AI models from OpenAI, Anthropic, Gemini and more. One of the features will be to convert your Figma designs into code and generate components using Flowbite and Tailwind CSS.
55 |
56 | If you'd like to be notified when the Flowbite AI feature is available, please sign up below to our newsletter.
--------------------------------------------------------------------------------
/content/getting-started/react.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS React - Flowbite
4 | description: Learn how to install Tailwind CSS with Flowbite for your React project and start developing modern web applications using interactive elements based on utility classes
5 | group: getting-started
6 | toc: true
7 | requires_react: true
8 |
9 | previous: Changelog
10 | previousLink: getting-started/changelog/
11 | next: Next.js
12 | nextLink: getting-started/next-js/
13 | ---
14 |
15 | [React](https://react.dev/) is one of the most popular front-end libraries in the world used by websites such as Facebook, Instagram, Yahoo Mail, Dropbox, and more built by the Meta (formerly Facebook) company.
16 |
17 | Coupled with Tailwind CSS and the React components from Flowbite you will be able to develop applications faster than ever based on the [Flowbite React](https://flowbite-react.com) library using advanced theming functionalities and React specific components and methodologies.
18 |
19 | ## Getting started
20 |
21 | You can easily install or add Flowbite React to an existing project with our new CLI toolkit.
22 |
23 | ## Create a React project
24 |
25 | Use our project creation CLI to scaffold a new application with Flowbite React already configured:
26 |
27 | ```bash
28 | npx create-flowbite-react@latest
29 | ```
30 |
31 | This will create a new project with React, Flowbite, and Tailwind CSS (v4) ready to use.
32 |
33 | ## Add to existing project
34 |
35 | For existing projects, use the Flowbite React CLI to set up and configure everything automatically:
36 |
37 | ```bash
38 | npx flowbite-react@latest init
39 | ```
40 |
41 | This will add Flowbite React and configure Tailwind CSS to an existing React project.
42 |
43 | ## Integration Guides
44 |
45 | Flowbite React is a UI component library that can be integrated with many other technologies and libraries such as Next.js, Astro, Gatsby, Laravel, Remix and more.
46 |
47 | Check out [this page](https://flowbite-react.com/docs/getting-started/quickstart) to learn how to get started with each integration.
48 |
49 | ## React components
50 |
51 | Flowbite React offers a wide variety of UI components such as buttons, dropdowns, modals, datepickers, and more that you can plug and play into your application. Check out the [Flowbite React docs](https://flowbite-react.com/docs/components/button) for more details.
52 |
53 | ## Theme customization
54 |
55 | Flowbite React offers an advanced system of customizing your components and templates using the new [theming engine](https://flowbite-react.com/docs/customize/theme). You can style components by directly using the `className` attribute of the component, but also by passing a theme object to the `` component.
56 |
57 | For example, here is a simple way you can update a button component:
58 |
59 | ```javascript
60 | import { Button } from "flowbite-react";
61 |
62 | function App() {
63 | return ;
64 | }
65 | ```
66 |
67 | Additionally, you can also use the `createTheme` helper to create a theme object that you can then pass on to the `` component with which you can style subcomponents too:
68 |
69 | ```javascript
70 | import { Button, createTheme, ThemeProvider } from "flowbite-react";
71 |
72 | const customTheme = createTheme({
73 | button: {
74 | color: {
75 | primary: "bg-red-500 hover:bg-red-600",
76 | secondary: "bg-blue-500 hover:bg-blue-600",
77 | },
78 | size: {
79 | lg: "px-6 py-3 text-lg",
80 | },
81 | },
82 | });
83 |
84 | function App() {
85 | return (
86 |
87 |
88 |
91 |
92 | );
93 | }
94 | ```
95 |
96 | ## Storybook
97 |
98 | Flowbite React also has a [Storybook](https://flowbite-react.com/storybook) version which you can use to preview and test components in isolation.
99 |
100 | ## Open-source community
101 |
102 | The Flowbite React UI library is an open-source project under the MIT license. You can access the source code on [GitHub](https://github.com/themesberg/flowbite-react) and collaborate with our community of developers to contribute to its growth.
103 |
104 | ## Support development
105 |
106 | If you’d like to support our open-source work, you can explore the [pro version](https://flowbite.com/pro/) of Flowbite, which offers 400+ components and templates, a Figma design system, an admin dashboard, and more.
--------------------------------------------------------------------------------
/content/plugins/datepicker.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: redirect
3 | sitemap_exclude: true
4 | redirect: "/docs/components/datepicker/"
5 | ---
--------------------------------------------------------------------------------
/content/typography/hr.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home
3 | title: Tailwind CSS Horizontal Line (HR) - Flowbite
4 | description: Create a horizontal line using the HR tag to separate content such as paragraphs, blockquotes, and other elements using the utility classes from Tailwind CSS
5 | group: typography
6 | toc: true
7 |
8 | previous: Text
9 | previousLink: typography/text/
10 | next: Charts
11 | nextLink: plugins/charts/
12 | ---
13 |
14 | The HR component can be used to separate content using a horizontal line by adding space between elements based on multiple styles, variants, and layouts.
15 |
16 | ## Default HR
17 |
18 | Use this example to separate text content with a `` horizontal line.
19 |
20 | {{< example id="default-hr-example" github="typography/hr.md" show_dark=true >}}
21 |
Track work across the enterprise through an open, collaborative platform. Link issues across Jira and ingest data from other software development tools, so your IT support and operations teams have richer contextual information to rapidly respond to requests, incidents, and changes.
22 |
23 |
Deliver great service experiences fast - without the complexity of traditional ITSM solutions.Accelerate critical development work, eliminate toil, and deploy changes with ease, with a complete audit trail for every change.
24 | {{< /example >}}
25 |
26 | ## Trimmed
27 |
28 | Use this example to show a shorter version of the horizontal line.
29 |
30 | {{< example id="hr-trimmed-example" github="typography/hr.md" show_dark=true >}}
31 |
Track work across the enterprise through an open, collaborative platform. Link issues across Jira and ingest data from other software development tools, so your IT support and operations teams have richer contextual information to rapidly respond to requests, incidents, and changes.
32 |
33 |
Deliver great service experiences fast - without the complexity of traditional ITSM solutions.Accelerate critical development work, eliminate toil, and deploy changes with ease, with a complete audit trail for every change.
34 | {{< /example >}}
35 |
36 | ## Icon HR
37 |
38 | This example can be used to set a custom [SVG icon](https://flowbite.com/icons/) in the middle of the HR element.
39 |
40 | {{< example id="hr-icon-example" class="text-center" github="typography/hr.md" show_dark=true >}}
41 |
Track work across the enterprise through an open, collaborative platform. Link issues across Jira and ingest data from other software development tools, so your IT support and operations teams have richer contextual information to rapidly respond to requests, incidents, and changes.
42 |
43 |
44 |
45 |
48 |
49 |
50 |
Deliver great service experiences fast - without the complexity of traditional ITSM solutions.Accelerate critical development work, eliminate toil.
51 | {{< /example >}}
52 |
53 | ## HR with text
54 |
55 | Use this example to add a text in the middle of the HR component.
56 |
57 | {{< example id="hr-text-example" class="text-center" github="typography/hr.md" show_dark=true >}}
58 |
Track work across the enterprise through an open, collaborative platform. Link issues across Jira and ingest data from other software development tools, so your IT support and operations teams have richer contextual information to rapidly respond to requests, incidents, and changes.
59 |
60 |
61 | or
62 |
63 |
Deliver great service experiences fast - without the complexity of traditional ITSM solutions.Accelerate critical development work, eliminate toil.
64 | {{< /example >}}
65 |
66 | ## HR shape
67 |
68 | This example can be used to separate content with a HR tag as a shape instead of a line.
69 |
70 | {{< example id="hr-shape-example" github="typography/hr.md" show_dark=true >}}
71 |
Track work across the enterprise through an open, collaborative platform. Link issues across Jira and ingest data from other software development tools, so your IT support and operations teams have richer contextual information to rapidly respond to requests, incidents, and changes.
72 |
73 |
74 |
"Flowbite is just awesome. It contains tons of predesigned components and pages starting from login screen to complex dashboard. Perfect choice for your next SaaS application."