Improve the description of SetSiteOptionsStep

[juanmaguitar]

On page https://wordpress.github.io/wordpress-playground/blueprints-api/steps/#SetSiteOptionsStep

This is equivalent to calling update_option

Add a link to https://developer.wordpress.org/reference/functions/update_option/ on update_option

options (Record) – The options to set on the site.

Add a link to the list of options that could be set in this step on "The options"

[ironnysh]

Great suggestion, @juanmaguitar.

I wonder if it'll make sense to add references to the Developer docs in other relevant steps as well. Basically anything that isn't SQL or file system :-)

[adamziel]

Yes it would @ironnysh, great idea!

[ironnysh]

Coolio!

Cross-referencing additional developer-related improvements to the docs:

• Reorganize the chapters
• Revise the Contributing chapter
• wp-now Docs
• Misc

[ironnysh]

Hmm, so I hit a blocker:
The steps descriptions are provided in multiple typescript files found in this directory.
That's not a problem, except they are written as code comments that are parsed here (I think 🙂).
Adding (HTML or markdown) links to the text of the comments has no effect on the generated content. Only code markup is currently supported.
What's the best way to handle this, @adamziel?

[adamziel]

@ironnysh ah, bummer. Hm, proceed as if Markdown was supported and I'll make that happen :-)

[ironnysh]

Magic! :-)) So, just to make sure, when you say

proceed as if Markdown was supported

You mean this?

/**
 * Sets site options. This is equivalent to calling [`update_option`](https://developer.wordpress.org/reference/functions/update_option/) for each
 * option in the [`options`]( https://developer.wordpress.org/apis/options/#available-options-by-category) object.
 */

Added [word](url) markdown links to the comment in site-data.ts)

[adamziel]

Yup!