What we are building for MALYOMAR

A clickable prototype of the whole training business: a new public website, one back office built around a central data hub, and portals for learners, instructors, corporate clients and partner organisations.

See every pageOpen the software landscape

MALYOMAR in one paragraph

MALYOMAR Engineering is an engineering training company and an ASME Authorized Training Provider. It teaches piping, pressure equipment and asset integrity, engineering management, value engineering and energy topics to working engineers and to the companies that employ them. Some programs are official ASME courses delivered by ASME-authorized instructors; others are MALYOMAR's own industry programs.

The goal. All systems connect through one centralized hub, so that website, sales, learning delivery, operations, finance and analytics work together while staying flexible for future expansion.

This prototype shows that goal as screens. Nothing here is connected to a database or a payment provider. It exists so the owners can agree on what gets built, in what order, and so developers can see every screen and every record before writing code.

What changed in revision 5 Oct 2026

This revision answers the feedback brief with ten requirements. It adds new modules and workspaces, corrects nine recorded finance inconsistencies and makes the open policy decisions visible. Everything changed is highlighted in pink on the page where it changed; new and updated pages carry a pill in the menu.

Start here for the review

Change log and completion

How to read the highlighting, every page added or changed, the nine finance defects and the flat completion matrix: a verdict, the page and the control to press for each acceptance check, and the remaining gaps.

Open the change log Click through

End-to-end scenarios

Nine walk-throughs that follow one shared record across modules: a tender, a weak batch, a target shortfall, a returning customer, partner delivery, an employee, a purchase and the financial close, as the brief asks, and one added for a website change.

Open the scenarios Not approved

Open decisions

Ten policies the brief leaves open. Until management approves them, everything that depends on one is shown as a provisional assumption and links to its decision.

Open the decisions

The ten requirements

What “demonstrated” means. A reviewer can click through an acceptance check on sample data. Each check has its own verdict in the completion matrix: most are demonstrated, a few only partly, and the matrix says which part is missing. Nothing in this revision is implemented or verified in production: role filtering is static hiding, AI output is pre-written and labelled simulated, what a reviewer changes on a page is not stored, and no accounting, payroll, banking or website system is connected.
Illustrative figures. Targets, plan values, thresholds, percentages and timelines taken from the review are test data. They are labelled where they appear and are not approved company values.

Six ways into the prototype

Each card opens a different view of the same business. Use “Switch view” in the top bar to move between them at any time.

For visitors and buyers

Public website

What an engineer or a training manager sees before they are a customer.

  • Academies and learning paths, not only a course list
  • ASME programs and MALYOMAR programs kept visibly apart
  • Schedule, enrolment, request a proposal, verify a certificate
Open the public website For staff

Back office

One workplace for sales, operations, finance, marketing and support.

    Open the back office     For students

    Learner portal

    Where an enrolled engineer learns, attends and collects certificates.

    • My courses, course player and learning path
    • Live session schedule with join links
    • Certificates, CEUs, orders and invoices
    Open the learner portal     For instructors

    Instructor portal

    Where an instructor prepares, delivers and closes a batch.

    • My sessions and availability
    • Roster, attendance and assessments
    • Course materials and payouts
    Open the instructor portal     For client companies

    Corporate portal

    Where a client's learning and development manager follows their team.

    • Team, seats and cohort progress
    • Programs and new training requests
    • Invoices and purchase orders
    Open the corporate portal     For partner organisations

    Partner portal

    Where an approved partner follows the deliveries it takes part in.

    • Own deliveries and service responsibilities
    • Settlement lines under its own agreement
    • Nothing from other partners; static hiding in the prototype
    Open the partner portal     For owners and developers

    Blueprint

    The explanation behind the screens: you are in it now.

    • Software landscape, journeys, modules and data model
    • Roles, AI layer, build or buy decisions
    • Migration from Tutor LMS and the phased roadmap
    • Change log, scenarios and open decisions
    Continue with the software landscape

    The problem with today's site

    AreaToday: WordPress with Tutor LMSTarget: what this prototype shows
    PositioningA course shop: Home, Courses, Instructors, Events. Courses sit in WordPress categories.An engineering learning platform organised by academies and learning paths.
    Authorship“Course Author-ASME” and “Course Author-MALYOMAR” are listed in the instructor directory next to real people.Three separate things: provider (ASME or MALYOMAR) on the course, and human experts in their own directory.
    Catalog dataCourses with no price, no hours or no lessons; drafts and test items mixed with live courses; two prices that look like another currency.One course record with required fields, a status workflow and a migration checklist.
    SalesA cart for single seats. Corporate enquiries arrive by email and phone and are not tracked.Leads, pipeline, proposals and private batches for companies.
    OperationsNo batches, seats, waitlists, attendance or instructor availability in the system.Batches, attendance, instructor availability, certificates.
    FinanceOrders live in the shop plugin; invoices, bank transfers and instructor payouts are handled outside it.Invoices, payments, reconciliation and payouts from the same records.
    NumbersCounters on the About page show zero or defaults; other pages show different counts.Dashboards read from the hub, so one number has one source.
    Observations come from the live site and from the Tutor LMS export of February 2026. Details are on the migration page.

    Three delivery modes

    On-demand courses

    Self-paced online learning: lessons, quizzes and progress tracking in the course player.

    Virtual classroom

    Live, instructor-led training delivered online, with attendance and recordings.

    In-person training

    Face-to-face training at a public venue or at the client's site, including private corporate cohorts.

    Every course can be offered in one or more modes. A dated run of a course in one mode is a batch.

    Open decision. The landscape drawing keeps WordPress as the public front end. Whether it stays or is replaced is one of the choices listed on build, buy or mix.

    How to read the prototype

    Real content

    From MALYOMAR

    Courses, their topics, outcomes, hours and prices come from the Tutor LMS export. Academies group those courses. Instructors are the people listed on the live site.

    Line tags carry course codes. An amber band is an ASME authorized program, a teal band is a MALYOMAR program.

    Sample data

    Invented

    Leads, deals, orders, invoices, learners, staff names, batches, dates and amounts are invented so that screens tell one consistent story.

    Client companies are always named “Sample …”. No client, logo, statistic, award or testimonial in the prototype should be read as a claim about MALYOMAR.

    Amounts are shown in EGP as a working assumption. The export holds bare numbers; currency is an open decision.

    What works, what does not

    Static

    Navigation, tabs, filters, drawers and modals work. Buttons that would change data show a short confirmation instead.

    On the revised pages, selectors and forms recompute the figures on the page, and “View as” narrows the back-office menu to one employee’s roles. Neither is stored, and hiding a menu is not authorization.

    Violet chips and notes mark places where the AI layer assists. The text in them is written by hand to show the intent, and is labelled “Simulated AI output”.

    Every screen is built from one stylesheet. The styleguide shows each component.

    Reading order for the blueprint

    1. Change logWhat this revision changed and how complete it is
    2. ScenariosThe eight end-to-end walk-throughs of the brief and one for the website
    3. Open decisionsTen policies awaiting approval
    4. Software landscapeThe hub and the capability groups around it
    5. JourneysHow a customer and a staff member move through it
    6. Modules and screensWhat each module owns
    7. Data modelThe records and who owns them
    8. Roles and accessWho sees and approves what
    9. Build, buy or mixDecisions the owners must make
    10. MigrationGetting out of Tutor LMS
    11. RoadmapPhases and what done means