feat: initial release

[griimick]

scss partials hierarchy

• ctp-<variant>.scss: each theme will have its palette defined and @use the following
• theme.scss: theme color range and accent colors (full palette and specific accent support)
• ctp-vars.scss: catppuccin app variables (future custom customization support)
  • variables applied to downstream
• custom.scss: place for all the defined selectors for specific UI elements customisations
  • selectors for outliers (not handled by logseq variables)
• ls-vars.scss: logseq app variables (refer the logseq source code)

variable usage

// ctp-<variant>.scss
--ctp-surface1: x, y, z

// theme.scss: apply specific accent if defined else fallback for full-palette
--ctp-color-100: rgb(--ctp-accent, --ctp-surface1)

// ctp-vars.scss: single place to customise the theme (potentially expose this to settings)
--ctp-component-color: var(--ctp-color-100)
--ctp-switch-background: var(--ctp-accent, --ctp-surface1)

// custom.scss: for elements which need custom selectors for customisation
a.ui__toggle > span {
    background-color: var(--ctp-switch-background)
}

// ls-vars.scss: default variables defined and used by logseq
--ls-component-color: var(--ctp-component-color);

Roadmap

Aim is to cover main layout and pages. Target only colors for first release.

• [x] groundwork for for accent and basic element customisation for support from day 0
• [x] fill up variables used by logseq and assess what remains
• [ ] more breakdown based on assessment or go for first release

Feature and Plugins

• [ ] Left and right sidebar
• [x] Header
• [ ] Settings
• [x] Plugins page (Marketplace)
• [x] Search
• [ ] All Pages
• [ ] Journals
• [ ] Graph View
• [ ] Flashcards
• [x] Markdown and styles

Components

• [x] Switches
• [x] Button
• [x] Dropdown
• [x] Tooltip
• [x] Table
• [ ] Block/Page preview

[griimick]

• Dropping the thought of a full palette for the first release. Too much cognitive load with color decisions. I will be focusing on a single palette scheme for the initial release.