[phrotoma]

On the landing page one can find:

- a list of AEPs (explore the AEPs)

- a link to the AEP ecosystem

- a description of how AEPs are built

- a list of AEP clients

- something to do with open standards and versioning

- a blog

and

- a single sentence suggesting the project has something to do with APIs

If any maintainers stop by this comment section, I suggest offering some explanation about what this project _does_.

[locknitpicker]

> If any maintainers stop by this comment section, I suggest offering some explanation about what this project _does_.

This. It's a pretty awful way to present anything. The reader is still clueless and unsure about what they are reading even after navigating through 3 or so links. At each click I was hoping to read anything related to APIs but all I was reading is bureaucrat noise.

Perhaps it's a good idea. I can't tell. I wonder if anyone can.

[9dev]

Seconded. And even browsing the actual AEPs, they are presented so confusingly, it's hard to say how it actually works. There's lots of prose, when the first thing I would want to see of a concept is a plain-text HTTP request and response, not a clever Protobuf definition and colored words all over the place.

[jiggawatts]

Any project where all of the links on the first page are “meta” such as “project governance” is my little red flag that tells me there is zero value to be found here.

[Terretta]

Start here: https://aep.dev/llms.txt