feat: add custom logo and favicon for writers pub branding

[pracheyyy]

Description

This PR introduces a new logo and favicon for Writers Pub to improve branding, visual identity, and recognition across the platform.

Changes Made

• Added a custom logo aligned with the Writers Pub theme
• Added favicon for browser tabs and bookmarks
• Updated logo references across the application
• Improved overall branding consistency
• Ensured compatibility with both desktop and mobile views

Why

The previous branding lacked a distinct visual identity. The new logo and favicon help:

• Improve brand recognition
• Create a more professional appearance
• Enhance user trust and credibility
• Provide a consistent visual experience across the website

Testing

• Verified logo displays correctly across pages
• Verified favicon appears in browser tab
• Tested locally using the development server
• Confirmed responsive behavior on different screen sizes

Type of Change

• New feature (non-breaking change which adds functionality)

Fixes #62

logo:

(dark)

(light)

(favicon)

[vercel]

@pracheyyy is attempting to deploy a commit to the areeb-coder's projects Team on Vercel.

A member of the Team first needs to authorize it.

[pracheyyy]

@Areeb-coder
please review the PR.
thsnk you!

[pracheyyy]

@Areeb-coder
/please review the PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
writters-pub	Ready	Preview, Comment	Jun 4, 2026 5:49am

[pracheyyy]

@Areeb-coder
thank you for merging my PR

/please would you add label of gessoc , because then and only then it will consider under gessoc

[pracheyyy]

@Areeb-coder
would you please add relvent lables and merge and close this issue.
because then and only then it will consider as my contribution under gssoc.
thank you!

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
33155964	Triggered	Google API Key	98a74a5	writers-pub.env	View secret
33155965	Triggered	PostgreSQL Credentials	98a74a5	writers-pub.env	View secret
33155966	Triggered	MongoDB Credentials	98a74a5	writers-pub.env	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}