DOC-6216 code example progression attribute

[andy-stark-redis]

A test example for adding a loose order of progression among the code examples in a page (effectively forms a simple dependency graph), which appears to be very beneficial for AI tools. The main thing to check out is the buildsUpon attribute in the {{< client-example >}} shortcodes. Adding these to the existing examples would be a one-off job and then future examples should get suggestions for buildsUpon from autocomplete, or else be easily added as a batch by Augie (which is how I added them for this test page).

It seems a useful feature without too much maintenance burden. If we're OK with it then I'll go ahead and add the buildsUpon attributes to the rest of the examples.

[github-actions]

DOC-6216

[github-actions]

Staging links:
https://redis.io/docs/staging/DOC-6216-code-example-progression/develop/data-types/lists/

[dwdougherty]

Am I correct in saying that there's no visible element for this PR? I took a peak in Chrome devtools, but I didn't see anything. That said, I'm wasn't exactly sure what I was looking for.

[andy-stark-redis]

Am I correct in saying that there's no visible element for this PR? I took a peak in Chrome devtools, but I didn't see anything. That said, I'm wasn't exactly sure what I was looking for.

@dwdougherty Correct, yes - the links between the examples are just done with id attributes in the page, etc. The main issue is really whether the extra parameters in the {{< clients-example >}} are going to be a pain.

[dwdougherty]

IMHO, the shortcode is starting to become a bit unwieldy, but if we continue to lean on AI for example generation, which I haven't had a lot of success doing thus far, then maybe it's not so bad. A politician's answer to be sure.

[andy-stark-redis]

@dwdougherty Yeah, perhaps we'd better not add any more to the shortcode. Anyway, thanks for the review :-)