Webwide is the inclusive discussion community for web designers, developers & makers.

Whether you're an enthusiast, in training, or a seasoned pro – you'll fit right in at Webwide. Creating an account is fast, easy and completely free so you can start participating right away.

Read our Code of Conduct

Free Membership Benefits

  • Participate in hundreds of interesting discussions
  • Network with industry peers and make new connections
  • Show off your own projects and relevant content
  • Get help and feedback for your coding and designs
  • Buy and sell services and resources in the marketplace
  • Participate in our friendly community challenges
  • Earn trophies and work your way up our leaderboards
  • Enjoy exclusive Webwide member discounts and offers
  • ...and so much more!

open source

  1. eldadfux

    Now Live Appwrite - Open-source Backend Server

    Hi guys! I am super excited to share my first major open source project called Appwrite and I would really appreciate some feedback. 🙏 Appwrite is an open-source platform for developers that abstracts and simplifies common and repeating development tasks behind REST APIs, in order to help...
  2. Adam

    🥶 Is your code future-proof? GitHub is archiving all active public repos to store in the arctic for the next 1,000 years.

    https://archiveprogram.github.com/ The deadline is 02/02/2020 and on that day, GitHub will be archiving all active public repos to store in their arctic vault for at least 1,000 years. I wonder if React will still be cool... (no pun intended 😆). I hope the humans(?) of the year 3000 enjoy the...
  3. VickiLanger

    I'm Gonna be Open w/ You: What I Learned at the All Things Open conference

    Earlier this week, I went to the All Things Open conference in Raleigh, NC. My goal was to meet people and learn new things, but I could never have prepared for the things I learned. As a new person in tech and a first-time conference-goer T-shirts, hoodies, shorts, and other casual clothing...
  4. Gummibeer

    Solved How to structure Stancy documentation?

    Hey all, I need some help how I should structure the Stancy documentation. It's my first fully self written (except contributions) open source package which I also have to write documentation for. I'm really not good in documentation structuring at all. 😓 Is there anyone who has some good tips...