Context
OSS – OopsSec Store currently has no visual identity. The project uses the default Astro favicon on the documentation site, and the main app has no custom icon either. There is no real banner for the README or for social link previews.
As the project grows, having a consistent and recognizable brand helps with discoverability, credibility, and link sharing.
Scope
1. Logo
- A logo that represents the project identity (security, hacking, e-commerce, CTF)
- Should work at small sizes (favicons) and larger sizes (README, docs)
- Provide both SVG and PNG (16x16, 32x32, 180x180, 512x512)
- Should look good on both light and dark backgrounds
2. GitHub social preview banner
- Dimensions: 1280x640px (GitHub recommended)
- Used as the Open Graph image when sharing repository links on social media, Slack, Discord, etc.
- Should include the project name, a short tagline, and the logo
3. README banner
- A wider banner to place at the top of the README (replacing or complementing the current ASCII art)
- Should work well on both GitHub light and dark themes
4. Documentation site banner
- A header or hero image for the Astro docs site
- Should be consistent with the overall branding
5. Favicons
- Replace the default Astro favicon on the docs site (
docs/public/favicon.svg + docs/public/favicon.png)
- Add a favicon to the main Next.js app (
app/layout.tsx currently has no custom icon)
Design direction
The project is an intentionally vulnerable e-commerce app for learning web security. Some themes to consider:
- Security / hacking (locks, shields, terminals, skulls, bugs)
- E-commerce with a twist (a "broken" shopping cart, glitched storefront)
- CTF / gamification (flags, challenges)
The tone should feel technical but approachable: not corporate, not overly edgy. Think developer tool, not enterprise product.
Deliverables
| Asset |
Format |
Destination |
| Logo |
SVG + PNG (multiple sizes) |
README, docs, favicons |
| Social preview |
PNG 1280x640 |
GitHub repo settings |
| README banner |
SVG or PNG |
README.md |
| Docs banner |
SVG or PNG |
docs/ |
| Favicon (docs) |
SVG + PNG |
docs/public/favicon.svg, docs/public/favicon.png |
| Favicon (app) |
ICO or SVG |
app/ |
Notes
- If you want to discuss ideas before starting, feel free to share mockups or sketches in this thread.
- Contributions can be partial — you don't have to deliver everything at once.
Context
OSS – OopsSec Store currently has no visual identity. The project uses the default Astro favicon on the documentation site, and the main app has no custom icon either. There is no real banner for the README or for social link previews.
As the project grows, having a consistent and recognizable brand helps with discoverability, credibility, and link sharing.
Scope
1. Logo
2. GitHub social preview banner
3. README banner
4. Documentation site banner
5. Favicons
docs/public/favicon.svg+docs/public/favicon.png)app/layout.tsxcurrently has no custom icon)Design direction
The project is an intentionally vulnerable e-commerce app for learning web security. Some themes to consider:
The tone should feel technical but approachable: not corporate, not overly edgy. Think developer tool, not enterprise product.
Deliverables
README.mddocs/docs/public/favicon.svg,docs/public/favicon.pngapp/Notes