We're accepting story submissions 📝

We'd love to publish your work on the Byteconf blog! We're always seeking out new stories about things that you're learning, new frameworks, development methodologies, or whatever else you think our audience would enjoy.

We try to publish at least once a day. That means that if you submit a draft and we accept it, it often gets published within the next week. We're pretty quick!

We also don't hold any copyright or make you sign away any of your work. Byteconf is built on the back of open-source: we have that same ethos when it comes to writing. Link to your own site, or your Twitter, or whatever seems right for the story–we're happy to work with you and keep your writing, your voice, and your content as you'd like it to look!

We don't have a ton of requirements, or "rules" around publishing, but here's what we ask our contributors to think about before submitting a draft:

If your piece has been previously published with another publication, please confirm that you're allowed to post on other publications. If you published on your own website, blog, or Medium account, you're welcome to link back to your own work.

We're OK with profanity, humor, etc – that being said, we won't publish things that are discriminatory, or are unnecessarily rude against other people, programming languages, or communities. It should be pretty common sense - that being said, you may want to double-check out our Code of Conduct on GitHub.

If you have an idea for a draft, reach out to us at blog AT bytesized DOT xyz. We'll add you as a contributor to our blogging platform (you're looking at it!) and then you'll be able to submit a draft.

Once you've submitted a draft, shoot us another email (or reach out on Twitter to @byteconf or to me personally) and we'll get your draft reviewed ASAP. Once it's ready for publication, we'll let you know when we're planning on publishing.

Sharing the post in any additional places that we think it would be a good fit, such as Hacker News, or a subreddit for a particular language (like /r/reactjs)

The details around how to post will probably update frequently, but instead of getting bogged down in the details, you should just submit a post! We'd love to learn from you alongside the rest of our community. If you have any questions, reach out on Twitter to @byteconf or to me personally via DMs, or via email: blog AT bytesized DOT xyz.