Skip to content

Conversation

@mich-elle-luna
Copy link
Collaborator

  • Add 16 new integration tiles for client libraries and platforms to connect things and align with the redis.io home page listing:

    • Client libraries: Go, PHP, C (hiredis), C++ (Boost.Redis), Ruby, Dart, Rust
    • Cloud providers: AWS, Azure, Google Cloud with Redis Cloud quickstart links
    • Platforms: Vercel, Heroku, Kubernetes, Docker (Enterprise & Open Source)
    • AI/ML: LangChain integration for vector search and AI applications
  • Standardize all integration pages with consistent structure:

    • Overview section explaining the integration purpose
    • Key Features section with 8 bullet points highlighting capabilities
    • Getting Started section with links to detailed documentation
  • Improve page content to prevent footer overlap issues:

    • All pages now have sufficient content length for proper navigation display

- Add 16 new integration tiles for missing client libraries and platforms:
  * Client libraries: Go, PHP, C (hiredis), C++ (Boost.Redis), Ruby, Dart, Rust
  * Cloud providers: AWS, Azure, Google Cloud with Redis Cloud quickstart links
  * Platforms: Vercel, Heroku, Kubernetes, Docker (Enterprise & Open Source)
  * AI/ML: LangChain integration for vector search and AI applications

- Standardize all integration pages with consistent structure:
  * Overview section explaining the integration purpose
  * Key Features section with 8 bullet points highlighting capabilities
  * Getting Started section with links to detailed documentation

- Update existing pages to new structure:
  * RedisVL: Add comprehensive AI/vector database content
  * redis-py: Add Python client features and framework integration
  * NRedisStack: Add .NET/C# client with Redis Stack module support
  * RedisInsight: Convert to proper image-card shortcode with reduced width

- Improve page content to prevent footer overlap issues:
  * All pages now have sufficient content length for proper navigation display
  * Consistent professional appearance across all integration pages
  * Better user experience with comprehensive information before linking to guides

- Technical improvements:
  * Use proper Hugo shortcodes for clickable images and cards
  * Consistent weight-based ordering for logical grouping
  * Proper categorization and metadata for all integration types
@github-actions
Copy link
Contributor

github-actions bot commented Sep 23, 2025

DOC-5756

@mich-elle-luna mich-elle-luna requested a review from a team September 23, 2025 21:36
Copy link
Collaborator

@dwdougherty dwdougherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments mostly around the use of Redis Stack.

Other folks should review "their" sections as well.

Copy link
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might be OK having tiles for the community-supported clients (whatever you feel is best) but I think the PHP tile is a bit unclear as it stands. Otherwise, good update to the page :-)

@@ -0,0 +1,38 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a community-supported client. We list it on our clients page as our recommendation, but I'm not sure we should have a tile each for these (we don't control them, so perhaps best not to make any firm claims about them?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@@ -0,0 +1,38 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Community-supported again. Text looks OK, but I don't know if we should be claiming anything about what it can do or how it works.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@@ -0,0 +1,38 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is a bit confused :-) Predis is the one we recommend and is semi-supported (we don't strictly control it, but we work closely with the developer, make contributions, and provide quite a bit of documentation). PhpRedis is community-supported and we don't have any special relationship with it. The main reason we list PhpRedis as an alternative is that it probably has better performance for some tasks.

@@ -0,0 +1,38 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the strangest one - we don't control it or document it but for some reason, it is in the Redis org on Github. Another one that probably shouldn't have a tile.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed, thanks!

@@ -0,0 +1,38 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mirko has just confirmed that this one now has the same status as Predis (we don't control it but we've "adopted" it). The text below looks OK for now, but I'll add a landing page for Rust and update the link in this tile when it's ready.

mich-elle-luna and others added 10 commits September 25, 2025 09:21
- Remove boost-redis integration tile (C++ client)
- Remove dart-redis integration tile (Dart client)
- Remove ruby-redis integration tile (Ruby client)

