Conversation
This was referenced Sep 8, 2026
bionicman
force-pushed
the
feat/board-backgrounds
branch
from
September 10, 2026 12:45
cf6fa7b to
d2fb28c
Compare
bionicman
force-pushed
the
feat/board-backgrounds
branch
from
September 15, 2026 16:14
b022bc9 to
8b17459
Compare
Keep calendar view navigation and the board background in the shared board shell.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds optional solid-colour and uploaded-image backgrounds to boards.
I built this for a sizeable Trello migration where board backgrounds are useful
visual landmarks across a large workspace. This follows the direction started
in #513 and extends it with image storage, dashboard and public rendering,
copy/template behaviour, and import support. I would coordinate the final PR
shape with @knom rather than silently replacing that work.
tiles while retaining the current patterned fallback for undecorated boards;
board images;
materialising remote images into Kan-controlled object storage;
board:editpermission and board menu/modal patterns.The schema remains board-owned (
backgroundColourCodeandbackgroundImageKey), and API responses expose a discriminated background valuerather than storage keys or internal IDs. Replacement, removal, failed uploads
and failed copies have explicit object-cleanup paths.
I realise that decoration features have a noticeable effect on the interface
and may deserve a wider product discussion. The integration is deliberately
non-invasive: boards without a selected background retain Kan's current
patterned appearance, while teams moving from Trello can preserve the visual
landmarks they already use. The manual picker stays within Kan's existing
palette. I am open to constructive suggestions on the UX and boundaries.
This PR is intended to be considered together with the card-cover work in #605.
They are separate review units, but solve the same navigation and
personalisation problem on boards and cards respectively.
Screenshots
Board gallery:
Decorated board:
Background settings:
Anonymous public board:
Mobile gallery:
Verification
upstream/mainbootstrap.cjserrors;the branch removes the two board visibility errors present on
upstream/main)Type of change
Checklist
Linked issue
Part of #155