Home/Resources/Test Zidom & give feedback
Resources / Zidom JS

Test Zidom & give feedback

Try a real consumer app and share reproducible beta feedback.

Help shape Zidom beta.2#

Zidom is a framework for real applications, not just fast counters. Version 0.1.0-beta.2 is now published as an experimental prerelease. The documentation website still runs pinned @zidomjs/*@0.1.0-beta.1 demos. Please test Beta.2 in a new project and report the exact installed versions.

We're prioritizing broken real-world workflows, confusing documentation, and examples that don't behave as written before adding more framework APIs.

Try the framework, not only the demo#

  1. Follow the getting-started guide in a fresh Vite project outside the Zidom repositories.
  2. Run your counter, change the signal, refresh the page and build for production.
  3. Try the live examples or the interactive playground. Each working browser example shows the source module that it runs.
  4. Build a small flow with two pages, a form and a query. Refresh at a deep link, navigate back, submit invalid input and cancel an in-flight request.
  5. Run your app on desktop and mobile widths, test the keyboard, and switch browser engines where possible.

The docs website is itself a real consumer of the published packages, built with Zidom TSX in a separate repository. Documentation pages are statically generated for reading and SEO; they are not claims that full Zidom SSR/hydration is ready.

Tell us what was difficult#

We're particularly interested in:

  • Onboarding: Was installation, TSX configuration, or the first application confusing?
  • Correctness: Did signals, keyed lists, routing, forms or queries behave differently than expected?
  • Documentation: Did you need to guess at an import, error handling or a package limitation?
  • Examples: Is the code readable next to the live preview? Are the VS Code-style tabs, wrapping, indentation and line spacing useful?
  • Accessibility: Did keyboard, focus, screen readers, light mode or narrow layouts reveal a problem?

A small reproducible bug helps more than a long feature wishlist.

Report a docs or example issue#

Use the following template when reporting a problem. The public issue link below also pre-fills these questions; copy the template if you prefer:

text
●  Zidom
Zidom version: 0.1.0-beta.2Package(s):Node / npm:OS / browser:Page or example URL:What I tried:What I expected:What happened:Minimal steps to reproduce:Console error / screenshot (without secrets):The most confusing part:One improvement that would help:

Public feedback inbox: Submit public Zidom feedback (GitHub sign-in required). The link opens a prefilled issue in the maintainer's public GitHub profile repository. You do not need access to either private Zidom repository. This is a temporary intake route, not a public source-code release. You can also browse existing Zidom reports.

If the issue form is not available to you, copy the report template above and open a new public issue. Reports remain public, and two independent external developer feedback reports were deferred beyond the Beta.2 release.

Never include passwords, API keys, personal information or private customer data in bug reports.

How we'll use feedback#

We will first fix issues that prevent installs, break application behavior or create security problems. Next come docs inaccuracies, inaccessible interactions and confusing examples. Requests for new APIs will be collected but won't automatically be added to the next release.

Read the current release status and explore the feature examples to see exactly which packages and behaviors are implemented.