This reduces the integration page to focus on the most commonly used client libraries while maintaining comprehensive coverage of cloud providers, platforms, and AI/ML integrations.
Copy link
Contributor

@cmilesb cmilesb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not entirely sure why we need an integration page for all of the Cloud vendor options. I don't think it makes sense to have them when we have the Supported Cloud regions page in the Redis Cloud docs. If you really think they're necessary, I marked a bunch of places where the info in them is straight-out wrong or could be worded better.

The Heroku and Vercel stuff looks good, I'd keep those pages - but I don't see any use for each Cloud Vendor integration page.


## Getting Started

Get started with [Redis Cloud]({{< relref "/operate/rc/rc-quickstart" >}}) on Azure to create and manage your Redis databases.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add something about AMR here, since Azure is only available on Essentials.


## Key Features

- **GCP Integration**: Native integration with Google Cloud VPC and services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line.

- **GCP Integration**: Native integration with Google Cloud VPC and services
- **Private Service Connect**: Secure, private connectivity within Google Cloud
- **Global Network**: Deploy across Google's worldwide network of regions
- **AI/ML Integration**: Optimized for Google Cloud AI and machine learning workloads
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line as well.

- **Private Service Connect**: Secure, private connectivity within Google Cloud
- **Global Network**: Deploy across Google's worldwide network of regions
- **AI/ML Integration**: Optimized for Google Cloud AI and machine learning workloads
- **BigQuery Integration**: Seamless data pipeline integration with BigQuery
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also remove this line.

## Key Features

- **Azure Integration**: Native integration with Azure Virtual Networks and services
- **Private Endpoints**: Secure, private connectivity without internet exposure
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is available on all Cloud vendors, I'd remove it here.

- **Azure Integration**: Native integration with Azure Virtual Networks and services
- **Private Endpoints**: Secure, private connectivity without internet exposure
- **Multi-region Deployment**: High availability across Azure regions and availability zones
- **Azure Marketplace**: Simplified procurement and billing through Azure
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line, unless talking about AMR.

- **Private Endpoints**: Secure, private connectivity without internet exposure
- **Multi-region Deployment**: High availability across Azure regions and availability zones
- **Azure Marketplace**: Simplified procurement and billing through Azure
- **Enterprise Security**: Azure AD integration, encryption, and compliance certifications
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line.

- **Azure Marketplace**: Simplified procurement and billing through Azure
- **Enterprise Security**: Azure AD integration, encryption, and compliance certifications
- **Auto-scaling**: Automatic scaling based on demand and usage patterns
- **Azure Monitor**: Integration with Azure monitoring and alerting services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line, unless talking about AMR specifically.

- **Enterprise Security**: Azure AD integration, encryption, and compliance certifications
- **Auto-scaling**: Automatic scaling based on demand and usage patterns
- **Azure Monitor**: Integration with Azure monitoring and alerting services
- **Hybrid Cloud**: Seamless integration with on-premises and multi-cloud architectures
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove this line. I am not super-familiar with the AMR offering, but even then I'm pretty sure we don't offer any Hybrid Cloud stuff with Redis Cloud.

@mich-elle-luna
Copy link
Collaborator Author

@cmilesb Yeah, I'm adding these because the redis.io home page lists them as integrations and links to the integrations page, so I want folks coming from the redis.io home page to find them--I didn't notice the Supported regions page in redis cloud docs, but that is a bit different than what we need for folks coming from the home page if that makes sense.

Copy link
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

RC: Add Heroku mention to RC docs
Copy link
Collaborator

@dwdougherty dwdougherty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one additional comment (remove mention of modules from the Go page). I'll go ahead and approve.

@mich-elle-luna mich-elle-luna merged commit b109ff4 into main Sep 29, 2025
7 checks passed
@mich-elle-luna mich-elle-luna deleted the DOC-5756 branch September 29, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants