mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #590] [FEATURE] Logo rotation, daily, from an array to simulate doodles #379
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#379
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Champagnois88 on GitHub (Dec 24, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/590
Description:
Allow users to fill a doodles folder (https://www.google.com/doodles for context) with images that will replace the logo on the landing page as part of some once a day rotation.
Admins could enable this feature, supply it with inputs, and ultimately replace the Whoogle Logo with a daily flash card that promotes learning about a particular subject matter.
@Don-Swanson commented on GitHub (Oct 1, 2025):
Hello @Champagnois88
While I love the concept, we won't be implementing a built-in doodles feature, there are several ways you can achieve daily logo rotation on your Whoogle instance:
Option 1: Custom CSS (No backend access needed)
Use the built-in Custom CSS feature in the Config panel:
Change the URL daily via your own automation, or host different images and use CSS to rotate them.
Option 2: Backend File Automation
If you're self-hosting with Docker, you can directly modify the logo template:
Add to crontab:
0 0 * * * /opt/whoogle-logo-rotation.shOption 3: Volume Mount (Docker)
Mount your own logos and swap them via symlink:
Then rotate the source file daily with your own script.
Reasons for not implementing this:
We recommend implementing whichever method works best for your deployment. Feel free to share your solution in Discussions to help others!