Easy to use, searchable, cookbook-style library of functions, regular expressions, techniques etc

[myitcv]

Creating a new discussion following an exchange with @kghenderson on Slack:

i wish there was a very easy to use, searchable, cookbook-style library of functions, regular expressions, techniques with tags and comments for cue snippets on the site, ideally tying in to the tests/expected outputs and also tying into unity

fwiw, as reference, i really like the https://www.nushell.sh/ guide that's directly linkable and searchable

[myitcv]

Interesting. Do you have any specific UX that you're after here? Any good links from https://www.nushell.sh/?

For the new content on cuelang.org, we will have how-tos - that's probably the closest in terms of a specific question and answer style.

And the plan is that (with time) all the content on cuelang.org will be tested as part of CI.

Not only that, most examples will (once we add this feature) be interactive in a playground-style experience on cuelang.org.

cc @Lyoness.

[myitcv]

In a follow-up, @kghenderson added:

i wish that the cue playground had: support for tools/packages, sample data sets, as well as being easily indexed/searched with tags & descriptions for more permanent samples - i know that code reuse in modules will be a big deal and helpful, but some such as myself work in restricted environments where importing 3rd party packages can be difficult ... also maybe some way to thread or show alternatives, such as here are a few ways to tackle a particular problem ... i also think it would be helpful to have some sample data sets that could be used in playground for common cases & common understanding, e.g. kubernetes, but also things like tony's music example, financial accounts, service contracts, etc. which could be community submitted and maintained

[myitcv]

which could be community submitted and maintained

A key part of the cuelang.org redesign is that we have a good clear pipeline of how to suggest, add and maintain content, a pipeline that is open to all members of the CUE community.

For more background reading for anyone following along please see the slides from the first docs and content call.