CSS: Tailwind-Build-Pipeline klären / dokumentieren #30
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Needs-v00-Abnahme
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Zentonic/zentonic-publisher#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
█████░░░░░████████░░████░░░░░░█████████░██████░░░░Befund
templates/zentonic22_tailwind/tailwind.config.jsvorhanden, Templates nutzen Tailwind-Klassen + Custom-Klassen (my-card,my-container). Kein klarer Build-Schritt im Generator.Ziel
tailwindcss -i input.css -o /res/style.css --minifybuild.sheinbinden (optional, wennnode_modulesvorhanden)Constraint
Speaker-Spalte:
-rotate-90mit kleinen Avataren und vertikal gedrehter Beschriftung ist gewollt (kompaktes Element neben Episode-Cover). Im neuen CSS-Setup muss dieses Layout reproduzierbar bleiben — Avatare doppelt rotiert (Container-rotate-90, Imagerotate-90), Texte intext-[6px]oder kleinerer Eigenklasse.