Problem

Current hueless color system based on HSL is not working out well and results in poor contrast and inconsistent perceived lightness. The original plan was to switch to OkLCH when it gains browser support, however it does not look like it is getting wide enough adoption soon while the preset is almost ready to launch. We do not want to be inferior to Tailwind in any aspect so this needs to be reworked.

Solution

Remove / rethink hue and highlight utilities, change semantic color configuration to expect OkLCH values, and compile sRGB hex codes in UnoCSS.

It is unclear at the moment whether hue, lightness and chroma should become completely static or accept modifiers (e.g background-normal-setH(45)-addL(10)) especially since it would be no longer possible to propagate them down the DOM using custom CSS properties.

Originally posted by @jojojojojoj5564656465465

Would you be abble to add this to Windblade ;

Hello, would you please explain how to add my custom color system into unocss.config.js?
For instance, i added this, it doesn't work

Type 'Preset<Theme>' is not assignable to type 'Preset<{}> | Preset<{}>[]'. Type 'Preset<Theme>' is not assignable to type 'Preset<{}>'. Types of property 'rules' are incompatible. Type 'Rule<Theme>[] | undefined' is not assignable to type 'Rule<{}>[] | undefined'. Type 'Rule<Theme>[]' is not assignable to type 'Rule<{}>[]'. Type 'Rule<Theme>' is not assignable to type 'Rule<{}>'. Type '[RegExp, DynamicMatcher<Theme>]' is not assignable to type 'Rule<{}>'. Type '[RegExp, DynamicMatcher<Theme>]' is not assignable to type '[string, CSSObject | CSSEntries] | [RegExp, DynamicMatcher<{}>]'. Type '[RegExp, DynamicMatcher<Theme>]' is not assignable to type '[string, CSSObject | CSSEntries]'. Type at position 0 in source is not compatible with type at position 0 in target. Type 'RegExp' is not assignable to type 'string'.ts(2322)

Problem

Currently documentation pages are functions that compose documents with objects and components passed to them which has the following problems:

• many things that are useful in documentation are not possible (links, text effects)
• syntax is not most intuitive
• we are reinventing the wheel which will likely lead to missing / badly designed features

Solution

Keep documentation pages as functions, however change their return types to markdown strings. That way users can still access object like Theme but also get all of the markdown features and a familiar and well-proven syntax.

 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/unocss-preset-windblade: Not Found - 404

This error happened while installing a direct dependency of /home/manjaro/DEV/astro uno/uno

unocss-preset-windblade is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.
Progress: resolved 3, reused 3, downloaded 0, added 0

Tasklist:

• create a documentation workflow
• document utilities that differ from Tailwind counterparts
• build a frontend