replaced with draft content from #384

per #395 the "builder" is now a developer writing their own automation

_guides/start_building.md

@@ -1,43 +1,36 @@
 ---
 title: Start Building
-description: The many ways to get involved in automation building, depending on your experience and interests 
+description: If you'd like to build your own automation, here's how to get started
 status: active
 display: true
 category: 1
 ---
 
-## Want to Build an Automation?
-You can help build automations that are at different phases and find opportunities that suit your level:
+## Steps to add an existing automation to 100 Automations:
 
-1. You have your own idea and you want to build it yourself
-2. You want to build an automation from scratch but don’t have your own idea
-3. You want to contribute to an automation that’s already being developed
+1. Create a new repository under the 100 Automations - [quick link here](https://github.com/organizations/100Automations/repositories/new)
 
-See below for how to get started!
+2. Ensure the repository contains, at a minimum:
+- A Readme
+- Licence: we use the GNU General Public License v2.0 at Hack for LA [**Double-check this**]
+- A Code of Conduct.md
+- A Security.md
+- A Support.md
+- A Contributing.md
 
-## Build Your Own Automation
-So you have an idea for an automation and want to build it yourself? You can either fill out this [Automation Form](https://docs.google.com/forms/d/e/1FAIpQLSeGJrU92Tj5Ft763MMWpSwyB6VqctPXzu8WKIy4xTjf1nJg0Q/viewform?usp=sf_link).
+3.  Once the repository is complete with documentation and the automation code, complete [this automation card template](https://github.com/100Automations/futureautomations/issues/new?assignees=&labels=documentation%2C+review&template=-automation-proposal.md&title=%5BAutomation+Name%5D+Proposal) in the Future Automations repo and move it to the [Review column](https://github.com/100Automations/futureautomations/projects/1#column-9876980)
 
-If you use the Automation Form, one of the 100 Automations team will take the information, create an issue card for you in the automation creation workflow in GitHub, and reach out to you once that is ready.
+4. If you prefer completing the automation card template over multiple sessions, place it in the [In Progress column](https://github.com/100Automations/futureautomations/projects/1#column-9876974) on the Future Automations board
 
-If you use the Automation Proposal template, our [automation workflow overview](https://github.com/100Automations/futureautomations/wiki/Workflow-Guide-for-Ideators) will help you get an understanding of how you can use this to develop automations.
+5. Once the repo and template card are ready for review, the 100 Automations team will reach out to partner on getting the materials together to get the automation ready for the 100 Automations website. You will use [this automation materials template](https://github.com/100Automations/futureautomations/issues/new?assignees=&labels=documentation%2C+good+first+issue&template=create-automation-card-for--automation-name-.md&title=Create+automation+card+for+%5Bautomation+name%5D) for this purpose.
 
-When your automations get to the "In progress" phase of the workflow, be sure to read our [Guide on Creating an Automation Repo](url) to get you set up at the build phase.
 
-## Build From Automations Log
-Don't have your own idea? We have a log of well-developed and documented automation ideas vetted by the 100 Automations team that need development. So you can jump right in and start developing.
+## References ##
 
-To find an automation you'd like to build, go to the [Automations Log here](https://github.com/100Automations/futureautomations/projects/1#column-9876973), self-assign yourself on the issue, and move it to the In Progress (actively working) column. 
+Here is an example of an [automation repo](https://github.com/100Automations/true-github-contributors)
+Here are guides on:
+- Writing a good readme
+- Writing good health files (code of conduct, contributing.md, support.md, security.md)
 
 
-## Improve An Automation
-Some automations are already in development but still need help. Click on the "needs help" part of an automation card on our home page and see what type of help is needed for that automation. To find out more about an automation, click on the Readme button. 
-
-Here is the [anatomy of an automation card](https://github.com/100Automations/Website/blob/gh-pages/_guides/project_card_anatomy.md) to hep you navigate around automations on our homepage.
-
-## Need help at any stage?
-If you need help at any stage of the build process, be sure to move your automation card in the [Futureautomations board](https://github.com/100Automations/futureautomations/projects/1) to the [Questions for the 100 Automations Team](https://github.com/100Automations/futureautomations/projects/1#column-12391599){target="_blank"} column.
-
-If your automation needs help, in the form of peer review, maintenance, support for users, refactoring, or documentation, make sure to apply the "Needs help" and the type of help labels to your automation card.
-
-Happy developing!
+If you have any additional questions, please feel free to reach out to the 100 Automations team at [email protected]. We look forward to supporting you in your contributions!