Zacess Themes 0.1.5

Changed

• ANSI black in Zacess Dark and Zacess Yellow on Black is a mid grey (#a3a3a3) instead of a near black, so text a program prints in black stays readable at 7:1 or more. Bright black moves to #c8c8c8 so the two stay apart. Every one of the 16 terminal colours in every theme is now measured as text on the background, with no exceptions, which lets terminal theme catalogues grade all four themes AAA.
• The install guides note that the four themes are in the iTerm2 Color Schemes collection, which Ghostty, WezTerm and other terminals draw from.

Zacess Themes 0.1.4

Added

• Sublime Text colour schemes in editors/sublime, one .sublime-color-scheme per theme. Each names the palette colours as variables, sets the editor colours and maps the same TextMate scopes as the VS Code themes, with bold, italic and underline from the palette's font styles.
• Helix themes in editors/helix/themes, one per theme, with a [palette] table and the interface, diagnostic, diff, Markdown and syntax scopes. Font styles map to Helix modifiers and underlines.
• Emacs themes in editors/emacs, one deftheme file per theme, covering the default, region, current line, line number, mode line, search, parenthesis, diff, Flymake and Flycheck faces, every font-lock face and the 16 ansi-color faces. Each file adds its folder to custom-theme-load-path when loaded.
• npm run check parses the new files: the Sublime Text schemes as JSON, the Helix themes as TOML and the Emacs themes by their brackets. It also proves that every colour, variable and palette name they use comes from the palette.
• Each release attaches zacess-sublime-<version>.zip, zacess-helix-<version>.zip and zacess-emacs-<version>.zip.
• Each release updates two read-only copies with a matching release in each: zacesshq/obsidian-theme for the Obsidian community directory and zacesshq/zacess.nvim for Neovim plugin managers.

Changed

• The install guides link the Obsidian community directory listing and install Neovim from zacesshq/zacess.nvim.

Zacess Themes 0.1.3

Changed

• The install guides link the VS Code Marketplace, Open VSX and JetBrains Marketplace listings. The VS Code guide installs by extension ID instead of a downloaded file. The release files stay available for offline installs.

Zacess Themes 0.1.2

Changed

• Fewer greens in Zacess Yellow on Black: types and classes are lavender (#e5c7ff) instead of light green in VS Code, the JetBrains IDEs, Zed and Neovim, so strings are the only green in code.
• Zacess Yellow on Black in VS Code draws inline code in white, for example in Markdown previews, hovers, settings and extension pages, instead of the string green.
• A new optional code palette role sets the inline code colour. A theme without it keeps the string colour.

Zacess Themes 0.1.1

Changed

• Calmer borders in Zacess Yellow on Black: the borders, dividers and outlines that only separate areas are a neutral grey (#7a7a7a, 4.8:1 on black) in VS Code, the JetBrains IDEs, Obsidian, Zed, Neovim and kitty. Yellow stays for focus, the active tab, selections, buttons and badges, which now share that one yellow accent.
• Zacess Yellow on Black terminals draw their default text in white with a yellow cursor, so yellow and other light ANSI output no longer blends into normal text. ANSI white is #d9d9d9 so it stays distinct from the default text. This covers VS Code, the JetBrains console, Zed, iTerm2, Alacritty, kitty, Ghostty and Windows Terminal.
• Calmer chrome in Zacess Cream: the side bar, activity bar, title bar, status bar and tabs use a quieter warm neutral, while the editor, the terminal and reading surfaces keep the cream #fdf6e3.
• A new borderActive palette role for focus and active borders, so each theme keeps one accent for focus and active states.
• The checks hold every border and divider role, focus and active borders and every border, outline and separator key in the generated VS Code themes to 3:1 on each surface they divide, require every ANSI colour to stay distinct from the terminal's default text and require every fallback sensitive VS Code key to be set with its text at 7:1.

Fixed

• Zacess Cream in VS Code now builds on the normal light base instead of the high contrast light one. Every theme now sets the inline code, code block, quote, separator, hover, notification, quick input, menu, list, input, dropdown, badge, button and keybinding colours itself. Inline code in Markdown previews and extension pages, which showed dark green on navy in Cream, is readable again.

Zacess Themes 0.1.0

Added

• Four themes matching the Zacess reader's contrast themes: Zacess Light, Zacess Dark, Zacess Yellow on Black for low vision and Zacess Cream for dyslexia friendly reading.
• One palette in palette/zacess.json with a JSON schema, holding the interface, syntax and terminal colours of every theme, the font style of each token and the floors the checks enforce.
• A generator that writes a VS Code extension, a JetBrains theme plugin with editor colour schemes, an Obsidian theme with Style Settings options, Neovim colour schemes, a Zed theme extension and iTerm2, Alacritty, kitty, Ghostty and Windows Terminal themes.
• Checks that hold every text and syntax colour to 7:1 contrast on the background, the selection, the current line and the diff backgrounds, test paired tokens for tone and under simulated protanopia, deuteranopia and tritanopia and parse every generated file.
• SVG previews drawn as real text and the data for the themes page on the Zacess website.
• CI that runs the checks, proves the committed files are current, packages the VS Code extension and builds the JetBrains plugin. A release workflow that attaches the .vsix, the JetBrains zip and an Obsidian zip to each GitHub release and publishes to each marketplace once its token is set.