Skip to content

SUPPORT.md

Latest commit

 

History

History
88 lines (61 loc) · 3.44 KB

SUPPORT.md

File metadata and controls

88 lines (61 loc) · 3.44 KB
Raw

💬 Support

Welcome to the support guide for the Deep Dey Portfolio & System Architecture project. Use the appropriate channel below depending on the nature of your request.

🧭 Support Matrix

Request Type Recommended Channel
Bug report (UI, routing, data) GitHub Issue — Bug Report
Feature suggestion GitHub Issue — Feature Request
Documentation improvement GitHub Issue — Documentation
Security vulnerability Private email only (see SECURITY.md)
General / technical outreach team.deepdey@gmail.com
Platform bugs (API, CDN, QuickLink) a@qlynk.me
Photography / creative outreach thedeeparise@gmail.com
Ticketed web contact deepdey.vercel.app/contact

🐛 Before Opening a Bug Report

Please check the following before submitting a new issue:

  1. Confirm it's reproducible — try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) and an incognito window.
  2. Check existing issues — search open issues to avoid duplicates.
  3. Check the latest branch — your issue may already be fixed in a recent commit.

Required in your report:

  • Steps to reproduce (numbered, exact)
  • Expected behavior
  • Actual behavior
  • Browser, OS, and device type
  • Screenshots or screen recording if the issue is visual

💡 Before Opening a Feature Request

Feature requests are welcome but given the current academic hiatus, review may be delayed. Before submitting:

  1. Check if it already exists — browse the site at deepdey.vercel.app and search existing issues.
  2. Describe the value clearly — what problem does this solve and for whom?
  3. Keep scope small — incremental improvements are easier to review than complete redesigns.

🔒 Security Issues

Never open a public issue for a security vulnerability.

Follow the private reporting process documented in SECURITY.md:

🆔 Identity Verification for Support

For account-specific support, you may be asked to share your private 16-digit service key from your logged-in profile.
This helps verify ownership without exposing public profile data.

⏱️ Response Times

Academic Hiatus Active — due to JEE Advanced 2027 preparation, non-critical responses may be slower than usual. Security reports are always prioritized.

Request Type Typical Response
Critical security report ≤ 48 hours
Bug report (production-breaking) ≤ 7 days
Bug report (visual/minor) Next maintenance window
Feature request Post-examination (2027+)
General outreach 3–7 days

📚 Helpful Links