Oleg Isonen
f1c3abf1be
## Outcome
Refresh the accessible low-resolution Builder documentation screenshots
with current, native 2× light and dark captures. Images retain useful
crops, descriptive alt text, and explicit display widths.
The final audit accounts for 165 candidate files: 132 refreshed, 29
inaccessible screenshots kept with the user's approval, two existing
images made 2× by setting their display width, and two Content Engine
query screenshots held because the current Builder shows a false
draft-filter type warning. Those two originals remain in place pending a
separate Builder fix and recapture. Four animated GIFs remain outside
this still-screenshot refresh.
## Review checklist
- [x] Inventory image references, native dimensions, display widths, UI
states, and source pages; audit omitted references across all docs.
- [x] Replace the approved Form pairs and accessible Builder screenshots
with matching 2× light and dark captures.
- [x] Keep inaccessible external/account/desktop and disabled Export
images, as approved.
- [x] Review size-sufficient images and GIF/diagram exclusions.
- [x] Review crops, alt text, widths, links, and source references.
Independent screenshot review passed.
- [x] Check the full docs image inventory: 322 placements, 284 unique
assets, zero missing files. The only unaccounted sub-2× refs are four
excluded GIFs.
- [x] Run `git diff --check` and verify all 204 changed image files are
referenced; 117 changed picture placements have matching themes and at
least 2× native width.
- [x] Verify required PR checks: Lint PR, Check submodules, Visual
regression, and Main workflow all passed at 14937127db.
- [ ] Recapture the two Content Engine query images after [Builder fix
#6597](https://github.com/webstudio-is/webstudio/pull/6597) reaches the
Builder used for capture. Keep their originals until then.\n- [ ]
Confirm GitBook rendering at intended CSS widths after publication. This
repository has no PR preview.
## Held images
`content-engine-overview-query.png` and
`content-engine-article-query.png` are unchanged. The current Builder's
query form reports a false type warning for the Boolean
`properties.draft` filter. Screenshotting that state would teach a
broken workflow. The user approved a separate [Builder query type fix in
PR #6597](https://github.com/webstudio-is/webstudio/pull/6597). Once
that fix is reviewed, the two screenshots can be recaptured from the
corrected UI. This PR does not change application code.
All captures use synthetic content. No release or publication branch is
changed.
2.2 KiB
description
| description |
|---|
| The XML Node is used to create an XML document, such as a sitemap. |
📘 XML Node
{% hint style="info" %} Webstudio automatically generates a sitemap for static pages such as Home and About. If you are integrating with a CMS, you can use this component to create a sitemap for CMS data. {% endhint %}
The component appears when Document type is XML
How to use the XML Node component
-
Go to Page Settings > Document Type and select XML from the dropdown
-
Go to Components > XML and add XML Node (this component won’t show until Step 1 is completed)
-
Set the tag and text content (e.g., “loc” and “https://example.com)
Tips
- XML Nodes can be nested within each other
- Use Collection to iterate over a list of data
- A sitemap skeleton is available in the Marketplace
Include the static sitemap
While you can use the autogenerated sitemap for static pages and create a separate sitemap for dynamic pages, you can also combine the two.
To include the static sitemap data in your custom sitemap, follow these steps:
-
Create a page
-
In the page settings, set the Document Type to XML
-
Set the page path to /sitemap.xml. This will override the default sitemap.
-
In Settings > Variables, add a variable and choose Sitemap resource in the New variable dialog.
-
Use a Collection to iterate over the static sitemap data
Related
- XML Time – ISO date formatting for feeds
- Collection – Iterate over feed items
- Head Slot – Add meta tags