Add styled landing page intros to AI and context engine docs#3558
Add styled landing page intros to AI and context engine docs#3558mich-elle-luna wants to merge 1 commit into
Conversation
Adds tagline, three clickable cards, "What is X?" and "Why use X?" sections with Redis-palette styling to the Redis for AI, Context Engine, Agent Memory, LangCache, Context Retriever, Data Integration, and Feature Form index pages. Also renames "Agent Memory Server" to "Agent Memory" throughout. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
andy-stark-redis
left a comment
andy-stark-redis
left a comment
There was a problem hiding this comment.
Just a few suggestions but otherwise LGTM - good idea to make them all look consistent like this.
| {{< image-card image="images/ai-LLM-memory.svg" alt="Use cases icon" title="API and SDK Examples — See real-world usage patterns with session events and long-term memory" url="/develop/ai/context-engine/agent-memory/api-examples" >}} | ||
| {{< image-card image="images/ai-brain-2.svg" alt="Python SDK icon" title="Python SDK — Easy integration with tool abstractions for OpenAI and Anthropic" url="/develop/ai/context-engine/agent-memory/api-examples" >}} |
There was a problem hiding this comment.
These two tiles point to the same page. Also, it doesn't really contain any Python SDK examples (although it has a link to the PyPI page where there are some examples). Maybe use a different topic for the card or link directly to the PyPI page? Then again, maybe this is an indication that we do need some Python examples on redis.io.
| <ul class="space-y-1 text-redis-pen-600"> | ||
| <li>Agents reliably follow defined data paths instead of guessing at SQL</li> | ||
| <li>Live, structured context from your business data at every agent step</li> | ||
| <li>No tool zoo sprawl — one model definition, consistent tool surface</li> |
There was a problem hiding this comment.
Although the page intentionally has a slight marketing feel to it, I think "tool zoo sprawl" is a bit flowery! Maybe something like:
| <li>No tool zoo sprawl — one model definition, consistent tool surface</li> | |
| <li>Minimal tool set and single model definition keep things simple</li> |
Feel free to ignore this if "tool zoo sprawl" is in widespread use and it's just me who has never heard of it :-)
|
|
||
| Stream live business data into Redis so agents always work with accurate, up-to-date information. | ||
|
|
||
| Redis Data Integration (RDI) keeps your Redis Cloud database in sync with your existing relational databases using change data capture. Agents query Redis at full speed without ever touching your production databases directly. |
There was a problem hiding this comment.
Link might be helpful for people seeing this stuff for the first time, and defining the abbreviation is appropriate because it gets used later in the page. Also, "touching" might be a bit misleading since you do still have to write to the production databases.
| Redis Data Integration (RDI) keeps your Redis Cloud database in sync with your existing relational databases using change data capture. Agents query Redis at full speed without ever touching your production databases directly. | |
| Redis Data Integration (RDI) keeps your Redis Cloud database in sync with your existing relational databases using [Change data capture](https://en.wikipedia.org/wiki/Change_data_capture) (CDC). Agents query Redis at full speed without ever reading from your production databases directly. |
| ``` | ||
|
|
||
| RDI performs an initial full sync, then captures every subsequent `INSERT`, `UPDATE`, and `DELETE` and applies them to Redis within seconds. See the [RDI quick start]({{< relref "/operate/rc/rdi/quick-start" >}}) to get up and running with a live PostgreSQL source. | ||
|
|
There was a problem hiding this comment.
The stuff that follows is existing text but it seems to repeat what is said in the new intro. Might be useful to do a quick tidy-up on the rest of the page to avoid redundant info.
| See the full [LangCache API and SDK examples]({{< relref "/develop/ai/context-engine/langcache/api-examples" >}}) for more. | ||
|
|
||
| Redis LangCache is a fully-managed semantic caching service that reduces large language model (LLM) costs and improves response times for AI applications. | ||
|
|
There was a problem hiding this comment.
Another situation where the following text looks quite similar to what's already been said in some places.
| </div> | ||
| </div> | ||
|
|
||
| Redis Feature Form helps teams define, manage, materialize, and serve machine learning features while keeping existing data systems in place. In the documented workflow, Redis acts as the low-latency online store for feature serving. |
There was a problem hiding this comment.
Not part of the PR, but maybe just remove this line now?
| Redis Feature Form helps teams define, manage, materialize, and serve machine learning features while keeping existing data systems in place. In the documented workflow, Redis acts as the low-latency online store for feature serving. |
| <div class="p-5 border border-redis-pen-300 rounded-lg"> | ||
| <h3 class="text-redis-ink-900 font-semibold mb-3">For developers</h3> | ||
| <ul class="space-y-1 text-redis-pen-600"> | ||
| <li>Python, JavaScript, Java, Go, and .NET client libraries</li> |
There was a problem hiding this comment.
PHP too, surprisingly :-) Also, maybe best to make it clear that these clients support search specifically (I think only Python/JS support the Iris stuff?)
| <li>Python, JavaScript, Java, Go, and .NET client libraries</li> | |
| <li>Redis Search available in Python, JavaScript, Java, Go, .NET, and PHP client libraries</li> |
2 participants
Adds tagline, three clickable cards, "What is X?" and "Why use X?" sections with Redis-palette styling to the Redis for AI, Context Engine, Agent Memory, LangCache, Context Retriever, Data Integration, and Feature Form index pages.
Note
Low Risk
Documentation-only Hugo/Markdown and styling changes with no application or auth logic affected.
Overview
Adds landing-page style intros to seven Hugo index pages under
develop/ai: Redis for AI and search, Redis Iris context engine, Agent Memory, LangCache, Context Retriever, Data Integration, and Feature Form.Each page now opens with a short tagline, a three-card
image-cardgrid (quick start / examples / related links), then shared “What is …?” and “Why use …?” blocks using Redis palette classes (text-redis-red-500,border-redis-pen-300, two-column benefit cards). Several service pages also add Quick example snippets (REST JSON,ctxctl, or RDI YAML).Copy and metadata tweaks: Context Engine front matter description is shortened; Agent Memory renames Redis Agent Memory overview to Two-tier memory model and refers to the Agent Memory service instead of “Agent Memory Server.” Original deeper sections below the new intros are largely retained, so some pages repeat overview text after the new blocks.
Reviewed by Cursor Bugbot for commit c159a93. Bugbot is set up for automated code reviews on this repo. Configure here.