nickjj / nickjj/docker-flask-example

Clarification of tailwindcss configuration

Open
#27 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
765
Forks
139
No merged PRs in 30d

Description

I see assets/tailwind.config.js exists, but according to the .js file is legacy and won't be used unless the @config directive is used to load it. I do not see a corresponding directive in assets/css/app.css so am I correct in assuming the tailwind.config.js is a legacy artifact and can be deleted?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting assets/tailwind.config.js and assets/css/app.css, then compare the current setup with the linked Tailwind @config documentation. Done means establishing whether the configuration file is used and deciding whether it should be removed or retained.

Written by the indexing model from the issue text.

Assessment

Tech stack
tailwindcss
Domain
build-system, frontend
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.