Oqtane

The product

Oqtane is an open-source CMS and application framework for building web, mobile, and desktop apps on modern .NET. It can host its UI on Static Blazor, Blazor Server, Blazor WebAssembly, or Blazor Hybrid through .NET MAUI, and it is an official .NET Foundation project. Its API documentation is generated automatically with DocFX and published at docs.oqtane.org, and it supports multiple relational database providers.

The developer problem

Oqtane gives .NET developers one framework across several ways to host a UI, and that range is also the hard part. A module written against Blazor Server can meet different constraints under WebAssembly or inside a .NET MAUI app. Each relational database provider is one more place where a schema or a query can behave differently. Generated API reference tells a developer what a type is and what it exposes. It does not say which hosting model and provider a module was tested against, or what changes when a project switches from one to another.

My focus

• Modules and themes. I’d build a sample module and theme first and run them under each hosting model Oqtane supports before writing the guides that go with them.
• Database provider work. I’d focus on schema and query behavior across the supported relational providers, with indexes checked against realistic data volumes rather than a demo database.
• API and developer docs. I’d pair the DocFX-generated reference with task-based guides in one docs-as-code workflow, so both are reviewed and rebuilt on each release.

Why it fits my experience

• At Mitutoyo I worked primarily in C# on the .NET Framework, starting in WinForms and moving to WPF as the product line was modernized, and I built an ASP.NET MVC dashboard so plant managers could see line status in a browser without a client install.
• At Mitutoyo I designed SQL Server schemas for measurement records and tuned the queries as customer databases grew. Indexing decisions that were fine at pilot scale were not fine three years in.
• At Mitutoyo I wrote the internal developer documentation and integration guides for the device APIs used by OEM partners. At Meta I partner with SDK engineers through the release cycle, reviewing API changes early enough that breaking changes ship with migration guidance.