Skip to content

Commit 84f52c5

Browse files
authored
Stubbing out the aep tooling list
will update links after #231 is addressed
1 parent 5631df6 commit 84f52c5

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

pages/general/adopting.md

+12-7
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,16 @@
11
# Adopting AEPs for your company
22

3-
Currently, we encourage adoption of AEPs via having your APIs adhere to the
4-
guidance served at https://aep.dev.
3+
By adopting the guidelines from the API Enhancement Proposals, you establish a much
4+
tighter and efficient possibility space. APIs that follow the
5+
[AEP guidance](https://aep.dev) from the design stage are:
56

6-
In the future, we plan to introduce a broader ecosystem of tooling including:
7+
- More consistent APIs within and across teams, reducing cognitive load for consumers
8+
- Argue less about API design decisions, saving time thanks to AEPs explar design patterns
79

8-
- A forkable repository which allows for internal mirrors and
9-
organization-specific guidance.
10-
- Client-side and server-side code generators.
11-
- Validators to ensure adherence to the specification.
10+
Having an AEP-compliant API also means benefitting from the AEP ecosystem of tooling, such as:
11+
12+
- Linters and validators to ensure adherence to the AEP design specification [proto]()/[openapi]()
13+
- Command line tool that make it easier to work with APIs ([aepcli](https://github.com/aep-dev/aepcli))
14+
- Client-side and server-side code generators ([aepc](https://github.com/aep-dev/aepc))
15+
- A Terraform provider ([terraform-provider-aep](https://github.com/aep-dev/terraform-provider-aep))
16+
- ... and more! Please start a [discussion](https://github.com/aep-dev/aep.dev/discussions) if there is something you wish to see, validate, or prioritize.

0 commit comments

Comments
 (0)