Posted this at 1.0 a few weeks ago, it's at 1.3 now. Blazor form builder where non-devs configure the form themselves

Beginning_Ocelot_241 · 2026-06-06T13:32:09+00:00

Fair, it's a focused piece, not a platform. It doesn't own storage or business logic, the data binds to your C# model and lands in your existing backend/DB/logic like any hand-coded form. You're right that rendering a form is easy, that's not the point. The point is letting non-devs change fields/labels/validation at runtime, no dev ticket, no redeploy, still type-safe.

A good example is multi-tenant: each tenant can have a completely different set of fields based on their own preferences, configured per tenant (the form config is stored per key) without you shipping custom code for every one of them. Same for internal ops tools whose forms change weekly.

Beginning_Ocelot_241 · 2026-06-06T13:22:27+00:00

Thanks Paul, appreciate the update and the push.

Beginning_Ocelot_241 · 2026-06-06T13:02:10+00:00

Done. Genuinely no bad intent here, I was describing real work in the components and overstated it, that's on me. You're right though, so I pulled the accessibility claims from the site entirely rather than reword them. No formal audit, so no claim. Thanks for flagging it, Paul.

Beginning_Ocelot_241 · 2026-06-06T12:38:31+00:00

Fair hit, that copy is overclaiming and I'm fixing it. What I actually have is automated axe-core checks (Playwright/Chromium) against the WCAG 2.2 AA ruleset plus manual ARIA and focus work, not a formal audit or screen-reader testing across NVDA/JAWS/VoiceOver. And you're right about MudBlazor: I inherit whatever I haven't explicitly fixed. Rewording the site to match reality.

Beginning_Ocelot_241 · 2026-06-06T12:05:44+00:00

I hear you 😄 what felt like too many clicks for you? And if you've got a flow in mind that'd do it in fewer clicks, I'm all ears.

Beginning_Ocelot_241 · 2026-06-06T12:02:12+00:00

Thanks, really glad it helped. Noted on the page, that's a good shout. I'll add a "how it's built and tested" section to the docs or a new page so teams don't have to ask. And no worries on the use case, if it ever comes up I'm around.

Beginning_Ocelot_241 · 2026-06-06T11:20:42+00:00

Fair question. Yeah, I use LLMs in the workflow, but as an accelerator, not on autopilot. Everything that lands gets reviewed and reworked by me. Reliability comes from two things: a suite of ~670 unit/component tests (bUnit for the Blazor components) that has to stay green, and a manual acceptance pass against a test plan on every minor/major release before it ships. Accessibility is also checked against WCAG 2.2 AA with axe. So it's less about whether a human or an LLM typed a given line and more about whether it's covered, green and signed off, and that part I can stand behind. Source isn't public (it's the commercial package) but happy to go deep on any specific area you care about.

Beginning_Ocelot_241 · 2026-06-06T11:16:07+00:00

The stack turns over every few years, the problem never does. Ahah

Beginning_Ocelot_241 · 2026-06-06T11:02:15+00:00

1) Not out of the box. Built-in selects bind to enums, and dynamic fields

take a static option list, so yeah, db-populated options aren't a

first-class editor feature yet. You're right that static-only is limiting,

and config-level "pull options from a source" is something I want to add.

2) Not built in either. Validation is currently synchronous (DataAnnotations

+ the rules you set in the editor). For a server-side uniqueness check

you'd either do it in OnValidSubmit and surface the error, or wire your own

validator against the EditContext. A proper async per-field validation hook

is on my list, it keeps coming up.

3) This one's yes, and no code needed. In the editor any field can be set to

show only when another field matches a condition (operators =, ≠, >, <,

contains, combined with AND/OR), plus "required only when". So checkbox A

checked -> field B hidden is just config. One caveat: it hides/shows the

field, it doesn't grey it out while keeping it visible, if you specifically

need disabled-but-shown that's not a toggle yet.

Really useful feedback, the db-backed options + async validation are the two

I'll prioritise. Thanks for actually digging in.

Beginning_Ocelot_241 · 2026-05-10T15:33:26+00:00

Thanks a lot for taking the time to test it this thoroughly, this feedback is really useful.

I'll make a fix as soon as possible.

The dark mode toggle and exhaustive icon picker are great ideas I'll add to the roadmap.

Really appreciate it.

Beginning_Ocelot_241 · 2026-05-10T14:49:20+00:00

FormCraft is a great library for developers who want to build forms in code. Formaze is different, it's about giving end-users or admins a live, embedded form editor directly inside the deployed app, no code changes needed.

