Request a login and password from support@admingen.dev, naming “Manufacturer website”. Enter the supplied details on the sign-in page. The demo overview explains access and limitations.
This food manufacturer example brings product information and corporate content together. The application can supply data to a brand website, catalogue or other clients.
Structure
| Module | Entities and purpose |
|---|---|
| Products | Brand, ProductLine, Product, PackagingVariant, Ingredient, ProductIngredient, Allergen — product portfolio, packaging, ingredients and allergens |
| Markets | Market, ProductMarket, Distributor — market presence and distributors |
| Corporate | Factory, QualityDocument, NewsArticle, Recipe — factories, documents, news and recipes |
| Virtual views | ProductInformationView and BrandContentView — combined responses for a client website |
Suggested walkthrough
- Start with Brand, then open a product line and product.
- Inspect packaging variants, ingredients and allergens. Switch the content language.
- In ProductMarket, explore how a product is linked to a market, then open a distributor.
- Open QualityDocument. It links document details to a factory and supports a file attachment. Inspect the available file when one is populated.
- Compare ProductInformationView with individual records and its API contract.
This generated example uses one relationship hop in virtual views. Sales processing, production accounting and automatic document approvals are outside its scope.
Apply the approach to your project
Entity names above are the real navigation labels of this demo, not a required model for every application. Start in Content, define your own entities and fields, arrange their forms, then run Generate. Replace ENTITY_NAME and FIELD_NAME placeholders in reference material with names from your project.