Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Omarvio.com

Open
  • Is something wrong?
#3,335 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws
Domain
backend, cloud

Research direction

Start with PUBLISHING.md and the _pattern-model template in aws-samples/serverless-patterns, then clone the model into a new pattern directory with a README and example-pattern.json covering intro.text, resources, and authors. Validate with cd _scripts && npm i and node _scripts/validate.js your-pattern/example-pattern.json. Done means the schema check passes and a PR containing only that one pattern directory is open; note the issue's own "GitHub PR for template" section is empty.

Written by the indexing model from the issue text.

Description

To submit a template to the Serverless Patterns Collection, submit an issue with the following information.

IMPORTANT
Patterns are intended to be primarily IaC-focused implementations of 2-4 AWS services, with minimum custom code. They should be commonly used combinations that help developers get started quickly. If you have a utility, demo, or application, submit these to the Serverless Repos Collection instead.

ONLY SUBMIT ONE PATTERN CHANGE PER PR. Multiple patterns or files spanning multiple pattern directories will be automatically rejected.

Patterns may take up to 4-6 weeks to review, test, and merge but there is no SLA and can take significantly longer due to other work the team has.

To learn more about submitting a pattern, read the publishing guidelines page.

  1. Use the model template located at https://github.com/aws-samples/serverless-patterns/tree/main/_pattern-model to set up a README, template and any associated code.

  2. THIS PROCESS HAS BEEN SIMPLIFIED. All the information below must be provided in the "example-pattern.json" file cloned from the model **

Note the following information for the model:

  • Description (intro.text) should be a 300-500 word explanation of how the pattern works.
  • Resources should like to AWS documentation and AWS blogs related to the post (1-5 maximum).
  • Author bio may include a LinkedIn and/or Twitter reference and a 1-sentence bio. Use your LinkedIn profile ID and Twitter handle, not URLs.
  • Returning authors with a profile page at https://serverlessland.com/about/your-name can list "contributors": ["content/contributors/your-name.json"] instead of authors.
  • Pull requests check "example-pattern.json" against the pattern schema. To check it locally, run cd _scripts && npm i, then from the repo root node _scripts/validate.js your-pattern/example-pattern.json.

You must ensure that the sections of the model README.md are completed in full.

GitHub PR for template:

Dominant language
Python
Stars
1.8k
Forks
1.1k
Avg merge
4d 9h
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/serverless-patterns

All issues in aws-samples/serverless-patterns

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.