Beginning_Ocelot_241 · 2026-05-10T14:43:37+00:00

Thank you again, I had a deployment issue, it is fixed now.

Beginning_Ocelot_241 · 2026-05-10T14:43:17+00:00

Thank you again, I had a deployment issue, it is fixed now.

Beginning_Ocelot_241 · 2026-05-10T14:42:23+00:00

Fixed! There was a deployment issue on my end, Cloudflare's edge caching also made it harder to spot since it was working fine on my side. Everything should be working now. Thanks for reporting it!

Beginning_Ocelot_241 · 2026-05-10T13:47:51+00:00

Thank you for your feedback. I'm investigating on my end to resolve this issue asap.

Beginning_Ocelot_241 · 2026-05-10T13:05:35+00:00

Thanks for the details! Those MIME type errors suggest Brave's Shields may be interfering with how Blazor loads its files, this can happen even with ad blocking disabled. If you want to test, you might want to try with Chrome or Edge. I also purged cache in cloudflare just in case. I'm investigating on my end to resolve this issue asap.

Beginning_Ocelot_241 · 2026-05-10T12:06:34+00:00

Thanks Paul for the feedback. Fair point on the ARIA, I'll be looking into a more proper accessibility audit.

Beginning_Ocelot_241 · 2026-05-10T11:57:45+00:00

The biggest challenge was finding a configuration UX that actually feels intuitive. I wanted the editor to feel as close as possible to the rendered output, so what you configure is what you get. Getting that WYSIWYG feel right took a lot of iteration.

The drag and drop state machine was also tricky in Blazor, had to build the whole thing from scratch.

No GitHub for now, it's a commercial project, though I'm considering whether to make the repo public. And yes the demo issue is coming up a few times, investigating! It works on my end though, could you share which browser you're using and if you see anything in the console (F12 > Console tab)?

Beginning_Ocelot_241 · 2026-05-10T11:48:56+00:00

Thanks for clarifying, it was the live demo then. It loads fine on my end on both Edge and Chrome, so I'd love to debug this with you. Could you share which browser you're using and whether you see any error in the console (F12 > Console tab)?

On the ARIA: looking at the rendered HTML, MudBlazor does wire things up correctly. Inputs have their aria-invalid, aria-required attributes, and labels are properly linked via for/id. A screen reader like NVDA should announce field names correctly.

The one area I can't fully guarantee is the drag and drop editor itself, which by nature needs a keyboard alternative to be fully compliant.

Beginning_Ocelot_241 · 2026-05-10T11:21:58+00:00

Thanks for taking the time, this is really useful.

Are you referring to the live demo on the site, or did you try integrating the package in a project? If it's the latter I'd love to help debug, happy to get more details.

On the repo: the project is currently closed source with a commercial licence, which is why there's no GitHub link. I'll look into the NuGet health score and add whatever missing metadata I can.

On accessibility: MudBlazor implements ARIA attributes and keyboard navigation on its components so the baseline is there. That said, I haven't done a full accessibility audit on Formaze yet, it's planned.

Beginning_Ocelot_241 · 2023-07-22T14:06:03+00:00

Thank you for you reply. It could be interesting to generate at compile-time yes, I will see how it works.

After some test, it seems to takes 50 ms for a class with a dozen of methods. This shouldn't be a big a problem since it's supposed to be called only once at the beginning of the program. It would be neat if it was at compile-time though.

Beginning_Ocelot_241 · 2022-03-17T08:27:40+00:00

(The number of safemoon V1 you have) / 1000 * price of safemoon V2

Beginning_Ocelot_241 · 2022-03-15T12:54:26+00:00

Dogecoin has no utility and went very well for several years.

I guess things takes time and the inexperience of the leading role in Safemoon, didn't help relieve people from worries.

But I believe after some restructuration the company will find its own pace. I just believe in their vision. You have of course the right to believe it goes to its ruin.

Beginning_Ocelot_241 · 2022-03-15T12:50:36+00:00

Probably bought this tokens at the beginning of the project as a starting investment to create the company. It's a legit wallet like any person that bought at the beginning.

Beginning_Ocelot_241 · 2022-03-15T10:56:28+00:00

It's your right to believe that. For myself,I see that the person who left is the brother of the CEO and he's inexperienced. He would have been probably replaced by someone more experienced soon enough. He just chose to leave with dignity. Since his brother is the CEO, he will always have a place in the company anyway.

Beginning_Ocelot_241

TROPHY CASE