---
title: "Roadmap"
description: "What Nyxel supports now and which platform capabilities come next."
canonical_url: "https://nyxel.dev/docs/roadmap"
markdown_url: "https://nyxel.dev/docs/roadmap.md"
---

# Roadmap
URL: /docs/roadmap
LLM index: /llms.txt
Description: What Nyxel supports now and which platform capabilities come next.

# Roadmap

Nyxel’s local architecture is functional: typed components, mixed renderer composition, JSON templates, Yjs-backed drafts, Canvas, Preview sessions, Shopify route data, and a reference storefront operate together in the monorepo.

## Now

The immediate product is the developer workflow. A developer can clone the repository, run the storefront and editor, author a typed component, compose templates visually, bind Shopify data, test the real route in Preview, save JSON, and validate the result through the CLI.

The reference theme covers the core storefront routes and interaction patterns needed to exercise that workflow. It is a foundation for theme development, not a catalog of every storefront feature.

## Future

The next platform boundary is secure persistence and release management. **Partial:** Nyxel Connect now has a standalone host, Shopify installation sessions, Redis-backed project and release records, bounded editor handoffs, GitHub/Vercel provider clients, Preview deployment creation, deployment polling, and scheduled promotion. It still needs customer-owned provider authorization, live installation proof, webhook reconciliation, production rollback, and operational hardening against real merchant infrastructure.

Developer onboarding also needs a supported project creation flow, published package releases, and a deployment guide that does not assume the monorepo.

Collaboration can build on the existing action and Yjs model after one authenticated editor session is reliable. That includes presence, shared cursors, comments, and conflict-aware remote synchronization.

A Liquid Bridge theme may provide narrowly scoped access to Shopify-native theme app extensions. It remains separate from the Astro storefront and should only be introduced where a real app-block requirement cannot be met through a headless integration.

The roadmap does not require every framework adapter or commerce feature to expand at once. New capability should enter when it advances a complete developer or merchant workflow and can be verified on the real storefront surface.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).