Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
razor-ui - Skill - OpenSmartRoute
Skillv1.0.0
razor-ui
Follow the repository [UI standards guide](../../docs/ui-standards-guide.md).
Gate resource-sensitive UI with the existing policy and policy-resource
tag-helper pattern; use PotentialAccessProbe.Instance when asking whether an
action is possible before a concrete resource exists.
Use a dedicated confirmation page for primary-entity deletion or the existing
data-confirm pattern for inline destructive actions. Do not add inline
onclick or onsubmit confirmation code.
Do not introduce legacy UI constructs such as control-label, help-block,
float-e-margins, btn-xs, dl-horizontal, admin-actions-filters,
deprecated Font Awesome aliases, or type="button" on links.
Validate changed views with a Razor-compiling build.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/frasermolyneux-portal-web-razor-ui-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.