60 docs tagged with "Internal"

Motivation

Authoring features are a collection of authoring-time behaviors in the editor: operations that rewrite node parameters to achieve an intended visual result, rather than relying on runtime transforms or renderer-specific tricks.

Key terms and concepts from the Chromium compositor (cc/) and display

The Chromium compositor (cc/) is responsible for taking painted content

Research findings from reading the Chromium source code (chromium/cc/,

The scheduler orchestrates the frame production pipeline. It receives

The damage tracking system computes the region of each render surface that

How Chromium optimizes visual effects (blur, shadow, opacity, blend modes,

How Chromium maintains smooth interaction (scroll, pinch-zoom) even when

Memory Budget

How Chromium stores and accesses per-node data across its rendering

How Chromium records, stores, and replays paint operations. The recording

Complete mechanism for how Chromium handles pinch-to-zoom: the immediate

The compositor stores layer properties (transform, effect, clip, scroll) in

A render surface is an offscreen GPU texture that a subtree is composited

Source-level analysis of how Chromium handles rendering resolution during

How Chromium handles the SVG `` element. The pattern element is a

Tiling Model

Deep dive into Chromium's tiling implementation from source (cc/).

A working group draft describing the Grida ID Model (for CRDT) feature for the core engine.

Chromium Blink's single source of truth for CSS property metadata, used as a reference for browser-grade CSS cascade implementation

Renderer-agnostic model for attaching glyphs (arrowheads, markers, ticks) to 2D paths using the path's local frame.

Editor features are a collection of Grida editor-specific behaviors and capabilities. These documents focus on practical implementation details over mathematical abstractions, emphasizing real-world UX and editor workflows.

| feature id | status | description |

Scope: Fonts & Images (WASM / Embedded)

Implementation details behind importing .fig files into Grida.

| feature id | status | description |

| feature id | status | description |

This document proposes the philosophical basis for the fundamental toolset, enabling machines to design like humans.

| feature id | status | description | PRs |

| feature id | status | description |

This document proposes the philosophical basis for image manipulation tools that enable AI agents to generate, enhance, and transform visual content within the design canvas.

Hypothesis

| feature id | status | description | PRs |

Overview

Universal positioning, dimensions, layout management with anchors, flex and grid.

| feature id | status | description |

| feature id | status | description | PRs |

Procedural fractal Perlin noise effects with SVG filter semantics

| feature id | status | description | PRs |

Core / Modeling

Working group documents for Grida platform and infrastructure topics.

Per-side stroke widths for rectangular shapes (CSS border equivalent)

A summary of optimization techniques for achieving high-performance

Fonts & Images (WASM / Embedded)

Purpose

| feature id | status | description | PRs |

This document describes the selection behavior for pointer interactions and keyboard modifiers.

How node-level opacity interacts with fill and stroke paint when they

Pattern fills for SVG shapes — tiling a subtree as a repeating paint

This document describes the testing methodology and tools used to evaluate SVG rendering accuracy in Grida Canvas.

Status: Active — describes the current import strategy.

Motivation

Motivation

A working group draft describing the Unicode Coverage Tracker (UCT) feature for the core engine.

Summary

UX Surface documents specify Grida editor's specific practical UX specifications for surface interactions, selection, targeting, and related user interface behaviors.

see PR #408

Why Real WASM Benchmarking Matters

Welcome to the Grida Working Group documentation!