@tideworthy/tidysites 0.1.8 → 0.1.9
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/README.md +1 -1
- package/bin/tidysites.mjs +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -31,7 +31,7 @@ nothing else; it lives in `.tidysites/key`, which is kept out of git.
|
|
|
31
31
|
| `tidysites gallery [type]` | a screenshot of every section type and layout in this website's theme, or the first screen of one type |
|
|
32
32
|
| `tidysites fetch <url> [--out dir]` | a page of the site being ported: cleaned HTML, its outline (headings, navigation, images, phones, fonts, the stylesheet's own variables and colours) and its stylesheets, inline style blocks included |
|
|
33
33
|
| `tidysites rm <collection>/<slug> ...` | delete entry files with their sidecars (`services/*` for every entry of a collection); `push --prune` then removes them from the website |
|
|
34
|
-
| `tidysites publish --yes` | the live site becomes a copy of the preview site |
|
|
34
|
+
| `tidysites publish --yes` | the live site becomes a copy of the preview site. A website that is live on the client's own domain is never published from the command line: the website refuses and says so; the person publishes it (Publish now on the Website tab), or an assistant with them does through the connector after they confirm |
|
|
35
35
|
|
|
36
36
|
A section keeps its type with its key: to replace an intro with a row, give the row its own `_key`
|
|
37
37
|
(`validate` says so; the website would only say "internal error"). After a push the pushed files take the
|
package/bin/tidysites.mjs
CHANGED
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
* gallery [type] screenshot of every section type in this theme, or the first screen of one type
|
|
17
17
|
* fetch <url> [--out dir] a page of the site being ported: cleaned HTML and its outline
|
|
18
18
|
* rm <collection>/<slug> ... delete entry files (globs allowed: services/*); push --prune then removes them from the website
|
|
19
|
-
* publish --yes the live site becomes a copy of the preview site
|
|
19
|
+
* publish --yes the live site becomes a copy of the preview site (refused for a site live on the client's own domain: the person publishes that)
|
|
20
20
|
*
|
|
21
21
|
* The site is the remote: pull, edit, push. A push that would overwrite an
|
|
22
22
|
* entry changed on the website since the pull is refused until you pull
|
|
@@ -564,6 +564,7 @@ function rmCmd({ dir }) {
|
|
|
564
564
|
|
|
565
565
|
async function publish(ctx) {
|
|
566
566
|
if (!flags.yes) fail('Publishing makes the live site a copy of the preview site. Look at it first (`tidysites shot /`), then run `tidysites publish --yes`.');
|
|
567
|
+
// A website live on the client's own domain is never published from here: the website refuses (409 live_domain) and says who may.
|
|
567
568
|
const { json, text } = await tool(ctx.cfg, 'publish_website', { site_id: ctx.cfg.site });
|
|
568
569
|
say(json ? JSON.stringify(json, null, 2) : text);
|
|
569
570
|
}
|
package/package.json
CHANGED