Currently the plugin hardcodes the css input as input_file_path = os.path.join(project_root, "input.css") and similarly the output path as the output folder.
This will cause issues for example when these paths are defined differently in the pelican conf. It also prevents pelican --autoreload from picking up changes in input.css with default settings.
Proposed solution: Allow input and output paths to be configured in the TAILWIND dict.
Also: Kudos for using the tailwind binary! So much cleaner than npm!
Currently the plugin hardcodes the css input as
input_file_path = os.path.join(project_root, "input.css")and similarly the output path as theoutputfolder.This will cause issues for example when these paths are defined differently in the pelican conf. It also prevents
pelican --autoreloadfrom picking up changes ininput.csswith default settings.Proposed solution: Allow input and output paths to be configured in the TAILWIND dict.
Also: Kudos for using the tailwind binary! So much cleaner than npm!