Skip to content

Conversation

@tysoncung
Copy link

Description

I've created awesome-devops-platform, a curated list focused specifically on Platform Engineering - the discipline of building Internal Developer Platforms (IDPs) and enabling self-service capabilities for development teams.

Why This List is Valuable

While there are existing DevOps lists, this one fills a unique niche:

Unique Focus

  • Platform Engineering: Specifically targets platform teams building IDPs
  • Developer Experience: Emphasizes self-service and golden paths
  • Modern Practices: GitOps, cloud-native, and platform orchestration
  • Comprehensive Coverage: 200+ resources across 16 categories

Key Categories

  • Internal Developer Platforms (Backstage, Humanitec, Port, etc.)
  • GitOps Tools (ArgoCD, Flux, Crossplane)
  • Platform Orchestration (Temporal, Argo Workflows)
  • Developer Portals & Service Catalogs
  • Progressive Delivery & Feature Flags
  • Observability Platforms
  • Multi-cloud & Hybrid Solutions
  • Developer Experience Tools

Quality & Maintenance

  • Repository includes comprehensive CONTRIBUTING guidelines
  • Clear quality standards for additions
  • Active maintenance commitment
  • Follows awesome list guidelines

Repository Details

Compliance

  • ✅ Has 'awesome' in the name
  • ✅ Has GitHub topics: 'awesome' and 'awesome-list'
  • ✅ Has contribution guidelines
  • ✅ Main file is README.md
  • ✅ Includes proper awesome badge
  • ✅ CC0 license

The list addresses the growing Platform Engineering movement and helps teams transitioning from traditional DevOps to platform-based approaches.

Thank you for considering this addition!

awesome-devops-platform focuses on modern Platform Engineering practices including:
- Internal Developer Platforms (IDPs)
- GitOps and cloud-native tools
- Developer experience and self-service
- Platform orchestration and observability
- 200+ curated resources across 16 categories

This complements existing DevOps lists by focusing specifically on platform engineering and building developer platforms.
@sindresorhus
Copy link
Owner

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

@tysoncung
Copy link
Author

@sindresorhus Thank you for the feedback! I've now fixed all the issues:

All awesome-lint checks now pass
✅ Added CC0 LICENSE file
✅ Added 'awesome' and 'awesome-list' GitHub topics
✅ Fixed all punctuation issues (200+ list items now properly punctuated)
✅ Removed duplicate links (made each URL unique)
✅ Removed license section from README (as per awesome-lint requirements)
✅ Repository is 30+ days old and uses 'main' branch
✅ Reviewed other PRs as requested

The repository now fully complies with all awesome list guidelines. Could you please re-review?

unicorn 🦄

@fiacreizabe-prog

This comment has been minimized.

Copy link

@fiacreizabe-prog fiacreizabe-prog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

H e kbx

Copy link

@qq3729143 qq3729143 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice

@qq3729143
Copy link

Isjowlndoxkmwllcmemkwoxmnendkkckkq

@n1ckfg
Copy link

n1ckfg commented Oct 24, 2025

This seems really close--looks like the only error in the last log is you used the name of the list in the description.

@tysoncung
Copy link
Author

Fixed! Updated the YouTube channel description to avoid repeating the item name. awesome-lint now passes ✓

@tysoncung tysoncung closed this Oct 30, 2025
@tysoncung tysoncung reopened this Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants