Neon LawCall +1 510 800 2090
  • Navigator
  • Notations
  • Legal Aid
  • Sign in

← Using Neon Law Navigator

Develop locally

Chapter 2 of 6 · Section 3 of 24

Sections

1. Why do this

  • 1. Learning objectives
  • 2. The running matter

2. Develop locally

  • 3. Start the local room
  • 4. Sign in

3. Work the litigation matter

  • 5. The four nouns in one workflow
  • 6. One onboarding, one offboarding
  • 7. Walk the retainer intake one question at a time
  • 8. The other notations on a matter
  • 9. Inspect the matter page and its Matter Pages
  • 10. Make a sample-project change

4. Use the Project's forge

  • 11. Git is track changes for the whole folder
  • 12. Optional: work the folder with jj
  • 13. Sign in, then receive repository access
  • 14. Send a change through the same gate
  • 15. Follow the gate and its status

5. Open a real Project

  • 16. Fill the matter-open form
  • 17. Provision the repository and Drive folder — a separate step today
  • 18. Populate the repository
  • 19. Stage a document and sync it
  • 20. Work in a Project with Jujutsu
  • 21. Pull a fresh checkout's documents
  • 22. Matter Pages are a separate, later decision
  • 23. Verify

6. Wrap Up

  • 24. Verify the room

Start the local room

The same local web process resolves its public face from the host. In staging, use staging.neonlaw.com for Neon Law, staging.deleteyourdata.com for DeleteYourData.com, and staging.guiebshook.com for Guieb & Shook. The route and application stay shared; the host selects the brand's copy, mark, font, and colour layer.

The Navigator CLI owns the complete local lifecycle. From a New Worktree, run:


cargo run -p hudson -- dev worktree-env up --path "$PWD"
set -a; source .devx/env; set +a
cargo run -p neon

The boot command provisions the KIND dependency tier, applies the schema, seeds the sample matters, clones each sample project, stages its navigator.yaml, drafts/, and commit, and writes the generated environment. The host web process reads that environment on startup, so each matter's declared pages render on its show page after each boot.

The explicit refresh command uses the same clone and staging path when a sample project changes. Naming one matter refreshes only that matter, which is the fast loop while iterating on a single repository:


cargo run -p hudson -- dev sample-project --project sample-litigation

Restart web after refreshing so it reads the new staged source. The generated .devx/env contains NAVIGATOR_SAMPLE_PROJECTS_DIR, the directory every matter's source is staged under; source it before starting the host process.

Presenter notes

Run the boot commands before proceeding. Confirm that .devx/env names the staged sample-projects directory.

View all slidesOpen display
← PreviousNext →
Neon Law
  • X opens in a new tab
  • LinkedIn opens in a new tab
  • YouTube opens in a new tab
  • API
  • Blog
  • Contact
  • Design
  • Glossary
  • Navigator
  • Notations
  • Presentations
  • Privacy
  • Team opens in a new tab
  • Terms
  • Testimonials
  • contact@neonlaw.com
  • +1 510 800 2090
  • California
    1515 20th StreetBakersfield, CA 93301
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    1111 Main StSTE 201EVancouver, WA 98660
  • Justice Technology AssociationMission-Aligned Partner opens in a new tab
  • Proud member of Greater Vancouver ChamberGVC opens in a new tab

Attorney advertisement. Nothing here is legal advice without a signed retainer for an active project. Past results do not guarantee future outcomes.

Everyone deserves access to justice.Made with ❤️ in 🗽.

© 2026 Guieb & Shook PC

Powered by neon-law/navigator opens in a new tab26.11.17-rc.1GitHub stars 5