Replace the gruvbox palette with everforest, using the "paper" light
background (#efe6cd) rather than everforest's stock #fffbef, which read too
bright.
- gray is remapped to the everforest neutral ramp: 50-300 are the paper
background steps, 900/950 the dark canvas (#2d353b / #232a2e).
- primary-* variables now carry everforest green (#8da101 light, #a7c080
dark) instead of gruvbox blue.
- article prose gets explicit --tw-prose-* / --tw-prose-invert-* overrides.
The typography plugin ships Tailwind's own grays, so without this the body
copy, headings, rules and code blocks stayed slate on a warm background.
- inline code is hardcoded to indigo-500 by the plugin, so it needs a rule of
its own; links keep primary-400 via the typography config.
- theme-color meta and the logo mark follow the palette.
- the 404 button and the active theme-menu chip were white-on-accent, which
is unreadable on lime (2.9:1); they now use dark text on primary-500
(5.0:1 light, 7.3:1 dark).
Replace the cyan accent and Tailwind gray ramp with gruvbox.
- primary-* now resolves through CSS variables (css/tailwind.css) because
gruvbox uses a different blue for light (#076678) and dark (#83a598);
a single hex cannot serve both modes.
- gray is remapped to the gruvbox neutral ramp (light0 -> dark0), so page
background, headings, muted text and borders all come from the theme.
- body/header/mobile-nav/dropdown/search use bg-gray-50 instead of bg-white
so the canvas picks up light0 (#fbf1c7).
- theme-color meta and the logo mark follow the palette.
- 404 button was hardcoded bg-blue-600; now bg-primary-600.
This commit addresses the issue where an error was logged in the console when the user switched between light and dark modes. The warning was caused by the inappropriate use of SVG tags in JSX. The solution involved correcting the SVG tag usage to comply with JSX syntax requirements.
Closes#974