Currently users need to manually replace the background PNG files (north.png, south.png, east.png, west.png) to customize the view for their location.
Ideas to explore:
Add a configuration option to specify a backgrounds folder/theme
Create a web UI for uploading custom backgrounds
Provide pre-built background packs for common locations (desert, mountains, coastal, urban, etc.)
Generate backgrounds dynamically based on location coordinates
Add documentation for creating custom backgrounds with the correct dimensions (1536x1024)
Current behavior:
Backgrounds are hardcoded PNGs in the root directory that users must replace manually.
Currently users need to manually replace the background PNG files (north.png, south.png, east.png, west.png) to customize the view for their location.
## Ideas to explore:
- Add a configuration option to specify a backgrounds folder/theme
- Create a web UI for uploading custom backgrounds
- Provide pre-built background packs for common locations (desert, mountains, coastal, urban, etc.)
- Generate backgrounds dynamically based on location coordinates
- Add documentation for creating custom backgrounds with the correct dimensions (1536x1024)
## Current behavior:
Backgrounds are hardcoded PNGs in the root directory that users must replace manually.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently users need to manually replace the background PNG files (north.png, south.png, east.png, west.png) to customize the view for their location.
Ideas to explore:
Current behavior:
Backgrounds are hardcoded PNGs in the root directory that users must replace manually.