- An introduction to contributing to open-source
- Learn/improve your technical writing
- Find inspiration for your next project
Having difficulties starting your first contribution to Open-Source Project? Or maybe you have contributed and just looking for the next issue to get your teeth into! This is where The Project-O-Matic comes in! The projects are loaded via markdown files. I have seeded the database with a few to get started. The next step involves the help of developers like you. We need you to provide project ideas and solutions for your language/framework of choice. Follow the steps below to get an idea of how you can contribute to the project and simultaneously improve your technical writing skills.
Two things that can improve your coding knowledge are building projects and teaching others. The Project-O-Matic open-source collaboration effort helps with both! You build projects as you usually would, then you share the solutions of how you created them by creating a blog post on Hashnode. Writing the steps you have taken to create a project and the concepts you have learned cement the knowledge for future use and forces you to explain it in a way understandable to others. Contribution is entirely optional.... for now cocks gun. But seriously, it's your choice to improve your coding and writing skills while contributing to open-source. This is just here to guide you in these areas so you can go off and create/contribute to amazing things.
Head to the website https://project-o-matic.herokuapp.com/ and choose your skill level, language, and framework. Please sit back and let the project-o-matic work its magic. You will be given a project brief that will tell you what the project will achieve and what features are expected. Some project briefs may have a solution if you get stuck or want to see how other developers have approached the problem. Many of them won't; that’s where the following two points come in.
Check out this guide to learn how to contribute to open-source
- Create a markdown file using this template. You can create it in any text editor or an online markdown editor. Save it locally with the name of the project. E.g., Calculator. md
- Consider each step someone would need to take to create a project.
- If possible, make three different variations. One for beginners, one with more steps for intermediate, and one fully fledged app to cover more profound concepts for advanced learners.
# <Project Title Name>
# REMOVE - Example(Calculator)
*<Project Description>*
REMOVE - *Example(Create a calculator)*
## Features
<Add a list of features>
- Create a grid UI
- Add numbers 0 - 9
- Add a plus button
- Add a minus button
- Add an equals button
- Add a multiply button
- Add a modulo/remainder operator
- Add a decimal button
- Add a reset button
- Input section to show entered numbers
### Created By: [YOUR NAME](YOUR CHOSEN SOCIAL MEDIA OR WEBSITE)
- Download the code
- Open in your chosen IDE
- Upload the file to the wwwroot < project-files < beginner/intermediate/advanced depending on the markdown file. Ensure each file for each skill level has the same name.
- Commit your code to source control on GitHub.
- Create a pull request.
- Wait for it to be reviewed.
- Merge it into the main branch.
- The system does the rest of the work to add the project to the database.
Check out this guide on getting started with technical writing
- Head over to Hashnode.
- Create an account if you don't have one
- Create a new blog post.
- Using markdown, write up the steps you took to create a project, including any links, libraries, images, etc.
- Publish your post.
- Then copy the slug of your post. The slug is the line following your hashnode blog domain.
- Head over to the GitHub repo.
- Download the code.
- Open your chosen IDE.
- Open Solutions.json, which is under wwwroot inside a folder called solution-files.
- Copy and paste the last entry in this file and fill in the required details.
- Slug is the part of the blog post URL you copied earlier.
- HostName is your Hashnode account name.
- ProjectName is the name of the project file your solution relates to. If you need to check this it will be under wwwroot < project-files. If one doesn't exist for your created solution, add one using the guide above in "How to add a project.”
- LanguageName is the language it relates to. This is always in PascalCase.
- FrameworkName is the framework it relates to. If the project doesn't use a framework, it will always be "Vanilla.” If it does, add the correct name. e.g., React, Vue, etc.
- Save the file.
- Commit your code to source control on GitHub.
- Create a pull request.
- Wait for the code to be reviewed.
- Merge the code into the main branch.
- Blazor Server-Side
- HTML & CSS
- Heroku
If your chosen tech stack or framework isn't available, you can create an issue or contact me on Twitter @TechPickleJoel
This project was created as part of the Planetscale X Hashnode Hackathon