Issues — Feedback

Found a bug? Spotted an inaccuracy in a talk? Promised materials never showed up? Here's how to report it — clearly and quickly.

Which channel to use

Type of issue	Where to go
Bug on itfriday.community	GitHub Issues ↗
Inaccuracy in a talk / wrong fact	GitHub Issues ↗
Missing materials (slides, links)	GitHub Issues ↗ or Telegram ↗
Idea for a stream or improvement	GitHub Issues ↗ or Telegram ↗

How to open a GitHub issue — step by step

No GitHub account?

Registration is free: github.com/signup. Just an email is enough.

1. Open the issues list

Go to: github.com/leva13007/itfriday.community/issues

2. Check if a similar issue already exists

Before creating a new one — search to see if someone already reported the same thing. Use the search bar with Filters.

3. Click «New issue»

Green button in the top right corner.

4. Choose a type

GitHub will show four templates — pick the one that fits:

• 🐛 Bug on the site — something is broken or looks wrong
• 📋 Inaccuracy in a talk — wrong or outdated information in a stream
• 📦 Missing materials — slides, links, demos that were promised but never posted
• 💡 Suggestion — idea for a topic, format, or improvement

5. Fill in the form

Each template has hints as <!-- ... --> comments — they don't appear in the published issue, only while editing.

Required:

• A meaningful title — not «Doesn't work» but «Speakers page crashes on iOS Safari»
• A specific description — who, what, where, when

Optional but helpful:

• Screenshot (just drag the file into the text field)
• Link to a specific page or video timecode

6. Click «Submit new issue»

Done. The issue is submitted, we'll get a notification and respond.

How to write a good issue

Title: short and specific — someone should understand what's wrong without opening the details.

❌  Page broken
✅  /streams/ returns 404 in Firefox 126

❌  Error in stream
✅  Stream #002 ~14:30 — display:none doesn't remove element from accessibility tree (incorrect claim)

❌  I want a topic
✅  Suggestion: stream about React Server Components and Next.js App Router

Description: answer «what», «where», «when», «how to reproduce». Avoid vague phrasing.

Screenshot: if you're reporting a bug — a screenshot speeds up the fix in 90% of cases.

What happens after you open an issue

1. The issue appears in the public list on GitHub
2. We get a notification
3. If we need clarification — we'll reply directly in the issue (you'll get an email)
4. After the fix or response — the issue is closed with a comment

We usually respond within a few days.

What not to do

• Don't duplicate an issue if a similar one already exists — add a comment there instead
• Don't write personal messages or off-topic questions in issues — use Telegram for that
• Don't open an empty issue without a description