page:blueprints:real estate brokerages:public directory:next js

Real Estate Brokerages: Public Directory Using Next.js

Summary

A public directory blueprint for real estate brokerages built with Next.js on Ample. Domain schema:

Public information: published listings with media, agent and agency profiles, buying and selling guides. Kept out of scope until handling is reviewed: vendor and buyer identity, offers and negotiations, unpublished listings. Only listings with publishing_status = published appear publicly; offers and identities are out of scope.

Technical basis verified on Next.js: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

Representative Queries

Workflow Steps

  1. Model the real estate brokerages domain: Create the tables listings, agencies, listing_media, reports, state_transitions. Keep sensitive classes (vendor and buyer identity, offers and negotiations, unpublished listings) out of this schema.
  2. Workflow step 1: Model listings with a publishing_status state machine scoped to the agency.
  3. Workflow step 2: Serve only published listings, with media from the CDN bucket.
  4. Workflow step 3: Enforce the agency scope on every query.
  5. Workflow step 4: Deploy and verify a published listing and that unpublished listings are absent.
  6. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
    ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
    
  7. Verify: Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the real estate brokerages workflow.
    ample logs  --kind build
    

Cost Estimate

Limitations

Example

Success Checks

  1. App responds on its public URL
    • Path: /
    • Expect: ample canary next js patterns
  2. Relational-records self-test from the example
    • Path: /p/relational-records
    • Expect: see the pattern fixture checks.

Next Actions

Evidence Summary