Web Dev Learners
A learning server for new web developers: beginner forums, a weekly challenge, code review, projects and mentors.
- 8 categories
- 34 channels
- 12 roles
- Medium
Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.
Server structure
Channels
START
- orientation
Where to ask what, how the weekly challenge works, and how to reach a mentor.
- learner-rules
Be kind to beginners, show your code, no homework dumping.
- pick-your-track
Frontend, Backend, Full-Stack or Just Starting, plus Challenge Pings.
- learner-news
Workshops, new mentors and changes to the challenge cycle.
- learner-lounge
Chat that is not a question. Questions have their own forums.
BEGINNER QUESTIONS
- html-and-css-help
One thread per problem. Include the code and a screenshot of what you see.
- javascript-help
Paste the error message exactly. Say what you expected to happen.
- framework-help
Tag the framework. Say which version.
- backend-and-databases
Servers, APIs, queries and auth. Never paste a real secret.
- git-and-deploy-help
It works locally and not in production. Merge conflicts. Lost commits.
- no-dumb-questions5s slowmode
The question you are embarrassed to ask. Everyone here asked it once.
WEEKLY CHALLENGE
- challenge-of-the-week
This week's brief, posted by a mentor on Monday. Mentions Challenge Pings.
- challenge-submissions
One thread per learner per week: the link, what you learned, what you got stuck on.
- challenge-chat
Hints, not solutions, until Friday.
- past-challenges
Every previous brief, for anyone who wants to catch up.
CODE REVIEW
- review-requests
Link the repository, say what you want feedback on, tag your level.
- review-guidelines
How to ask for a review and how to give one that helps.
PROJECTS
- project-ideas
Things to build at each level, and what each one teaches.
- learner-projects
One thread per project. Update it as you go.
- find-a-study-buddy
Say your track, your timezone and what you are working on.
- portfolio-feedback
Portfolios and CVs. Ask for the kind of feedback you want.
MENTORS
- mentor-office-hours
When each mentor is in a Mentor Session room this week.
- ask-a-mentor30s slowmode
Questions about direction, not about a bug. Bugs go in the forums.
- mentor-loungeHidden from @everyone
Mentors only. Who is struggling, who is ready for more.
- mentor-notesHidden from @everyone
One thread per learner a mentor is following closely.
VOICE
- Study Hall
- Pair Programming
- Mentor Session 1
- Mentor Session 2
- Workshop
- AFK
STAFF
- staff-room
Reports, promotions and anything about a member.
- moderation-feedHidden from @everyone
Vetox posts moderation and join logs here.
- Staff Huddle
Roles
- Lead MentorAdministrator
- Community ModeratorModerator
- MentorModerator
- Graduate
- Learner
- Frontend Track
- Backend Track
- Full-Stack Track
- Just Starting
- Challenge Pings
- Muted
Overview
A server for people learning web development from scratch or switching careers into it, run by a few mentors who remember what the first month felt like. Beginner Questions is split so a learner never has to know which framework their bug belongs to: #html-and-css-help, #javascript-help, #framework-help and #backend-and-databases are forums with tags per topic and a Solved tag, #git-and-deploy-help takes the 'it works locally' problems, and #no-dumb-questions is a plain text channel with a five-second slowmode for the questions people are embarrassed to thread. Weekly Challenge is the heartbeat: mentors post the brief in #challenge-of-the-week, learners submit in the #challenge-submissions forum, and #past-challenges keeps the archive. Code Review is its own forum with a Beginner or Intermediate tag so reviewers pick the level they want to teach at, and #review-guidelines explains how to ask for one. Projects holds #learner-projects, #find-a-study-buddy and #portfolio-feedback. Mentors have a hidden #mentor-lounge and #mentor-notes, and voice has a Study Hall, a Pair Programming room, two small Mentor Session rooms and a Workshop stage.
When to use it
A learners' server without structure becomes a stream of 'my code doesn't work' messages that experienced members stop reading, while the beginners who most need a nudge post once and leave. This layout splits questions by topic so each has a small audience of people who know it, gives the week a rhythm with one challenge and one review cycle, and makes mentors reachable through office hours and two dedicated voice rooms instead of DMs.
What makes it different
- Four beginner forums split by topic, so a CSS question and a database question never compete for the same reader.
- #challenge-of-the-week is mentor-only and submissions are a forum, so the brief stays put and entries stay apart.
- Code Review is a forum tagged Beginner or Intermediate, so a reviewer can pick the level they want to teach at.
- #no-dumb-questions is a slow-moded text channel for the questions people are too embarrassed to thread.
- Two Mentor Session voice rooms seat three people, so a walkthrough is not a public performance.
Recommended Vetox setup
Reminders
Schedule a Reminder in #challenge-of-the-week every Monday morning with the new brief, and another on Friday in #challenge-chat for last submissions.
Self-Roles
Post a Self-Roles panel in #pick-your-track for Frontend Track, Backend Track, Full-Stack Track and Just Starting, so mentors can see where a learner is.
Streaks
Enable Streaks so a learner who shows up in #learner-projects or #challenge-submissions each week sees the count, which is what keeps the third month going.
Leveling
Grant Graduate as a Leveling reward around the level a learner reaches after finishing the challenge cycle twice, and let Graduates answer in the beginner forums.
Temp Voice
Point Temp Voice at Study Hall so three learners who want to pair on a challenge get their own room without waiting for the Pair Programming channel.
Questions
Who can post in #challenge-of-the-week?
Mentors and Lead Mentors. The channel is read-only for learners so the current brief is always the top message; discussion goes in #challenge-chat and entries into the #challenge-submissions forum, one thread per learner.
How does someone become a Mentor?
A Lead Mentor grants it. The usual path is Graduate first - a learner who finished the challenge cycle and has been answering in the forums - then Mentor after a few weeks of reviews in #review-requests that other mentors would have given themselves.
Why are the Mentor Session rooms limited to three people?
A walkthrough with an audience turns into a lecture. Three seats means a mentor, the learner and at most one more, which is the size at which people ask the question they actually have.
Common mistakes
- One help channel for everything, where the person who knows CSS grid never sees the grid question under the database ones.
- Letting mentors answer in DMs, which helps one learner once instead of every learner who searches the forum later.
Consider instead
- Programming Community Your members are working developers across many languages rather than beginners on one path.
More in Developers
View allDev Team Internal
FeaturedA private server for one engineering team: async standups, sprint rituals, code review, incidents and deploy feeds.
DevOps and Cloud Engineers
FeaturedDevOps and cloud engineers: provider channels, Kubernetes help, CI/CD, incident war stories and certifications.
Open-Source Project Hub
FeaturedA home for one open-source project: contributor onboarding, issue triage, RFCs, release notes and read-only CI feeds.
Programming Community
FeaturedA public programming server: per-language channels, a tagged help forum, a jobs board and a project showcase.
0.0k
Servers
0+
Commands
0
Users
0
Languages
