uniweb 1.25.6 → 1.25.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "uniweb",
|
|
3
|
-
"version": "1.25.
|
|
3
|
+
"version": "1.25.7",
|
|
4
4
|
"description": "Create structured Vite + React sites with content/code separation",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -41,15 +41,15 @@
|
|
|
41
41
|
"js-yaml": "^4.3.2",
|
|
42
42
|
"prompts": "^2.4.2",
|
|
43
43
|
"tar": "^7.5.21",
|
|
44
|
-
"@uniweb/core": "~1.6.1",
|
|
45
|
-
"@uniweb/semantic-parser": "~1.13.2",
|
|
46
44
|
"@uniweb/schemas": "~1.6.7",
|
|
47
|
-
"@uniweb/content-writer": "~1.3.1"
|
|
45
|
+
"@uniweb/content-writer": "~1.3.1",
|
|
46
|
+
"@uniweb/core": "~1.6.1",
|
|
47
|
+
"@uniweb/semantic-parser": "~1.13.2"
|
|
48
48
|
},
|
|
49
49
|
"peerDependencies": {
|
|
50
|
-
"@uniweb/build": "~1.14.3",
|
|
51
50
|
"@uniweb/semantic-parser": "~1.13.2",
|
|
52
|
-
"@uniweb/content-reader": "~1.5.8"
|
|
51
|
+
"@uniweb/content-reader": "~1.5.8",
|
|
52
|
+
"@uniweb/build": "~1.14.3"
|
|
53
53
|
},
|
|
54
54
|
"peerDependenciesMeta": {
|
|
55
55
|
"@uniweb/build": {
|
|
@@ -162,7 +162,7 @@ Three uses by info string: `yaml:`/`json:` data (parsed into `content.data.tag`,
|
|
|
162
162
|
|
|
163
163
|
Two tags, not a tag plus a variant: a warning and a note are `md:warning` and `md:note`. The fence takes no params.
|
|
164
164
|
|
|
165
|
-
A ` ```mermaid ` fence is a snippet that a foundation can draw as a diagram, with kit's `Mermaid` (foundation guide). Where it doesn't, or the diagram has a syntax error, the page shows it as code. Check by looking at the page: the build says nothing either way. ` ```mermaid:flow ` keeps the text at `content.data.flow`, for a section that declares `flow` and draws it.
|
|
165
|
+
A ` ```mermaid ` fence is a snippet that a foundation can draw as a diagram, with kit's `Mermaid` (foundation guide). Where it doesn't, or the diagram has a syntax error, the page shows it as code. Check by looking at the page: the build says nothing either way. ` ```mermaid:flow ` keeps the text at `content.data.flow`, for a section that declares `flow` and draws it. Leave colors out of a diagram and it takes the site's, in light and dark; a `fill` you set stays in both, and a pale one leaves its labels unreadable on a dark page.
|
|
166
166
|
|
|
167
167
|
### Math
|
|
168
168
|
|
|
@@ -56,6 +56,8 @@ With `provider: endpoint`, `endpoint:` is **required** (no default): `_search` r
|
|
|
56
56
|
|
|
57
57
|
**Results have one shape.** Always: `id`, `type` (`page` | `section` | `record`), `route`, `href`, `title`, `pageTitle`, `excerpt`, `snippetHtml`. Provider-optional (`null` when absent): `sectionId`, `anchor`, `description`, `component`, `snippetText`, `matches`, `group`, `item` (a record's fields). Guard optionals (`result.item?.image`). `snippetHtml` is HTML with `<mark>` — render through `SafeHtml`. A failing provider falls back to the local index when one exists, else returns no results with a console warning.
|
|
58
58
|
|
|
59
|
+
**Follow a result with `<Link to={result.href}>`.** `href` is a route with no language or base path in it, and `Link` adds both. Do the same for Enter by clicking the highlighted link: `window.location.href = result.href` or a bare `navigate(result.href)` sends a French reader to the English page, and the build says nothing. Where no `Link` can go, `resolveHref(href, website)` gives the whole address.
|
|
60
|
+
|
|
59
61
|
```jsx
|
|
60
62
|
const { results, isLoading, query, isEnabled } = useSearch(website) // `query` is a debounced function
|
|
61
63
|
```
|
|
@@ -109,7 +111,7 @@ The endpoint must accept the framework's batched `{ "events": [ … ] }` POST (`
|
|
|
109
111
|
**A `scripts` entry is a URL and nothing else, so these can't be installed that way.** Each one's install runs inline lines; from a URL alone GA sends nothing and Tag Manager never gets its page-load event. A tag carrying an attribute the vendor reads (`data-domain`, `data-website-id`) has the same problem. What works depends on who builds the pages:
|
|
110
112
|
|
|
111
113
|
- **The framework builds them** (`uniweb export`, `uniweb deploy --host=<adapter>`): the vendor's snippet goes in `head.html` next to `site.yml`, and the build adds it to every page's `<head>`. A `services.google` entry does nothing here.
|
|
112
|
-
- **Uniweb Cloud builds them** (`uniweb publish
|
|
114
|
+
- **Uniweb Cloud builds them** (`uniweb publish`, or publishing from the app): `head.html` is kept and synced but **not applied**. For Google's two, name the ID and the host loads the tag from the next publish, free, with no code, on any foundation:
|
|
113
115
|
|
|
114
116
|
```yaml
|
|
115
117
|
services:
|
|
@@ -117,7 +119,7 @@ The endpoint must accept the framework's batched `{ "events": [ … ] }` POST (`
|
|
|
117
119
|
id: G-XXXXXXXXXX # or GTM-XXXXXXX, or a list of both
|
|
118
120
|
```
|
|
119
121
|
|
|
120
|
-
|
|
122
|
+
Someone who edits only in the app adds it there, with no terminal: the *Google Analytics and Tag Manager* card in the site's Settings, under Features, then a publish. It is this same entry: `uniweb pull` writes what the card holds into `site.yml`, its switch as `enabled: false`. Leave `services.tracking.scripts` unset beside it — a site's own list replaces what the host states, so Google's tag would not load. `tracking: { enabled: false, consent: required }` beside it holds the tag until a visitor answers, and needs a component using `useTrackingConsent()`, or it never loads. Gate that component on the hook's `status`: `isTrackingEnabled()` is false here. Any other such vendor has to run from the foundation's code, so a site whose foundation you can't change can't add one — say so rather than writing a `head.html` that does nothing.
|
|
121
123
|
|
|
122
124
|
Either way, tell the person to check Realtime from a browser that doesn't block trackers: a visit from Brave, say, never reaches Google, which looks like a failed install. Google Analytics counts each page a visitor moves to through the browser-history setting, under Enhanced measurement in the data stream's settings, which a new stream has on.
|
|
123
125
|
|
package/src/framework-index.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
|
-
"generatedAt": "2026-11-
|
|
3
|
+
"generatedAt": "2026-11-02T20:25:11.171Z",
|
|
4
4
|
"packages": {
|
|
5
5
|
"@uniweb/api": {
|
|
6
6
|
"version": "1.6.9"
|
|
@@ -54,13 +54,13 @@
|
|
|
54
54
|
"version": "1.1.2"
|
|
55
55
|
},
|
|
56
56
|
"@uniweb/templates": {
|
|
57
|
-
"version": "1.2.
|
|
57
|
+
"version": "1.2.4"
|
|
58
58
|
},
|
|
59
59
|
"@uniweb/theming": {
|
|
60
60
|
"version": "1.2.1"
|
|
61
61
|
},
|
|
62
62
|
"@uniweb/unipress": {
|
|
63
|
-
"version": "1.1.
|
|
63
|
+
"version": "1.1.31"
|
|
64
64
|
}
|
|
65
65
|
},
|
|
66
66
|
"templates": {
|