Preparing Your Automation for Publication
Table of Contents
This is what you'll need to have before submitting your automation for publication
Image
A 744 x 300 image that illustrates the automation. Note that for sharper display on high-resolution screens, image will be appear at half size (372 x 150)
Alt image text
This is some text that helps people who cannot see the image understand what the image portrays
Example 1:
Some GitHub profile Images of people who have contributed to the hackforla.org website and titles under some names indicating Designer, Stakeholder, Product all in uppercase text.
Example 2:
Jekyll logo with test tube and words Gather Data Types all in green.
Description of Automation
See our Guide: Write a Short Narrative Description about Your Automation
Health Files
See our Guide: Supporting Your Automation with Community
Current Status of Automation
- in use and ready to deploy
- in use and being refactored
- ready to deploy
- in development
- ready for development
- in ideation
- abandoned
As seen on
If status in use, what codebase can it be seen in?
Help wanted
You can list all that apply:
- needs maintenance
- needs support for users
- needs refactoring
- needs documentation
- needs peer review
- needs to be built
- needs to be researched
- needs advice
- If advice is needed, write a short description of what you need
- needs takeover
Ready to submit your automation?
Use our issue template for submitting the information we will need for the project card to appear on the 100automations.org website