You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A modern, semantically-aware WordPress theme powered by *ReScript*, *Deno*, and *WASM*. Sinople (from the heraldic term for green) combines traditional WordPress theming with cutting-edge semantic web technologies for character relationships, glosses, and knowledge graphs.
8
8
9
+
== Current Status
10
+
11
+
Sinople is currently best understood as an ambitious integration prototype rather than a finished production platform.
12
+
13
+
* The repo contains real WordPress, ReScript, and WASM implementation work.
14
+
* Several headline claims still outrun the automated test surface and the audit record in link:RSR_AUDIT.md[RSR_AUDIT.md].
15
+
* In particular, Micropub/auth, accessibility verification, and standards-compliance claims should be treated as in-progress unless separately evidenced.
16
+
9
17
== Features
10
18
11
19
- 🧠 *Semantic Web Processing*: RDF/OWL processing via Rust WASM for construct relationships
12
-
- 🌐 *IndieWeb Level 4*: Full Webmention and Micropub support
13
-
- ♿ *WCAG 2.3 AAA*: Maximum accessibility compliance
20
+
- 🌐 *IndieWeb Integration Work*: Webmention and Micropub-related endpoints exist, but the auth/completeness story is still in progress
21
+
- ♿ *Accessibility-First Direction*: strong accessibility intent, but full AAA-style verification is still pending
14
22
- 🔒 *Type Safety*: ReScript-only architecture (NO TypeScript)
Copy file name to clipboardExpand all lines: sinople-theme/ROADMAP.adoc
+37-9Lines changed: 37 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,20 +3,48 @@
3
3
4
4
== Current Status
5
5
6
-
Initial development phase.
6
+
This repo is a broad prototype and integration surface, not a finished platform.
7
+
8
+
* The theme contains real implementation across WordPress, Rust/WASM, and ReScript.
9
+
* Public-facing claims currently outrun the evidence in `RSR_AUDIT.md` and the small test surface.
10
+
* The most useful role for this repo right now is to act as the application proving ground for the rest of the stack.
11
+
12
+
== P0 Release Blockers
13
+
14
+
* [ ] Reconcile README-level claims with `RSR_AUDIT.md`, especially around RSR status, Micropub, and production readiness.
15
+
* [ ] Replace placeholder or partial security/auth flows, especially the documented Micropub-auth placeholder.
16
+
* [ ] Create a real automated test baseline for the WordPress theme and semantic components.
17
+
* [ ] Define a narrower supported feature set instead of claiming the full conceptual surface at once.
18
+
19
+
== P1 Product Focus
20
+
21
+
* [ ] Treat the WordPress theme plus one or two distinctive semantic features as the release core.
22
+
* [ ] Add accessibility regression checks before making WCAG AAA-style claims.
23
+
* [ ] Add deployment and operator guidance that clearly distinguishes experimental features from supported ones.
24
+
* [ ] Use `php-aegis`, `project-wharf`, and `http-capability-gateway` as upstream hardening layers rather than replicating their responsibilities here.
25
+
26
+
== P2 Platform Growth
27
+
28
+
* [ ] Expand tests across WASM, ReScript, and WordPress integration paths.
29
+
* [ ] Decide which advanced features are real near-term scope and which belong in design documents only.
30
+
* [ ] Add one authoritative current-status document and demote stale or aspirational summaries.
0 commit comments