Build with Local Media Desk

A guided path from your first checkout to understanding, extending, and testing the platform.

Understand the system.
Make your first change.

Start with a working local environment, follow a real request through the platform, and use the implementation reference as you build.

Your reading path01 · Set up your workspace02 · Learn the architecture03 · Trace a product workflow04 · Test and contribute

Access for collaborators

The developer handbook and technical references require a Local Media Desk identity with documentation access. Workspace administrators and owners have documentation reader access automatically when they sign in. Outside collaborators who are not administrators can ask a platform administrator for the documentation-only platform.docs.read grant. Reading developer documentation does not require access to customer workspaces or permission to administer the platform. Repository access is separate: your administrator must also arrange GitHub access if you will contribute code or follow source links.

Sign in to the developer handbook. If you can sign in but cannot open it, ask your administrator to check your active administrator membership or documentation grant. How access works.

Learn, then look up

Developer handbook

Setup, architecture, data model, implementation walkthroughs, and contribution patterns. Sign-in required.

Engineering evidence

Authority, isolation, tests, release controls and exact implementation sources. Sign-in required.

Guided practice

Role-based labs with local fixtures, expected receipts, denied paths and answer keys. Sign-in required.

Implementation reference

Source-derived route, database, worker, permission, and package inventories. Sign-in required.

Operate the platform

Health checks, incidents, recovery, releases, and evidence. Additional operational access required.

Using the HubSpot app

Public installation and support guidance for the connected app.

What to expect

Guides explain how the pieces fit together. Generated references describe the checked-in implementation and link back to its source. Operational pages identify what has been verified and what still needs a real environment check. A route's presence in the reference does not make it a public or supported integration API.

Use search to find an interface or workflow. Copy Markdown from a page when you need it in your editor; exports and search follow the same access rules as the page. Private pages require your session and cannot be fetched by an external assistant merely by sharing their URL.