DaisyFT
Overview
DaisyFT is a toolkit for building beautiful web interfaces with FastHTML, Tailwind CSS, and DaisyUI. It provides a streamlined workflow for creating modern, responsive web applications in Python.
Documentation
Visit our comprehensive documentation at daisyft.com for guides, examples, and API reference.
Features
- 🚀 Quick Setup: Initialize a FastHTML project with Tailwind CSS and DaisyUI in seconds
- 🔄 Live Reload: Develop with instant feedback using the built-in dev server
- 🛠️ Build System: Optimize your CSS for production with a single command
- 🔌 Sync Command: Keep your Tailwind binary and configuration up to date
Installation
pip install daisyft
Quick Start
# Initialize a new project
daisyft init
# Start the development server
daisyft dev
# Build for production
daisyft build
# Build your css and run your app
daisyft run
Commands
daisyft init: Create a new project with minimal setupdaisyft init --advanced: More configuration optionsdaisyft init --binaries: Download Tailwind binaries only without modifying project filesdaisyft dev: Start the development serverdaisyft build: Build CSS for productiondaisyft run: Run the FastHTML applicationdaisyft sync: Update Tailwind binary and configuration
Configuration
DaisyFT uses a daisyft.toml file for configuration. This file is created automatically when you run daisyft init and used to customize the cli.
[project]
style = "daisy" # Options: "daisy", "tailwind"
theme = "dark" # Options: "dark", "light"
Opinionated Project Structure
Here's the structure new projects default to, which can be customized:
my-project/
├── main.py # Main FastHTML application
├── daisyft.toml # DaisyFT configuration
├── static/ # Static assets
│ ├── css/ # CSS files
│ │ ├── input.css # Tailwind/DaisyUI input
│ │ └── output.css # Generated CSS
│ └── js/ # JavaScript files
└── components/ # FastHTML components
Roadmap
- Documentation: ✅ Available at daisyft.com
- Component System: A library of reusable UI components (coming soon)
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for daisyft 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| daisyft-0.1.8.tar.gz | 57.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| daisyft-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 81.1 kB
Release files / daisyft-0.1.8.tar.gz
| Download URL | daisyft-0.1.8.tar.gz |
|---|---|
| Size | 57.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58c9f237abd8b015a0abf8ff2b55a74bacb55079b7e3f2902cfb624dce1f7fbd
|
|
BLAKE2b-256 checksum How to use checksums |
e194369e56f74b98a02c42a964a52fe977e9de89f894a0e1697020bacbed815f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 3, 2025.
Transparency logRelease files / daisyft-0.1.8-py3-none-any.whl
| Download URL | daisyft-0.1.8-py3-none-any.whl |
|---|---|
| Size | 23.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cae37a4f6be8b29e56e92d7f2029ac4f116ce2de1e59f2175576943393f47c30
|
|
BLAKE2b-256 checksum How to use checksums |
74a32278aef85476ee43301377b348721257ad9576a69257ca95517817ce2453
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 3, 2025.
Transparency log