Skip to content

chore(docs): add customer references section #1420

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

Merged
merged 3 commits into from
Apr 25, 2023

Conversation

dreamorosi
Copy link
Contributor

Description of your changes

This PR introduces a new section to the docs homepage that gives more details to the reader on how to support Powertools and also adds the customer references that were shared with this repo.

The PR also adds a new page called "We Made This (Community)" that contains community content that was submitted and/or published about Powertools.

The PR is a followup of the aws-powertools/powertools-lambda-python#2159 and once merged will close #1271.

Related issues, RFCs

Issue number: #1271

Checklist

  • My changes meet the tenets criteria
  • I have performed a self-review of my own code
  • I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding changes to the examples
  • My changes generate no new warnings
  • The code coverage hasn't decreased
  • I have added tests that prove my change is effective and works
  • New and existing unit tests pass locally and in Github Actions
  • Any dependent changes have been merged and published
  • The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

  • I have documented the migration process
  • I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

@dreamorosi dreamorosi self-assigned this Apr 25, 2023
@dreamorosi dreamorosi linked an issue Apr 25, 2023 that may be closed by this pull request
3 tasks
@pull-request-size pull-request-size bot added the size/M PR between 30-99 LOC label Apr 25, 2023
@github-actions github-actions bot added the internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) label Apr 25, 2023
@pull-request-size pull-request-size bot added size/L PRs between 100-499 LOC and removed size/M PR between 30-99 LOC labels Apr 25, 2023
@dreamorosi dreamorosi merged commit 5d680a0 into main Apr 25, 2023
@dreamorosi dreamorosi deleted the 1271-support-lambda-powertools branch April 25, 2023 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) size/L PRs between 100-499 LOC
Projects
None yet
1 participant