Point Lookout Fishing Club Community Platform

Project links and history

• First substantive build: 3 May 2026.
• GitHub repository: plfc-community-platform.
• Public site: visit the public site.

Related public projects

Each link below reflects an evidenced family, lineage or direct connection. This project has 6 relevant public connections.

Point Lookout Fishing Club digital builds

• plfc-ai-agent-md-forms - public page - earlier build; plfc-ai-agent-md-forms is later, explicit cross-reference, ordered build lineage, shared named build family.
• PLFC_01 - public page - later build; PLFC_01 is earlier, explicit cross-reference, ordered build lineage, shared named build family.
• PLFC_02 - public page - later build; PLFC_02 is earlier, explicit cross-reference, ordered build lineage, shared named build family.
• PLFC_2026_Data - public page - later build; PLFC_2026_Data is earlier, explicit cross-reference, ordered build lineage, shared named build family.
• PLFC_Live - public page - later build; PLFC_Live is earlier, explicit cross-reference, ordered build lineage, shared named build family.
• PLFC_web_2026 - public page - later build; PLFC_web_2026 is earlier, explicit cross-reference, ordered build lineage, shared named build family.

Exploratory open-source static website prototype for the Point Lookout Fishing Club.

The goal is to give the secretary and committee a working interface they can inspect, discuss and improve before replacing or extending the current public site.

What This Prototype Covers

• Public dashboard for the club story and next-step readiness.
• Stripe-ready commerce structure for memberships, casual competition fees, fundraisers and merchandise.
• Membership lifecycle flow based on the supplied flow chart.
• Committee meeting flow based on the supplied meeting chart.
• AGM roadmap page using the supplied roadmap visual.
• Field Ops visualisations for solunar/tide planning, tide shape, weather gauges, touchable Moreton Bay map zones, media queues and future digital-twin layers.
• Google Drive, Sheets and Gmail data hub concept for stakeholder routing.
• Public-safe club journey intelligence distilled from the supplied wrap-up workbook.
• Google Calendar event-type queue concept for approved competitions, meetings, working bees, renewals, media and sponsor deadlines.
• Honour board TV concept for wall-art installations, kiosks and public venue displays.
• Product data scaffold in data/stripe-products.json.

Pages

• index.html - public dashboard and prototype overview.
• commerce.html - Stripe-ready memberships, competition fees, fundraisers and merchandise.
• processes.html - membership and committee meeting process flows.
• field-ops.html - visual field-ops board for latest tide, solunar, weather, GPS, upload and digital-twin snapshots.
• data-hub.html - Google Drive / Sheets / Gmail data architecture for stakeholder routing.
• honour-board.html - web-app driven TV honour board concept for public-safe club storytelling.
• roadmap.html - AGM roadmap and next actions.
• docs/stripe-commerce-plan.md - plain-English Stripe setup plan.
• docs/field-data-contract.md - JSON handoff contract for a future agent stream or cron job.
• docs/example-data-sets.md - plain-English notes for the example JSON datasets.
• docs/honour-board-data-model.md - public display rules and source-system notes for the honour board.
• data/latest-field-data.json - sample field snapshot used by the Field Ops page.
• data/example-public-map-points.json - small public map point dataset based on the KMZ pattern.
• data/example-field-story-export.json - sample after-event story/simulator export.
• data/example-honour-board-tv.json - sample wall-display payload for the honour board page.
• assets/maps/plfc-point-lookout-fishing-club.kmz - supplied PLFC KMZ source for importing into Google My Maps / Drive.
• data/club-journey.json - public-safe summary layer from the wrap-up workbook.
• data/calendar-event-types.json - prototype Calendar queue rules, not live calendar data.
• templates/PLFC Backend Starter Workbook.xlsx - starter workbook for importing into Google Sheets.
• templates/PLFC Backend Governance Starter Pack.docx - starter governance pack for committee review.

Sources Used

• Current public site: https://pointlookoutfishingclub.com
• Current AGM dashboard: https://auraofintelligence.github.io/PLFC_2026_Data/
• Current shop products discovered from the public shop page:
  • 1-Comp Casual Membership - $25
  • Adult Annual Membership - $75
  • Annual Social Membership - $20
  • Cadet Annual Membership - $50
  • Junior Annual Membership - $30
  • Legendary Lifetime Member - $1,000 and $5,000
• Local supplied files:
  • PLFC Meetings Flow Chart.png
  • PLFC Members Flow Chart.png
  • PLFC AGM Roadmap.png
  • PLFC Wrap-up (1).xlsx
  • plfc comp1 photo.jpg
  • plfc comp1 wrapup.jpg
  • plfc honour board example.png
• Stripe guidance:
  • Payment Links for simple one-time products.
  • Checkout Sessions for web app checkout.
  • Billing only for approved recurring renewals.
  • API version verified as 2026-02-25.clover on Stripe documentation.

Field Ops Data Layer

field-ops.html does not fetch live tide, weather or GPS data itself.

It reads a simple JSON snapshot from:

data/latest-field-data.json

That file can later be updated by a separate agent stream, cron job or backend. Keep precise GPS, private member data, emergency contacts and private media URLs out of any public JSON file.

The map section uses public placemarks extracted from the supplied KMZ and opens each selected point in a Google Maps embed. The editable master map should live in the club Google Drive / My Maps account; this repo keeps a static KMZ copy and public-safe JSON fields for the website.

Google Drive Data Layer

The prototype assumes the club Google account can become the private operations vault.

Do not hard-code the club email address into public repo files unless the committee explicitly approves it.

Suggested private storage pattern:

• Drive folders for raw files, uploads, minutes, finance exports and media.
• Sheets for member ledgers, competition records, permissions, payments and action registers.
• Gmail labels for inbound requests and outbound confirmation trails.
• Calendar queues for approved meetings, competitions, working bees, renewals, content deadlines and sponsor/grant deadlines.
• Public-safe JSON exports for the GitHub Pages website.

Running Locally

This is a static site. You can open index.html directly in a browser.

For the Field Ops JSON loading, use the local server option below.

For a local server:

python -m http.server 4173

Then open:

http://localhost:4173

Open-Source Boundary

The code is prepared under the MIT License.

Club name, club material, photos, flow charts, AGM material and any future official copy should be treated as Point Lookout Fishing Club material unless the committee approves a separate content licence.

Before Public Launch

• Confirm every fee and product description with the committee.
• Decide which payments are allowed to go live first.
• Confirm Stripe account ownership and bank settlement details.
• Add privacy wording for member data, newsletter consent and SMS consent.
• Decide which uploaded documents can be public.
• Replace prototype wording with approved club wording.
• Decide whether this prototype replaces, links from or sits beside the current WordPress site.