Add comprehensive integration tiles and standardize chile page structure #2165
Conversation
- 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
| - **High Availability**: Built-in clustering and automatic failover | ||
| - **Advanced Security**: Role-based access control and encryption | ||
| - **Monitoring Dashboard**: Web-based management interface | ||
| - **Module Support**: Redis modules like RedisJSON, RediSearch, and RedisTimeSeries |
There was a problem hiding this comment.
I'm not sure how RS is handling the notion of modules these days. That said, maybe change this to:
| - **Module Support**: Redis modules like RedisJSON, RediSearch, and RedisTimeSeries | |
| - **Advanced capability support**: JSON, time series, and probabilistic data structures, and Redis Query Engine. |
Co-authored-by: David Dougherty <[email protected]>
Co-authored-by: David Dougherty <[email protected]>
Co-authored-by: David Dougherty <[email protected]>
Co-authored-by: David Dougherty <[email protected]>
Co-authored-by: David Dougherty <[email protected]>
| @@ -0,0 +1,38 @@ | |||
| --- | |||
There was a problem hiding this comment.
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?)
| @@ -0,0 +1,38 @@ | |||
| --- | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,38 @@ | |||
| --- | |||
There was a problem hiding this comment.
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 @@ | |||
| --- | |||
| LinkTitle: php-redis | |||
There was a problem hiding this comment.
| LinkTitle: php-redis | |
| LinkTitle: predis |
| description: Learn how to build with Redis and PHP | ||
| group: library | ||
| stack: true | ||
| summary: PhpRedis is a PHP extension for Redis. |
There was a problem hiding this comment.
| summary: PhpRedis is a PHP extension for Redis. | |
| summary: Predis is a PHP client for Redis. |
| - **Predis (Recommended)**: Pure PHP implementation, easy Composer installation, framework integration | ||
| - **PhpRedis**: High-performance C extension for maximum speed and efficiency |
There was a problem hiding this comment.
| - **Predis (Recommended)**: Pure PHP implementation, easy Composer installation, framework integration | |
| - **PhpRedis**: High-performance C extension for maximum speed and efficiency | |
| - **Pure PHP implementation**: easy Composer installation, framework integration |
|
|
||
| ## Getting Started | ||
|
|
||
| Refer to the complete [PHP guide]({{< relref "/develop/clients/php" >}}) to install, connect, and use PHP Redis clients with detailed examples and framework integration guides. |
There was a problem hiding this comment.
| Refer to the complete [PHP guide]({{< relref "/develop/clients/php" >}}) to install, connect, and use PHP Redis clients with detailed examples and framework integration guides. | |
| Refer to the complete [Predis guide]({{< relref "/develop/clients/php" >}}) to install, connect, and use PHP Redis clients with detailed examples and framework integration guides. |
|
|
||
| ## Overview | ||
|
|
||
| redis-py is the most popular Python client for Redis, providing a comprehensive interface for all Redis commands and features. It offers both synchronous and asynchronous APIs, making it suitable for a wide range of Python applications from simple scripts to high-performance web applications. |
There was a problem hiding this comment.
It is the most popular but we recommend it because it's our own library.
| redis-py is the most popular Python client for Redis, providing a comprehensive interface for all Redis commands and features. It offers both synchronous and asynchronous APIs, making it suitable for a wide range of Python applications from simple scripts to high-performance web applications. | |
| redis-py is the recommended Python client for Redis, providing a comprehensive interface for all Redis commands and features. It offers both synchronous and asynchronous APIs, making it suitable for a wide range of Python applications from simple scripts to high-performance web applications. |
| @@ -0,0 +1,38 @@ | |||
| --- | |||
There was a problem hiding this comment.
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.
| @@ -0,0 +1,38 @@ | |||
| --- | |||
There was a problem hiding this comment.
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.
Add 16 new integration tiles for client libraries and platforms to connect things and align with the redis.io home page listing:
Standardize all integration pages with consistent structure:
Improve page content to prevent footer overlap issues: