Skip to content

Commit 2f020ed

Browse files
committed
Add Vix roadmap page and homepage roadmap section
1 parent 158b31c commit 2f020ed

4 files changed

Lines changed: 1007 additions & 95 deletions

File tree

vix-site/src/data/home.js

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -393,6 +393,39 @@ vix dev`,
393393
},
394394
],
395395
},
396+
397+
stableFoundation: {
398+
eyebrow: "Stable foundation",
399+
title: "What Vix.cpp already provides",
400+
subtitle:
401+
"Vix.cpp already includes the core pieces needed to build, run, test, package, and document modern C++ applications with less friction.",
402+
cta: {
403+
label: "View the roadmap",
404+
to: "/roadmap",
405+
},
406+
items: [
407+
{
408+
label: "Developer workflow",
409+
title: "Project workflow",
410+
text: "Create projects, install dependencies, run locally, build, test, format, verify, and package C++ applications with a cleaner workflow.",
411+
},
412+
{
413+
label: "Runtime foundation",
414+
title: "Runtime and modules",
415+
text: "Use a growing runtime foundation with modules such as async, cache, core, db, fs, json, kv, log, middleware, net, orm, p2p, process, sync, threadpool, validation, websocket, and webrpc.",
416+
},
417+
{
418+
label: "Registry",
419+
title: "Package and registry workflow",
420+
text: "Install, publish, cache, verify, and reuse Vix packages through the registry and local package store.",
421+
},
422+
{
423+
label: "Platform",
424+
title: "Application foundation",
425+
text: "Build native applications, backend services, local-first systems, offline-first workflows, and production-ready tools on top of Vix.cpp.",
426+
},
427+
],
428+
},
396429
};
397430

398431
export default HOME;

vix-site/src/data/roadmap.js

Lines changed: 222 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,222 @@
1+
export const ROADMAP = {
2+
hero: {
3+
eyebrow: "Roadmap",
4+
title: "Vix.cpp Roadmap",
5+
text: "Vix.cpp already provides a strong foundation for building, running, testing, packaging, and documenting modern C++ applications. The roadmap now focuses on refinement, ecosystem growth, production readiness, and making the developer experience even more reliable.",
6+
badges: [
7+
"Stable CLI workflow",
8+
"Runtime foundation",
9+
"Module ecosystem",
10+
"Registry",
11+
"Production focus",
12+
],
13+
},
14+
15+
stableFoundation: {
16+
title: "Stable foundation",
17+
items: [
18+
{
19+
status: "Available",
20+
statusType: "stable",
21+
title: "Developer workflow",
22+
text: "Vix.cpp already supports the core C++ workflow: create projects, install dependencies, run applications, build, test, format, verify, package, and inspect local state with a cleaner CLI experience.",
23+
},
24+
{
25+
status: "Available",
26+
statusType: "stable",
27+
title: "Runtime and modules",
28+
text: "The runtime already includes a broad module foundation covering core utilities, async execution, storage, logging, validation, networking, WebSocket, P2P, sync, templates, process tools, and more.",
29+
},
30+
{
31+
status: "Available",
32+
statusType: "stable",
33+
title: "Registry workflow",
34+
text: "Vix.cpp already has a registry-oriented package workflow with commands for adding, installing, publishing, caching, verifying, listing, updating, and removing packages.",
35+
},
36+
{
37+
status: "Available",
38+
statusType: "stable",
39+
title: "Documentation structure",
40+
text: "The documentation already covers CLI commands, API references, modules, examples, getting started guides, internals, releases, and project setup.",
41+
},
42+
],
43+
},
44+
45+
currentFocus: {
46+
title: "Current focus",
47+
items: [
48+
{
49+
status: "In progress",
50+
statusType: "active",
51+
title: "CLI polish and consistency",
52+
text: "Improve the final user experience across <code>vix new</code>, <code>vix run</code>, <code>vix dev</code>, <code>vix build</code>, <code>vix check</code>, <code>vix tests</code>, replay, diagnostics, and package commands.",
53+
},
54+
{
55+
status: "In progress",
56+
statusType: "active",
57+
title: "Diagnostics and error clarity",
58+
text: "Make C++ errors easier to understand by improving compiler output, runtime hints, codeframes, suggestions, and beginner-friendly explanations without hiding the real build system.",
59+
},
60+
{
61+
status: "In progress",
62+
statusType: "active",
63+
title: "Documentation depth",
64+
text: "Move from basic documentation to deeper guides, API references, module tutorials, production examples, and complete workflows for real-world applications.",
65+
},
66+
{
67+
status: "In progress",
68+
statusType: "active",
69+
title: "Production proof",
70+
text: "Use Vix.cpp in real systems and document what works in production: servers, monitoring tools, WebSocket apps, package workflows, and native backend services.",
71+
},
72+
],
73+
},
74+
75+
phases: {
76+
title: "Next evolution",
77+
items: [
78+
{
79+
phase: "Evolution 1",
80+
title: "Refined developer experience",
81+
text: "Make the already working CLI feel smoother, more predictable, and more professional across project creation, development mode, builds, tests, diagnostics, and releases.",
82+
},
83+
{
84+
phase: "Evolution 2",
85+
title: "Stronger module ecosystem",
86+
text: "Continue improving each module as a reusable building block with cleaner APIs, better tests, better examples, and clearer documentation.",
87+
},
88+
{
89+
phase: "Evolution 3",
90+
title: "Registry maturity",
91+
text: "Turn the registry workflow into a more complete C++ package experience with better discovery, package metadata, verification, publishing, caching, and installation flows.",
92+
},
93+
{
94+
phase: "Evolution 4",
95+
title: "Production-ready platform",
96+
text: "Position Vix.cpp as a serious foundation for native applications, backend services, local-first systems, offline-first workflows, and tools that need native performance.",
97+
},
98+
],
99+
},
100+
101+
tracks: {
102+
title: "Main tracks",
103+
items: [
104+
{
105+
title: "CLI",
106+
text: "Keep improving the command-line experience around project creation, build, run, dev mode, tests, formatting, diagnostics, replay, registry, package commands, and release workflows.",
107+
},
108+
{
109+
title: "Runtime",
110+
text: "Strengthen the runtime layer used to build real applications: HTTP, WebSocket, async execution, filesystem tools, process tools, logging, errors, templates, and runtime services.",
111+
},
112+
{
113+
title: "Modules",
114+
text: "Grow the module ecosystem as independent, reusable C++ building blocks that can be documented, tested, packaged, and reused across projects.",
115+
},
116+
{
117+
title: "Docs",
118+
text: "Make the documentation complete enough for beginners, advanced C++ users, library authors, and teams evaluating Vix.cpp for real applications.",
119+
},
120+
{
121+
title: "Registry",
122+
text: "Improve package discovery, installation, publishing, verification, local caching, global tools, and package lifecycle management.",
123+
},
124+
{
125+
title: "Production",
126+
text: "Show that Vix.cpp is not only a concept or a demo. The goal is to prove it through real applications, benchmarks, production systems, and practical workflows.",
127+
},
128+
],
129+
},
130+
131+
modules: {
132+
title: "Module ecosystem",
133+
text: "Vix.cpp already includes a broad module foundation. The next step is to make each module easier to understand, test, document, package, and use in real applications.",
134+
groups: [
135+
{
136+
title: "Runtime core",
137+
items: ["core", "error", "log", "config", "env", "time", "os"],
138+
},
139+
{
140+
title: "Application development",
141+
items: [
142+
"http",
143+
"middleware",
144+
"websocket",
145+
"webrpc",
146+
"template",
147+
"validation",
148+
],
149+
},
150+
{
151+
title: "Systems and tooling",
152+
items: ["async", "threadpool", "process", "fs", "io", "path", "cache"],
153+
},
154+
{
155+
title: "Data and storage",
156+
items: ["json", "db", "orm", "kv", "conversion"],
157+
},
158+
{
159+
title: "Distributed systems",
160+
items: ["sync", "p2p", "p2p_http", "net", "crypto"],
161+
},
162+
],
163+
},
164+
165+
docs: {
166+
title: "Documentation roadmap",
167+
items: [
168+
{
169+
status: "In progress",
170+
statusType: "active",
171+
title: "CLI guides",
172+
text: "Continue improving the documentation for every major CLI command: new, run, dev, build, check, tests, fmt, install, registry, replay, cache, pack, verify, upgrade, and more.",
173+
},
174+
{
175+
status: "In progress",
176+
statusType: "active",
177+
title: "Module guides",
178+
text: "Expand module-level documentation for async, kv, p2p, sync, threadpool, and the rest of the Vix module ecosystem.",
179+
},
180+
{
181+
status: "In progress",
182+
statusType: "active",
183+
title: "API reference",
184+
text: "Make public APIs easier to discover and understand with clearer reference pages, examples, usage notes, and recommended patterns.",
185+
},
186+
{
187+
status: "Planned",
188+
statusType: "planned",
189+
title: "Real-world applications",
190+
text: "Add deeper examples showing complete applications: HTTP services, WebSocket apps, P2P nodes, package-based projects, local-first systems, and production-style backends.",
191+
},
192+
],
193+
},
194+
195+
longTerm: {
196+
title: "Long-term direction",
197+
items: [
198+
"Make C++ development feel faster, clearer, and less repetitive without hiding the native toolchain.",
199+
"Provide a reliable runtime foundation for native applications, backend services, and developer tools.",
200+
"Build a serious module ecosystem around web, async, storage, sync, networking, validation, logging, and packaging.",
201+
"Make C++ diagnostics easier to understand while keeping the real compiler output accessible.",
202+
"Create a package and registry workflow that feels natural for modern C++ developers.",
203+
"Support local-first and offline-first application foundations through sync, storage, cache, and P2P modules.",
204+
"Prove Vix.cpp through real production systems, not only examples or demos.",
205+
],
206+
},
207+
208+
cta: {
209+
title: "Follow the progress",
210+
text: "Vix.cpp is built in public. The foundation is already here; the next step is refinement, adoption, production proof, and a stronger ecosystem for modern C++ development.",
211+
primary: {
212+
label: "View GitHub",
213+
href: "https://github.com/vixcpp/vix",
214+
},
215+
secondary: {
216+
label: "Read the docs",
217+
href: "https://docs.vixcpp.com",
218+
},
219+
},
220+
};
221+
222+
export default ROADMAP;

0 commit comments

Comments
 (0)