Demo projects · 0.8.1

Demos: choose a project and get access

How to sign in, what to explore and how concurrent sessions work.

On this page

Use the demos to explore applications created with Admingen: open records, follow relationships, switch content languages and inspect the API. All examples contain fictional data.

Choose a project

Demo What to explore
Product catalogue Products, variants, specifications, suppliers and offers
Services and enquiries A service company's website content and customer enquiries
Manufacturer website Brands, product lines, packaging, markets and documents
Employee development Generated screens for people, competencies, plans and learning
Employee development with custom code The same domain with a purpose-built interface and calculations

Get access and sign in

  1. Email support@admingen.dev and name the projects you would like to explore. Support will send the addresses and sign-in details for those demos.
  2. Open a project's link and enter the supplied login and password.
  3. Start with Dashboard. It includes the project description, suggested routes through the demo, API, data model and code structure. The demo itself shows the generator version used.

The .app and .dev addresses with the same number open the same demo and records. Different projects have separate databases and accounts: access to one does not automatically grant access to the others.

What visitors can do

Browse lists and record details, use the available search, filters and sorting, follow related records and inspect populated attachments. The interface is in English; sample content is prepared in Russian and English. Where translations are available, use Content language to switch.

Demos are read-only. Some form controls allow typing so you can explore them, but a demo account cannot save, create or delete records. Closing a form does not turn unsaved input into project data.

Dashboard's API section uses Swagger UI. Explore schemas and permitted GET requests. The model and structure sections show entity relationships and generated/custom boundaries. They help explain the project; they are not a full source checkout.

Concurrent sign-ins

Several browsers can use the same account at once. The current limit is 10 active sessions per account in one project. An eleventh sign-in revokes the oldest session; that browser will need to sign in again when access is checked. Multiple browsers or repeated sign-ins can use more than one session for a single person.

If access stops working or you need additional accounts for a presentation, email support@admingen.dev. Shared passwords are not published in the documentation.