You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-13Lines changed: 25 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,14 @@
1
+
## Create a new APIOps project (CLI)
2
+
3
+
4
+
```bash
5
+
npm create apiops@latest
6
+
```
7
+
8
+
This command runs the `create-apiops` initializer package and generates a starter APIOps project template in your current directory.
9
+
10
+
11
+
1
12
# APIOps Cycles Method
2
13
3
14
This repository contains the source for the APIOps Cycles method, including resources such as canvases. It can be used for multiple purposes, such as the method website (https://www.apiopscycles.com/), which is generated from these files, and the Canvas Creator tool that allows creating, importing and exporting the canvases, and provides a UI. (https://canvascreator.apiopscycles.com/).
@@ -13,24 +24,35 @@ APIOps and APIOps Cycles are trademarks owned by Osaango Oy (https://www.osaango
13
24
```
14
25
├── src/
15
26
│ ├── assets/ # APIOps Cycles logos and other core assets which you might need in your tooling or product
27
+
│ ├── lib/ # Method-engine, "walks" developer or AI through the method starting from needs, also used by the CLI when using the create apiops template
16
28
│ ├── data/method/ # The Method JSON files (structure, relationship, and guideline content)
17
29
│ ├── data/method/canvas/ # The Canvases included in the method as JSON files (also used by tools like Canvas Creator)
18
30
│ ├── snippets/ # Raw markdown files used for long content for resource docs (only essential extensions for the json files)
19
31
├── scripts/ # Utility scripts
20
32
└── package.json
33
+
├── skills/ # AI skills that help use the method to design APIs
34
+
├── packages/
35
+
└── create-apiops # scaffolding template published as node module. Starts a new guided API design project with `npm create apiops@latest`
21
36
```
22
37
23
-
## Requirements
38
+
## Integrating the method in to tools, and developer workflows
24
39
25
-
You can use the JSON files as is and download a .zip file or clone the repository. You can also install them using `npm install apiops-cycles-method-data`.
40
+
You can use the JSON files as is and download a .zip file or clone the repository. You can also install them using `npm install apiops-cycles-method-data`, or create a new API design and/or development project with `npm create apiops@latest`
26
41
27
42
The module exposes top-level exports so you can import the data files directly, for example:
The `method-engine` export is intended for reusable APIOps workflow logic. It gives CLIs, AI agents, apps, and APIs the same station recommendation, resource lookup, and canvas generation behavior without reimplementing the method rules.
55
+
34
56
Validate the files locally with:
35
57
36
58
```bash
@@ -46,16 +68,6 @@ Install dependencies once with:
46
68
npm install
47
69
```
48
70
49
-
## Create a new APIOps project (CLI)
50
-
51
-
Once `create-apiops` is published to npm, you can scaffold a new project with:
52
-
53
-
```bash
54
-
npm create apiops@latest
55
-
```
56
-
57
-
This command runs the `create-apiops` initializer package and generates a starter APIOps project template in your current directory.
58
-
59
71
## Contributing
60
72
61
73
### Reporting issues or requesting features
@@ -64,7 +76,7 @@ If you spot a problem in the documentation or have an idea for new content, plea
64
76
65
77
### Editing or adding content
66
78
67
-
The main method files (instructions, guidelines, method structure) is located in the the JSON files at `src/data/method/`. These base files (`lines.json`, `stations.json`, `resources.json`, `criteria.json` and `station-criteria.json`) are not localized and live at the root of the folder. Textual values in them reference label keys. English labels are in `src/data/method/en-US` and translations are provided in `labels.lines.json`, `labels.stations.json`, `labels.resources.json` and `labels.criteria.json` under each locale folder. Some longer or more complex resource pages like the API Audit Checklist also use markdown snippets `src/snippets/` linked to the `resources.json`. Do not use any frontmatter in the snippet files. Any supported markdown markup is ok. See references from [Starlight markdown reference](https://starlight.astro.build/guides/authoring-content/) and [Extended markdown reference](https://www.markdownguide.org/extended-syntax/).
79
+
The main method content files (instructions, guidelines, method structure) are located in the the JSON files at `src/data/method/`. These base files (`lines.json`, `stations.json`, `resources.json`, `criteria.json` and `station-criteria.json`) are not localized and live at the root of the folder. Textual values in them reference label keys. English labels are in `src/data/method/en-US` and translations are provided in `labels.lines.json`, `labels.stations.json`, `labels.resources.json` and `labels.criteria.json` under each locale folder. Some longer or more complex resource pages like the API Audit Checklist also use markdown snippets `src/snippets/` linked to the `resources.json`. Do not use any frontmatter in the snippet files. Any supported markdown markup is ok. See references from [Starlight markdown reference](https://starlight.astro.build/guides/authoring-content/) and [Extended markdown reference](https://www.markdownguide.org/extended-syntax/).
68
80
69
81
Each station links to specific entry criteria followed by the next core station's criteria as exit criteria.`criteria.json`, `station-criteria.json` and `labels.criteria.json`
0 commit comments