Skip to content

Conversation

thegagne
Copy link

@thegagne thegagne commented Sep 5, 2025

This PR adds information about the tooling and ecosystem for AEPs. The documentation enhances the user experience by providing clear guidance on available tools and the surrounding ecosystem that supports AEP development and implementation.

🍱 Types of changes

What types of changes does your code introduce to AEP? Put an x in the boxes that apply

  • Enhancement
  • New proposal
  • Migrated from google.aip.dev
  • Chore / Quick Fix

📋 Your checklist for this pull request

Please review the AEP Style and Guidance for contributing to this repository.

General

💝 Thank you!

@thegagne thegagne requested a review from a team as a code owner September 5, 2025 13:58
Copy link
Member

@rambleraptor rambleraptor left a comment

Choose a reason for hiding this comment

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

I love this! Thank you for doing this. I have a couple suggestions but broadly looks good.

Especially love the AI, User Interface, and Linting sections.

- **[aep-explorer](https://github.com/aep-dev/aep-explorer)** - Interactive web
UI for AEP-compliant APIs

**Infrastructure-As-Code and GitOps**
Copy link
Member

Choose a reason for hiding this comment

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

What do you think about removing the "planned" tools from all these lists?

Then we can put Terraform and aepcli under this list

Suggested change
**Infrastructure-As-Code and GitOps**
**Developer Tools**

- **Kubernetes CRD generator** - Generate Custom Resource Definitions for
Kubernetes for AEP-compliant APIs (_Planned_)

**Operations & Governance**
Copy link
Member

Choose a reason for hiding this comment

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

Let's get rid of this list while it's empty

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.

2 participants