Add community configuration system

[victoria-lo]

We’d like to make this tool more community-agnostic and easily reusable by other tech groups (for example: open source meetups, developer community organisations, hackathon groups, etc). Right now it is branded and structured around ragTechDev, but with a few adjustments it could serve a wider audience.

Goals:

• Allow other tech communities to add their own brand (names, logos, colours) without needing deep code changes.
• Provide a clear onboarding path for new communities to fork/customise the project.
• Make configuration of templates (templates for social posts, event banners, etc) more flexible so communities can adapt text/layout/logo easily.
• Keep the core functionality (canvas export, platform sizes, etc) intact, but separate “branding assets” from core logic.

Sub-issues:

We’d like to make this tool more community-agnostic and easily reusable by other tech groups (for example: open source meetups, developer community organisations, hackathon groups, etc). Right now it is branded and structured around ragTechDev, but with a few adjustments it could serve a wider audience.

Goals:

• Allow other tech communities to add their own brand (names, logos, colours) without needing deep code changes.
• Provide a clear onboarding path for new communities to fork/customise the project.
• Make configuration of templates (templates for social posts, event banners, etc) more flexible so communities can adapt text/layout/logo easily.
• Keep the core functionality (canvas export, platform sizes, etc) intact, but separate “branding assets” from core logic.

Sub-issues:

• Add community configuration system #1
• Refactor template components to use config #2
• Add multi-community theme folder structure #3
• Add theme selector #4
• Update README and documentation #5
• Add example community preset #6
• Add automated test coverage #7

#1 Add community configuration system

Goal: Introduce a structured configuration file for community branding settings.

Description:
Create a community.config.json (or .yaml) file that defines community name, logos, colors, fonts, and social links.
The app should load and validate this file at runtime, making values accessible across templates through a helper (e.g. getBrandConfig()).

Acceptance criteria:

• Config file supports: name, logo URLs, colors, fonts, and social handles.
• App loads and validates config successfully.
• A single utility function provides config values to templates.
• Default values fallback to ragTechDev branding if no config provided.

Dependencies: None