# Dynamic UI Rendering The Base Registry includes a dynamic form rendering engine that reads the registry’s JSON schema and generates appropriate UI forms at runtime. Instead of building custom screens for each registry, UI components interpret schema definitions, grouping rules, and widget specifications to render entry forms, detail views, and table listings. Custom field types such as lookup widgets can be declared in the schema and automatically linked with lookup APIs that return enumeration values from centralized metadata. #### Extensible Component Model UI implementers may define new custom components that the renderer can use inside JSON Schema definitions. Apart from the custom domain models that are presented based on the JSON schema configurations, the domain registers (customized and extended) will render themselves using the same hierarchical tab navigation for child registers, verification panels, version history panels, pending change alerts, and de-duplicate screens. This ensures a consistent user experience across all registry types while still allowing domain-specific customizations. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.openg2p.org/products/registry/registry/features/dynamic-ui-rendering.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.