Since church-core handles API configuration and connectivity:
- Remove detailed API setup instructions
- Simplify configuration to focus on display settings only
- Note that API connectivity is managed by church-core
- Emphasize that most configuration is automatic
- Remove redundant environment variable examples
- Fix requirements to not assume file structure
The README now accurately reflects that users don't need to
manually configure API endpoints when using church-core.
- Document church-core as core dependency and architectural foundation
- Add details about shared library benefits (consistency, reliability)
- Update features list to highlight modular components and caching
- Add architecture section explaining church-core integration
- Document key modules and their responsibilities
- Emphasize elimination of code duplication through shared library