uniweb 0.33.1 → 0.34.1
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 +7 -7
- package/partials/agents.md +73 -38
- package/src/backend/client.js +122 -35
- package/src/backend/site-sync.js +42 -43
- package/src/commands/build.js +17 -17
- package/src/commands/clone.js +7 -7
- package/src/commands/content.js +2 -3
- package/src/commands/doctor.js +34 -10
- package/src/commands/i18n.js +53 -39
- package/src/commands/publish.js +39 -15
- package/src/commands/pull.js +26 -25
- package/src/commands/push.js +24 -14
- package/src/commands/validate.js +1 -1
- package/src/framework-index.json +16 -9
- package/src/index.js +39 -4
- package/src/utils/flag-guard.js +2 -2
- package/src/utils/git.js +8 -2
- package/src/utils/records-guard.js +80 -0
- package/src/utils/schemaless-report.js +4 -4
- package/src/utils/site-data-upload.js +2 -2
- package/src/utils/site-identity.js +65 -2
- package/templates/site/site.yml.hbs +24 -6
|
@@ -25,20 +25,38 @@ index: home
|
|
|
25
25
|
# pages/docs: ../../../docs # Mount docs repo at /docs route
|
|
26
26
|
# pages/blog: ../../blog-content # Mount blog content at /blog route
|
|
27
27
|
# layout: ./custom-layout # Custom layout directory
|
|
28
|
-
#
|
|
28
|
+
# entities: ./data # Where this site's entities live
|
|
29
29
|
#
|
|
30
30
|
# To give a mounted route a layout or a title, add a local folder for it
|
|
31
31
|
# (pages/docs/) holding a folder.yml — folder.yml, not page.yml, because the
|
|
32
32
|
# mounted directory is a folder of pages. Whatever that stub leaves unset comes
|
|
33
33
|
# from the mounted directory's own folder.yml, so it need only say what differs.
|
|
34
34
|
|
|
35
|
-
# ───
|
|
36
|
-
#
|
|
37
|
-
# Pages and sections reference sources by name via `data: source-name`.
|
|
35
|
+
# ─── Structured Content ───────────────────────────────────────────────────────
|
|
36
|
+
# Three things, and they are separate on purpose:
|
|
38
37
|
#
|
|
39
|
-
#
|
|
38
|
+
# entities/{schema}/ your stored records. The folder names their data schema:
|
|
39
|
+
# entities/article/ → @/article (your foundation's)
|
|
40
|
+
# entities/std/person/ → @std/person
|
|
41
|
+
# records.yml WHAT IS PUBLISHED. Listing an entity here is what makes it
|
|
42
|
+
# a record; anything you leave out is a draft. Usually three
|
|
43
|
+
# lines:
|
|
44
|
+
# - article/*.md
|
|
45
|
+
# - person/*.md
|
|
46
|
+
# queries.yml HOW CONTENT IS REACHED — named queries over those records:
|
|
47
|
+
# recent:
|
|
48
|
+
# schema: '@/article'
|
|
49
|
+
# sort: date desc
|
|
50
|
+
# limit: 10
|
|
51
|
+
#
|
|
52
|
+
# Pages and sections then name a query: `data: recent`, or
|
|
53
|
+
# `fetch: { query: recent }`.
|
|
54
|
+
#
|
|
55
|
+
# You can also keep queries here instead of in queries.yml:
|
|
56
|
+
#
|
|
57
|
+
# queries:
|
|
40
58
|
# articles:
|
|
41
|
-
#
|
|
59
|
+
# schema: '@/article'
|
|
42
60
|
# sort: date desc # Sort by frontmatter field
|
|
43
61
|
#
|
|
44
62
|
# fetch:
|