@tideworthy/tidysites 0.1.3 → 0.1.4

package/README.md

@@ -28,6 +28,7 @@ nothing else; it lives in `.tidysites/key`, which is kept out of git.
 | `tidysites schema [type or collection]` | the section types and layouts, or one type's or collection's fields |
 | `tidysites gallery [type]` | a screenshot of every section type and layout in this website's theme, or the first screen of one type |
 | `tidysites fetch <url> [--out dir]` | a page of the site being ported: cleaned HTML, its outline (headings, navigation, images, phones, fonts, colours) and its stylesheets |
+| `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 |
 | `tidysites publish --yes` | the live site becomes a copy of the preview site |
 
 A section keeps its type with its key: to replace an intro with a row, give the row its own `_key`
@@ -50,7 +51,7 @@ menus/<name>.json             a menu as a tree: { "label", "items": [{ "label",
 
 A new entry is a new `<collection>/<slug>.json` with at least `"data"`; the
 slug is the file name, the status is `published` unless the file says
-`draft`. Delete a file and `push --prune` removes the entry. A field taken
+`draft`. Delete a file (`tidysites rm services/old-one`, or `services/*` for all) and `push --prune` removes the entry. A field taken
 out of a file is cleared on the website at the next push. `id` and
 `updated_at` are the website's; leave them as pulled. A pull never overwrites
 a file you changed and have not pushed; it keeps the file and the difference

package/bin/tidysites.mjs

@@ -13,6 +13,7 @@
  *   schema [name]                             section types and layouts, or one type's or collection's fields
  *   gallery [type]                            screenshot of every section type in this theme, or the first screen of one type
  *   fetch <url> [--out dir]                   a page of the site being ported: cleaned HTML and its outline
+ *   rm <collection>/<slug> ...                 delete entry files (globs allowed: services/*); push --prune then removes them from the website
  *   publish --yes                             the live site becomes a copy of the preview site
  *
  * The site is the remote: pull, edit, push. A push that would overwrite an
@@ -465,6 +466,32 @@ async function fetchCmd(ctx) {
 	say(`Saved to ${relative(process.cwd(), outDir)}/: ${base}.html (cleaned), ${base}.raw.html, ${base}.outline.json${cssTexts.length ? `, ${cssTexts.length} stylesheet${cssTexts.length === 1 ? '' : 's'}` : ''}`);
 }
 
+/**
+ * Delete entry files inside the folder, with their sidecars, so nobody has to reach for the shell's rm (which a
+ * harness may stop to ask about). Takes collection/slug paths; a trailing * takes every entry of the collection.
+ */
+function rmCmd({ dir }) {
+	if (!positional.length) fail('Usage: tidysites rm <collection>/<slug> [...]   (services/* for every entry of a collection)');
+	let removed = 0;
+	for (const arg of positional) {
+		const m = /^([a-z][a-z0-9_]*)\/(\*|[A-Za-z0-9][A-Za-z0-9_-]*)(?:\.json)?$/.exec(arg.replace(/^\.\//, ''));
+		if (!m) fail(`${arg}: write collection/slug or collection/*`);
+		const [, collection, slug] = m;
+		const colDir = join(dir, collection);
+		if (!existsSync(colDir)) { say(`${collection}/: no such collection folder`); continue; }
+		const slugs = slug === '*' ? readdirSync(colDir).filter((f) => f.endsWith('.json')).map((f) => f.slice(0, -5)) : [slug];
+		for (const sl of slugs) {
+			let hit = false;
+			for (const ext of ['json', ...Object.keys(SIDECARS[collection] ?? SIDECARS.default)]) {
+				const f = join(colDir, `${sl}.${ext}`);
+				if (existsSync(f)) { rmSync(f); hit = true; }
+			}
+			if (hit) { removed++; say(`- ${collection}/${sl}`); } else say(`${collection}/${sl}: no such entry file`);
+		}
+	}
+	say(`${removed} entr${removed === 1 ? 'y' : 'ies'} removed from the folder; \`tidysites push --prune\` removes them from the website.`);
+}
+
 async function publish(ctx) {
 	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`.');
 	const { json, text } = await tool(ctx.cfg, 'publish_website', { site_id: ctx.cfg.site });
@@ -524,6 +551,8 @@ async function main() {
 			return schema(config());
 		case 'fetch':
 			return fetchCmd(config(false));
+		case 'rm':
+			return rmCmd(config());
 		case 'publish':
 			return publish(config());
 		case 'help':

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tideworthy/tidysites",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Pull a Tidysites website to files, edit, validate against its content model, push it back, screenshot the result.",
   "type": "module",
   "bin": {