docs: point at the playground, which nothing linked to
docs: authoring without `new`, including your own components
The factory surface had no page of its own: the README showed it, the template
used it, and anyone asking "why does this compile without a `new`?" had nowhere
to look. Worse, the answer everyone reaches for — "that must be a framework-only
trick" — is wrong, and nothing said so.
DeclarativeSurface covers the contract (named like the type, mirrors a
constructor, no overloads, `children` last), how an app's own components join it
through the generator, the widest-constructor rule and `[UiFactory]`, EQ3101 and
EQ3102, and the one sharp edge: a factory shadows its type, but only for types
that arrive through a `using` — so your own are never shadowed, and `Gap` and
`DotBadge` exist for the framework's two that are.
Also the `dotnet clean` note for a renamed generator, because eqc reads the
generated FILES and the compiler never removes what a generator stopped writing.
docs: one styling engine — the Tailwind adapter is gone
Styling now documents the single pipeline (typed C# to atomic CSS / GPU paint)
and a bring-your-own-CSS note on the escape hatch; the Tailwind package page,
build-flow stages and examples are removed or made framework-neutral.
docs: present the product as a single, settled design
The wiki now describes what eQuantic.UI is — never what it used to be. Removed
every legacy banner, migration log, slice label, internal date, baseline
progression and discarded-decision story across 18 pages; changelog pages fold
into their product pages and remain as pointers; the roadmap lists only what
is ahead. Facts were verified against the source tree while rewriting (golden
count, Vulkan backend, theme bridge, Tailwind property names).
📝 docs: o modelo do editor de código, densidade, degraus densos e a face mono
📝 docs: the 2026-07-31 state — excision, Track S, motion/gestures, waves 3/3b, the macOS shell, real text+icons
Home/WriteOnceComponents/DesignSystem/Photon/Roadmap reconciled with the repo:
write-once is the ONLY architecture (28 components), styling is CSS-free via
the atomic engine, theming is IAppTheme (Photon + Material 3 dynamic color),
Photon renders real text (CoreText) and icons (pure-C# SVG parser + CG) inside
a real NSWindow shell, 17/17 Metal parity, 74 goldens. Legacy pages
(Components/Styling/TailwindUpdates) carry excision warnings. Roadmap rewritten
against ROADMAP.md incl. Track E (the VS Code visual editor).
📝 docs: the native/write-once era — Photon, WriteOnceComponents, DesignSystem + reconciled Home/Roadmap
The wiki predated the entire mobile track. New pages:
- Photon: the proprietary GPU engine (normative Sdf core, golden harness,
Metal parity at ±1 LSB, component-rendering state, no-Skia decision).
- WriteOnceComponents: the shared architecture (vocabulary, realizers,
runtime-provided library, semantic import routing, write-once pages,
migration state 8/~54).
- DesignSystem: typed tokens, spec-fidelity testing, and the
generated-never-hand-written pipeline (CSS/TS/icons/fixtures).
Home gains the Native & Write-Once section and the updated framing (web AND
native from one C# source); Roadmap gains Phases 7-9 (Photon, unification,
migration waves) with the current gates; Architecture/Components carry
banner notes pointing web-only readers to the new world.
📝 docs(image): add comprehensive documentation for server-side image optimization
✨ feat(build): introduce BunPackage for npm dependencies and new UI components
📝 docs(system): restructure and enhance core documentation
Introduces new documentation for Asset Management, Component System, and Server Integration. Deletes outdated Component Robustness and Core Components docs, and
📚 docs: add comprehensive component robustness documentation
- Add ComponentRobustness.md with complete feature documentation
- Add TailwindUpdates.md tracking Tailwind package updates
- Update Home.md to include new documentation links
- Update Styling.md with component robustness section
Features documented:
✨ Compound Components Pattern (Card, CardHeader, CardTitle, etc.)
✨ Granular Variants (CardVariant enum with 5 options)
✨ Controlled/Uncontrolled components (TextInput, Select, Checkbox)
✨ Loading States (Button.Loading with automatic spinner)
✨ Error States & Validation (FormField component)
✨ Input Groups (InputGroup + InputAddon)
✨ Data & ARIA Attributes (native HtmlElement support)
✨ XML Documentation (complete IntelliSense support)
Tailwind updates:
- ButtonTheme: Added loading state support with data attributes
- CardTheme: Added 5 variants + Title/Description support
- InputTheme: Added GetVariant() for validation states
- IInputTheme: Updated interface with GetVariant() method
All updates are backward compatible with zero breaking changes.
📝 docs: add comprehensive CompileTimeEvaluation documentation
Added detailed documentation for the CompileTimeEvaluator system covering:
- Overview and key concepts of compile-time evaluation
- How symbolic compilation works (detection, pattern recognition, execution)
- 5 supported patterns (interpolated string, string.Join, string.Format, passthrough, binary)
- Architecture diagrams and evaluation flow
- Real-world usage examples with TailwindClass
- Performance benefits (42% smaller bundles, 33% faster first paint)
- Extensibility guide for adding new patterns
- Limitations and best practices
- Debugging tips and diagnostic tools
Updated Home.md to include link to new documentation.
📝 docs(compiler): add supported C# features matrix
📝 docs(architecture): introduce self-contained package architecture and update build flow
📝 docs(runtime): add comprehensive debugging and development guide
📝 docs(wiki): add External Type Resolution documentation
Add comprehensive guide for resolving external types in component compilation.
Features documented:
- SemanticModelProvider with project compilation support
- ProjectCompilationHelper for loading full project context
- ComponentCompiler.SetProjectCompilation() API
- Before/after examples with User model
- Architecture diagrams and usage examples
- 5 new tests validating external type resolution
📝 docs(build): update documentation for build flow, styling, and diffing strategy
📝 docs(documentation): translate documentation to English, update roadmap, and add theme & styling system details
📝 docs(wiki): remove .md extension from internal links
📝 docs(wiki): create comprehensive documentation wiki with core articles