I stored Tailwind classes in the database. After the build, half of the styles disappeared

The author shares their experience with a non-standard technical challenge: storing raw HTML with Tailwind CSS classes directly in a database. During development, a problem arose where some styles failed to render after the project build. The root cause lies in how the Tailwind JIT compiler works; it scans source files to generate CSS. Since the classes stored in the database are not part of the project's static files, the builder does not 'see' them and excludes them from the final bundle. The article explores the reasons behind this conflict and suggests solutions, including configuring scan paths or using specific settings for dynamically generated content. This case study highlights the importance of understanding build tools when integrating dynamic content into modern web applications.