Stencil component comparison

What it is

Stencil compiles reusable web components. This evaluation will produce a component workbench and use a separately exported custom element for a shared chat surface. It is not itself a Markdown wiki generator.

Why test it against Quartz

Quartz remains the operational-wiki baseline. Stencil is being evaluated for framework-independent interactive components that can augment different static-site stacks, rather than replacing Quartz content authoring or indexing. The workbench should demonstrate real component behavior, not only a starter screen. Quartz upstream supplies the wiki baseline.

flowchart LR
  A[Verified upstream sources] --> B[Application preparation pending]
  B --> C[Build and interaction proof pending]
  D[Quartz operational wiki] --> E[Setup and release evidence]

Verified versions and source

Verified on 2026-09-27: @stencil/core 4.45.1, released 2026-09-23; create-stencil 4.0.2. Maintained ecosystem candidates include @ionic/core 9.0.5 and @stencil-community/context 1.0.0. Context and unplugin-stencil are utilities, not visual component libraries. The community app starter last changed in 2024; the archived ionic-pwa-toolkit is excluded.

Stencil · core release · Stencil community · Ionic components

Version lookups establish source provenance, not installed or deployed versions. The project versions.json records exact source pins, lookup dates, and unknown values separately.

Read by task

• setup — source-derived preparation, output paths, and acceptance checks.
• Restricted operations — the intended authenticated full-build operations route.
• Application destination — intended destination, not a current availability claim.

Current status

Application pending. This is the initial wiki-first preparation. No application build, deployment, search interaction, shared chat integration, browser screenshot, or authentication proof is claimed here. Wiki configuration and source content have been prepared; publication and live route verification remain the release owner’s responsibility.

The intended access split is an authenticated application, a public wiki root, and an authenticated full wiki under /private/. This describes the deployment contract, not observed ingress behavior. The public build excludes the source private directory; frontmatter alone is not an access control.