hpmArchitect

New developers open the blank Developer Identity slide in to fill in their Master Manifest registry details. As soon as the new identity is saved you become an existing developer, and your Workbench consists of an Add Package card.

The entries save locally, so you can revisit edits in a session, before syncing to the server as you end a session. Your Workbench will show an amber Draft indicator on your Pacakge card, as well as the global Workbench Synced button when you are ready to save your session.

Existing Developers, using your HPM Master Manifest name, skip straight to the Existing Developer experience. The grid opens with a Developer Identity tile along the top, and the same Add Package card lives alongside the package tiles whether the workbench is empty or full.

Clicking the identity tile slides the Developer Identity card back into focus. Any edit flips the Save button to amber, letting you know a draft exists locally, until you hit the Workbench Synced button.

The identity metadata is the head of the Intermediate Manifest, so keep the details tidy before exporting.

The grid represents one card per Package plus the omnipresent Add Package card. Clicking any card/tile opens the Edit Package slide in and changing any field immediately turns the Save control amber.

The Draft indicator stays amber until you press the Workbench Synced button in the upper-right. The View Raw Json button to the left exposes the manifest-ready payload for deployment.

Use the Edit Package slide on any package or the Add Package card. Each change flips the local Save amber so you can work on multiple packages before syncing.

The Workbench keeps track of drafts and the Workbench Synced button stays amber until everything is pushed, while the View Raw Json button remains the authoritative export point.

Each card can reveal its individual HPM JSON, and the Workbench always keeps a View Raw Json button next to the Workbench Synced button so the latest draft can be copied to your Master / Intermediate manifests.

Each package card also hosts a button to reveal its specific HPM JSON, and the metadata panel highlights package types and tags for easy reference before pushing to GitHub.

The View Raw Json button is the heart and the goal of hpmArchitect. It combines your Developer Identity, your Intermediate Manifest (typically repository.json), and one block/parcel of Json for every Package on the workbench, ready for you to paste each block into your designated repository.