Michael Kappel
- mike@ns12.com
- Phone
- (630) 362-7576
- Location
- Cicero, Illinois
- Professional website
- MikeKappel.com
Public contact path
Contact Michael Kappel and VNWO
Contact the VNWO maintainer about corrections, templates, accessibility barriers, public-site security concerns, implementation examples, or professional collaboration. Do not send secrets, credentials, private files, or personal datasets.
Direct contact
Reach the maintainer without a form or tracking gate.
Include the affected URL or artifact, observed behavior, expected behavior, and VNWO version when reporting a site issue.
Professional experience
More than 20 years of enterprise software delivery focused on .NET and SQL Server modernization, C# and ASP.NET/Core, TypeScript and Angular front ends, API and data systems, and human-reviewed AI-assisted engineering.
- .NET, C#, ASP.NET/Core, and Web API
- SQL Server, T-SQL, data systems, and parity validation
- TypeScript, Angular, typed interfaces, and accessible front ends
- Legacy modernization and human-reviewed AI-assisted engineering
Public profiles
Review professional and public work at the source.
Personal website
Résumé, experience, selected projects, case studies, and direct contact details.
Open MikeKappel.comProfessional experience, role history, and network context.
Open LinkedIn profileGitHub
Public repositories, code samples, and open-source activity.
Open GitHub profilePublic professional, technical, creative, and photography updates.
Open Facebook profileVNWO feedback
Choose the closest issue lane.
Correction request
Report inaccurate wording, stale links, route failures, version mismatches, or human/machine-readable parity gaps.
Template feedback
Identify missing fields, unclear variables, unsafe defaults, absent examples, or better claim-bounded wording.
Accessibility concern
Include the route, assistive technology or input method, browser, viewport, and the barrier encountered.
Public-site security concern
Describe a reproducible issue without sending exploits, credentials, private keys, or private user data.
Suggested report format
Affected route or file:
VNWO version or response header:
Observed behavior:
Expected behavior:
Reproduction steps:
Accessibility or claim-boundary risk, if any:Release diagnostics
For a mixed deployment, include the X-VNWO-Version, X-VNWO-Schema-Version, and X-VNWO-Last-Reviewed-UTC response headers plus the visible page metadata.
Editorial path
Accepted material changes should update the relevant public page, machine-readable artifact, downloads, documentation, version history, and .uai release memory in the same release.