You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifying Emerald / Amber in the YAML breaks styling in the live server (no colors (white) or something else), but the generated website uses Emerald / Amber correctly.
Properly solving this (and #118) will require support for compiling Tailwind on the fly in live server of Ema: srid/ema#20
In the interim, perhaps we can allow disabling compiling Tailwind (so CDN is used) during static generation, e.g.: emanote gen --no-tailwind-compile .... Or it can be specified in index.yaml.
Describe the bug
The live server and the generated website use different colors from tailwind.
reference: https://tailwindcss.com/docs/customizing-colors
Specifying "green" in the yaml file makes the live server use the color "emerald", but the generated website uses green.
Does not seem to affect the color blue for some reason.
It might affect more colors than green and yellow.
Example:
Using the
docs/
folder in https://github.com/EmaApps/emanote/Build the website, and run a live server with
emanote run --port=8081
Open these two pages:
https://emanote.srid.ca/guide/yaml-config
http://localhost:8081/guide/yaml-config
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: