Neon Law
  • Services
  • Book Consultation opens in a new tab
  • Sign in

← Contributing to Neon Law Navigator

Improve the Corpus

Chapter 2 of 5 · Section 3 of 11

Sections

1. Intro

  • 1. Five ways to contribute

2. Improve the Corpus

  • 2. Contribute to the product repository
  • 3. View content images locally
  • 4. Publish presentation images
  • 5. Ship through GitOps
  • 6. Work with the store
  • 7. Add a fillable government PDF

3. Share What You Learn

  • 8. Tell us what you learned
  • 9. Join a presentation

4. Put It to Work

  • 10. Use Neon Law Navigator

5. Wrap Up

  • 11. Why this matters

View content images locally

The repository deliberately leaves published blog, presentation, and workshop image bytes out of Git. Before running the site locally, hydrate the images referenced by the content tree from the public asset route:


cargo run -p cli -- ops assets fetch-referenced \
  --base-url https://www.neonlaw.com/assets
cargo run -p neon

This is a read-only HTTP download and needs neither Google Application Default Credentials nor access to the production bucket. The bucket stays private: the running application reads only its marketing assets with its own workload identity and publishes those bytes at /assets/*. Re-run the command when a post gains or changes an image; the files land in the ignored server/public/img/ tree and are served locally from /public.

Presenter notes

Keep the two access boundaries distinct. The production bucket is not public and does not need to become public for a developer to preview the blog: the public asset route reads only the marketing-image lane. fetch-referenced uses that route, so it fetches the same bytes a visitor's browser can reach while keeping documents, exports, and logs out of the path. The downloaded bytes remain local and ignored; they are a development cache, not repository content.

When creating a new slide image, keep the full-resolution PNG or JPEG at server/public/img/<deck-slug>/<filename> for local preview. Upload that same relative key to staging first and then to production; publishing one bucket never publishes the other. Production upload remains an authorized operator action.

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 opens in a new tab
  • Blog opens in a new tab
  • Contact
  • Glossary opens in a new tab
  • Navigator opens in a new tab
  • Notations opens in a new tab
  • Presentations opens in a new tab
  • Privacy opens in a new tab
  • Team opens in a new tab
  • Terms opens in a new tab
  • Testimonials
  • UX opens in a new tab
  • contact@neonlaw.com
  • +1 510 800 2080
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Justice Technology AssociationMission-Aligned Partner 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.

© 2026 Shook Law PLLC

NEON LAW® is a registered trademark of Shook Law PLLC, U.S. Reg. No. 6,325,650 opens in a new tab

Powered by Neon Law Navigator 26.10.4

Everyone deserves to be seen. Made with ❤️ in 🗽.