Public-safe ecosystem overview

Project Status

Last updated: 8 June 2026

This page keeps a calm, public-safe overview of the BremondWalks ecosystem. It documents structure, routines and future direction without exposing private secrets, passwords, API keys, tokens or Discord webhook URLs.

Current Ecosystem

Main Website

bremondwalks.com is the public brand hub. It should stay cinematic, mobile-friendly and focused on real places, real sounds and real atmosphere.

• Explain the BremondWalks project clearly.
• Link to YouTube, the app, Discord, Ko-fi and the future shop.
• Stay SEO-friendly and fast.

App Portal

app.bremondwalks.com is the living archive and creator workspace.

• Walking tour archive and upcoming route planning.
• Creator tools for thumbnails, shorts and outros.
• Filming tips and atmosphere tags.
• Discord channels, scheduled posts and YouTube update workflow.
• Backup / export for project data.

Docs Portal

docs.bremondwalks.com is the public-readable documentation archive. It should document process and structure, not secrets.

Discord

Discord is the community layer for BremondWalks. It supports updates, route suggestions, travel discussion, camera gear and editing topics.

GitHub and Lovable

Lovable is the main app-building environment. GitHub is used as source backup and technical history.

• Keep secrets out of GitHub.
• Keep .env ignored.
• Use .env.example only for placeholders.
• Private runtime secrets must stay in Lovable Cloud Secrets.

Maintenance Routine

The weekly project monitor should stay short and action-focused. It should check:

• bremondwalks.com, app.bremondwalks.com and docs.bremondwalks.com.
• /links and admin /settings.
• SSL certificates and domain health.
• sitemap and robots files where relevant.
• Lovable to GitHub sync.
• Recent backup status.
• Discord scheduled post cron.
• No public webhook URLs or secrets exposed.
• PWA/cache behavior after deployment.

Recent Stability Notes

• Discord channel list handles inactive channels.
• Scheduled Discord posts support images.
• YouTube Discord notifications are deduplicated.
• Backup / export panel exists.
• Service worker cache was bumped after runtime recovery.
• Public Supabase runtime fallback was added so the app can start when runtime env injection is incomplete.

Future Shop Direction

The current shop should stay simple until products are real. Ko-fi is enough for light support now. Shopify becomes relevant later when product photos, prices, shipping and order handling are ready.

• Possible products: stickers, tote bags, mugs, T-shirts, hoodies, caps and QR cards.
• The shop should feel calm, premium and optional.
• Products should connect to real walking tours, travel atmosphere and the BremondWalks identity.

Operating Principles

• Fix bugs before adding new features.
• Keep admin tools invisible to visitors.
• Keep public pages fast and mobile-friendly.
• Avoid feature bloat.
• Prefer practical workflow improvements.
• Never document secrets publicly.

Real places. Real atmosphere.