Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update _index.md #330

Merged
merged 1 commit into from
May 20, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/drops_contribution_guidelines/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ linkTitle: "Jumpstart Drops contribution guidelines"
weight: 7
---

## Jumpstart contribution guidelines
## Jumpstart Drops contribution guidelines

**Welcome to Jumpstart Drops contribution guidelines!**

We welcomes contributions following the guidelines described in the Arc Jumpstart [contribution guidelines](./../contribution_guidelines/).
We welcome contributions following the guidelines described in the Arc Jumpstart [contribution guidelines](./../contribution_guidelines/).

Our goal is to create a simplified contribution process for our users that guarantees high-quality standards for all submissions. Contributing a Drop is as simple as opening a GitHub Pull Request following a simple [scheme](https://github.com/Azure/arc_jumpstart_drops/blob/main/SCHEMA.md). We're also working on a streamlined **“Create Drop”** wizard which will walk you through the process step by step, making it effortless to submit your new Drop. With our wizard, you'll also enjoy a live preview of how your contribution will appear on the website. This ensures everything is perfect before sharing it with the community. Stay tuned, we're expecting this wizard to become available on the Jumpstart Drops homepage in the very near future.

Expand Down Expand Up @@ -107,4 +107,4 @@ The folder structure guidelines for submitting Drop source code as part of a Pul

1. Create a new folder named *artifacts* inside the root folder. This folder should contain all the files and scripts necessary to run the Drop.

1. Optionally, create a new folder named *media* inside the artifacts folder. This folder can contain any screenshots or architecture diagrams that showcase the Drop.
1. Optionally, create a new folder named *media* inside the artifacts folder. This folder can contain any screenshots or architecture diagrams that showcase the Drop.
Loading