Prepare and store the EthBuilders Newsletter
❤️ By the community, for the community ❤️

👷 👷‍♀️ 🏗️

Contribute to EthBuilders

🚀 Prepare and store our community newsletter.

• About
• Contribute
• This repo
  • Process for writing the Newsletter
  • Styleguide & Suggestions

Subscribe to the Meetup. We send out our newsletters via Meetup for now.

Similar to the Rust and Protocol Lab's (makers of IPFS) communities, we have a grassroots newsletter that talks about the achievement of our community.

This will help:

• Highlight cool projects made by our community
• Help keep the community informed with the most up to date education via grassroots effort
• Keep people in the loop about what is going on in the Ethereum.
• Give shouts
• Post job postings

A distributed newsletter is a good newsletter.

You can add to sections like:

• 👨‍🎨 Show and Tell
  Show off your cool projects to community. What did you build or learn this week?
• 🎟 Community Events
  Other events coming up
• 🔥 Cool Radar
  What do you think is cool?
• 📰 News
  Upcoming news, DeFi updates and more
• 🕵️‍♂️ Hack of the Week
  Post Mortems, security issues and 🌶 spicy takes
• 👩‍💻 Updates
  Updates to any of our community open source projects
• 🤑 Jobs
  Place job postings with full job descriptions.

👨‍💻 What to learn how to use Github? 👩‍🏫 Learn about the command line. Then see this great video Github for Poets by Dan Shiffman or take this Git course.

• See or make something cool.
• If a new newsletter:
  • Open a Pull Request, copy ./template.md.
  • Add it to /published
  • Rename using naming convention similar to: 2021-jan-01.md.
  • Our newsletters run Monday to Sunday, so start with a Monday date.
• If an existing newsletter:
  • Open a Pull Request
  • Collect feedback via the comment and iterate.
• Once accepted:
  • We will post to Medium
  • Tweet it out from your Twitter!

💡 Got an idea to make the newsletter better? ♥️ Open an issue!

• Stores the final versions for past newsletters.
• Tracks issues related to the newsletters in the issues
• Stores tools used to make the roundups
• Is used to collaborate on new issues.
• Sumbit a PR to insert a contribution! Let us know what you did this week!

• Use people's GitHub handles or their real names if they choose to. Example: "Anthony Albertorio", @tesla809.
• Try and include everyone who has made a PR or commented on an issue.
• Highlight, don't just summarize. Make a great attempt at description.
• In general, err on the side of giving credit to everyone involved. When people do the lion's share, mention them first. Something like "@skellet0r, @chanhosuh, @tesla809, etc..."
• In general, try linking larger phrases instead of single words. They're easier to notice and click on links.
• In general, try highlighting why something is cool.
• Have fun!