Update README and documentation

[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

#5 Update README and documentation

Goal: Document how to fork and customise the tool for other communities.

Description:
Update project README to include a clear guide for new communities on adding their own branding.

Acceptance criteria:

• Add “How to customise for your community” section.
• Include example config and folder layout.
• Add troubleshooting and best practices for branding.
• Include screenshots or example output if possible.

Dependencies: #1–#4