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: CONTRIBUTING.md
+47-9Lines changed: 47 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,8 +73,44 @@ cd website
73
73
- Go to https://github.com/redhat-data-and-ai/website
74
74
- Click "New Pull Request"
75
75
- Describe your changes
76
+
- Confirm the **Super linter** GitHub Actions check passes (required)
76
77
77
-
## Documentation Standards
78
+
## Before Submitting a Pull Request
79
+
80
+
This site does **not** use [pre-commit](https://pre-commit.com/) hooks. Validation runs in CI and via Makefile targets.
81
+
82
+
### Required checks
83
+
84
+
```bash
85
+
# Production Hugo build — must complete without errors
86
+
hugo --gc --minify
87
+
```
88
+
89
+
Confirm the **Super linter** workflow passes on your pull request. That job runs on every PR and is the lint gate for this repository.
90
+
91
+
### Optional local checks
92
+
93
+
```bash
94
+
# Super Linter (same as CI)
95
+
make super-linter
96
+
97
+
# Link checker (htmltest — also runs on a nightly schedule)
98
+
make test
99
+
100
+
# Spell check
101
+
make spellcheck
102
+
```
103
+
104
+
**Apple Silicon Macs:**`make super-linter` often fails locally with `no image found ... architecture "arm64"` because the slim Super Linter image is x86-only. Use the PR's GitHub Actions result instead.
105
+
106
+
### Checklist
107
+
108
+
-[ ]`./serve.sh` — preview looks correct in the browser
109
+
-[ ]`hugo --gc --minify` — builds without errors
110
+
-[ ] Super linter CI check passes on the PR
111
+
-[ ] Commands and paths in docs match the current template repositories
112
+
-[ ] Code examples tested where applicable
113
+
-[ ] No emojis in headings (see [Documentation Standards](#documentation-standards))
78
114
79
115
### Writing Style
80
116
@@ -139,11 +175,12 @@ content/
139
175
140
176
### Before Submitting
141
177
142
-
-[ ] Test locally with `./serve.sh`
143
-
-[ ] No build errors (check Hugo output)
144
-
-[ ] All links work
145
-
-[ ] Code examples are tested
146
-
-[ ] Spelling checked
178
+
-[ ] Preview with `./serve.sh`
179
+
-[ ]`hugo --gc --minify` completes without errors
180
+
-[ ] Super linter CI check passes (use GitHub Actions if `make super-linter` fails on Apple Silicon)
181
+
-[ ] Commands and links verified against current template repos
Copy file name to clipboardExpand all lines: README.md
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,12 +21,35 @@ brew install hugo asciidoctor
21
21
### Building
22
22
23
23
```bash
24
-
#Build static site
25
-
hugo --cleanDestinationDir
24
+
#Production build (run before opening a PR)
25
+
hugo --gc --minify
26
26
27
27
# Output in public/ directory
28
28
```
29
29
30
+
### Before Opening a Pull Request
31
+
32
+
This repository does **not** use pre-commit hooks (unlike the template repos). CI runs **[Super Linter](https://github.com/super-linter/super-linter)** on every push and pull request.
33
+
34
+
Run these checks locally before you push:
35
+
36
+
```bash
37
+
# 1. Production Hugo build (required — fast, works on all platforms)
38
+
hugo --gc --minify
39
+
40
+
# 2. Super Linter (matches CI — see note for Apple Silicon below)
41
+
make super-linter
42
+
43
+
# 3. Optional: link checker (nightly in CI, not PR-gated)
44
+
make test
45
+
```
46
+
47
+
**Apple Silicon (M-series Mac):**`make super-linter` may fail locally because the slim Super Linter container image has no `linux/arm64` build. In that case, rely on the **Super linter** check on your pull request in GitHub Actions.
48
+
49
+
**Development preview:**`./serve.sh` is for browsing changes at http://localhost:1313/ — it does not replace the production build step above.
50
+
51
+
See [CONTRIBUTING.md](CONTRIBUTING.md#before-submitting-a-pull-request) for the full checklist.
Copy file name to clipboardExpand all lines: content/_index.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,17 @@ title: "AI Templates"
6
6
7
7
Go beyond demos and proofs of concept. AI Templates deliver battle-tested, production-ready components for building AI applications on Kubernetes, following best practices.
8
8
9
+
{{< info title="What's New" >}}
10
+
**Deep Agent update (August 2026):** The Agent and UI templates have moved to [LangGraph Deep Agents](https://github.com/langchain-ai/deepagents). **template-agent** is now a config-as-code Deep Agent runtime (orchestrator, subagents, skills, MCP integration). **template-ui** has been updated to work with the new Deep Agent streaming API, including HITL interrupts, task progress, and markdown-first rendering. [Read the announcement →](/news/)
11
+
{{< /info >}}
12
+
9
13
## What are AI Templates?
10
14
11
15
AI Templates are reusable, modular components that accelerate your AI development journey. Each template is designed to work independently or as part of a complete AI application stack:
12
16
13
17
-**[MCP Server Template](/templates/mcp-server/)** - Build Model Context Protocol servers that extend AI agent capabilities
14
-
-**[Agent Template](/templates/agent/)** - Create LangGraph-based AI agents with enterprise security and observability
15
-
-**[UI Template](/templates/ui/)** - Deploy modern chat interfaces that work seamlessly with our agent template
18
+
-**[Agent Template](/templates/agent/)** - Deep Agent orchestration with config-as-code, subagents, skills, and enterprise observability
19
+
-**[UI Template](/templates/ui/)** - React chat UI for the Deep Agent streaming API
16
20
17
21
## Why Use AI Templates?
18
22
@@ -38,7 +42,7 @@ Deploy anywhere - OpenShift, EKS, GKE, or any Kubernetes cluster.
└── reference/ # Stack architecture, config, enterprise features
29
29
```
30
30
31
31
## Writing Guidelines
@@ -68,17 +68,26 @@ graph TD
68
68
69
69
## Testing Changes
70
70
71
-
Before submitting:
71
+
This site does **not** use pre-commit hooks. Run these before opening a pull request:
72
72
73
73
```bash
74
-
#Run local server
74
+
#Preview in the browser
75
75
./serve.sh
76
76
77
-
# Check for broken links
78
-
# Verify formatting
79
-
# Test on multiple screen sizes
77
+
# Production build (required)
78
+
hugo --gc --minify
79
+
80
+
# Super Linter — same as CI (may not run on Apple Silicon; check the PR workflow)
81
+
make super-linter
82
+
83
+
# Optional: broken-link scan (nightly in CI)
84
+
make test
80
85
```
81
86
87
+
On **M-series Macs**, `make super-linter` can fail because the container image has no ARM build. Confirm the **Super linter** check passes on your pull request in GitHub Actions instead.
88
+
89
+
Also verify formatting in the browser and test at multiple screen sizes.
90
+
82
91
## Submitting Changes
83
92
84
93
1.**Create a branch**: `git checkout -b fix/improve-docs`
0 commit comments