Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🐛 Bug Report: Old logo of Appwrite in favicon

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
design, frontend

Research direction

Start at https://builtwith.appwrite.io/ and inspect how the site references its favicon and available branding assets at https://appwrite.io/assets. Done means the deployed site shows the current Appwrite favicon in browser tabs, bookmarks, and history.

Written by the indexing model from the issue text.

Description

bug
👟 Reproduction steps

Issue Description:

Currently, the website https://builtwith.appwrite.io/ is still utilizing the old favicon of Appwrite. We should update this to reflect the new favicon for consistency and branding purposes.

Steps to Reproduce:

  1. Visit https://builtwith.appwrite.io/.
  2. Observe the favicon in the browser tab, bookmarks, or browser history.

Proposed Solution:

Update the favicon on https://builtwith.appwrite.io/ to the latest version that aligns with the current Appwrite branding guidelines.

Additional Information:

  • The new favicon assets are available here.

Labels:

design
branding
enhancement

👍 Expected behavior

The favicon for the website should be the latest and correct one, consistent with the Appwrite branding.

👎 Actual Behavior

The website is still using the old Appwrite favicon.

🎲 Appwrite version

Appwrite Cloud

💻 Operating system

Windows

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?
  • I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
Dominant language
TypeScript
Stars
45
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from appwrite/builtwith

All issues in appwrite/builtwith

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.