Neon Law
  • Fractional CTO
  • Litigation
  • Fractional GC
  • Legal Services
  • 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. Ship through GitOps
  • 5. Work with the store
  • 6. Add a fillable government PDF

3. Share What You Learn

  • 7. Tell us what you learned
  • 8. Join a show-and-tell
  • 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
BlogContactFoundationNavigatorPresentationsWorkshops
Contact us — 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
  • Washington
    720 Seneca StSte 107-715Seattle, WA 98101

© 2026 Shook Law PLLC and Neon Law Foundation

This is attorney advertisement. Nothing on this site is legal advice. Neon Law is the trade name of Shook Law PLLC, and an attorney-client relationship begins only with a signed retainer between you and Shook Law PLLC. Published flat fees cover the scope each one names and do not include third-party filing fees. Every legal matter is different, and past results do not guarantee a similar result.

Shook Law PLLC is a proud supporter of the Neon Law Foundation , a 501(c)(3) nonprofit.

Neon Law Foundation is a Nevada nonprofit corporation and a 501(c)(3) tax-exempt organization. It does not practice law and cannot represent you.

Nothing on this site is legal advice, and nothing here creates an attorney-client relationship.

5150 Mae Anne Ave Ste 405-9999, Reno, NV 89523
support@neonlaw.orgTransparency & public disclosures

Powered by Neon Law Navigator #26.8.20-hotfix.4

Open source — neon-law-foundation/navigator GitHub stars 2