🙌 Looking for collaborators & contributors

🙌 Looking for collaborators & contributors

This project — a TypeScript Serverless Framework plugin for AWS AppSync — is healthy, widely
used, and has a friendly, well-organized codebase. I'm looking for people who'd like to help
keep it that way and shape where it goes next. All experience levels are welcome, and even
a couple of hours a week makes a real difference.

You can help as a reviewer, a contributor, or both.

Why contribute here?

• Clean, modern codebase — TypeScript, targeting Serverless Framework v3/v4.
• Real test coverage — Jest unit tests plus end-to-end tests that synthesize CloudFormation
  offline (no AWS account needed to run them), with eslint + tsc and Prettier on top.
• Good docs & examples — a doc/ folder and a large examples/ directory you can learn
  from and extend.
• Tight feedback loop — npm test, npm run test:e2e, and npm run lint run locally in
  minutes; most changes are small and surgical.
• Active roadmap — recently triaged the backlog down to a focused set of actionable items,
  so it's easy to find something worth doing.

🌟 Recognition & visibility

Your work won't go unnoticed. As a thank-you for contributing, I'm happy to:

• Feature you in the README and in release notes when your changes ship.
• Help you publish a blog post about a feature you build — co-authored or as a guest post,
  and linked from the project. Great for your portfolio and for the community.
• Shout out your work to the Serverless / AWS AppSync community and on social.
• Grow into a recognized collaborator/maintainer — sustained contributors can earn
  triage/review rights and a standing place on the team.

If turning a contribution into a write-up or talk would help you, just say so — I'll support it.

Ways to help

Review (lowest friction — no AWS needed):

• Read through open PRs and leave constructive feedback
• Help triage and reproduce issues
• Sanity-check that changes have tests and match existing patterns

Contribute code:

• Pick up a good first issue or help wanted ticket
• Add tests/examples for existing features
• Improve docs (one of the highest-leverage, lowest-risk ways to start)

Good starter areas

If you're not sure where to begin, these are well-scoped on-ramps:

• New data sources — e.g. the Amazon Bedrock runtime data source. Adding a data source
  type closely mirrors the existing ones (DynamoDB, Lambda, HTTP, EventBridge…), so it's a
  great first feature.
• Docs improvements — e.g. recipes for cross-stack outputs/exports, retaining resources
  via resources.extensions, and common data-source gotchas. Low risk, high impact.
• Small, contained fixes — many open issues are a one-file change plus a test.
• Reviewing PRs — if you'd rather not write code yet, reviews are hugely valuable.

(Look for the good first issue and help wanted labels to find tagged tickets.)

How a change should look

• Branch off master, keep changes small and focused
• Match the existing style and patterns (Prettier handles formatting)
• Add tests — positive and negative cases, mirroring the nearby tests
• Make sure all green: npm run build, npm run lint, npm test, npm run test:e2e

How to get started

1. Browse the open issues and PRs (start with good first issue / help wanted)
2. Comment on this thread or email me at sid88in@gmail.com
3. Skim the contributing guidelines and the doc/ folder
4. Open a PR or start reviewing — and don't hesitate to ask questions!

Thanks for considering it — this project is what it is because of contributors like you. 💙