@riverbankcms/sdk 0.7.0 → 0.7.3

package/dist/cli/init-docs/content/workflow-publish.md

@@ -0,0 +1,280 @@
+# Workflow: Publish Content
+
+This workflow guides you through safely publishing content to make it live.
+
+## Understanding Draft vs Published
+
+| Status | Behavior |
+|--------|----------|
+| **Draft** | Content is saved but not visible on the live site. Only visible in preview mode. |
+| **Published** | Content is visible to all site visitors. |
+
+By default, new content is created as a draft.
+
+## Publishing Individual Items
+
+### Publish an Entry
+
+```bash
+riverbankcms entry publish <content-type> <identifier>
+```
+
+**Example:**
+
+```bash
+riverbankcms entry publish blog-post my-first-post
+```
+
+### Publish a Page
+
+```bash
+riverbankcms page publish <identifier>
+```
+
+**Example:**
+
+```bash
+riverbankcms page publish about
+```
+
+## Checking Publication Status
+
+### Check Entry Status
+
+```bash
+riverbankcms entry get <content-type> <identifier>
+```
+
+Look for:
+- `status: "published"` or `status: "draft"`
+- `hasUnpublishedChanges: true/false`
+
+### Check Page Status
+
+```bash
+riverbankcms page get <identifier>
+```
+
+### List All with Status (JSON)
+
+```bash
+# List entries with status
+riverbankcms entry list blog-post --json
+
+# Filter to see status fields (requires jq)
+riverbankcms entry list blog-post --json | jq '.items[] | {identifier, status, hasUnpublishedChanges}'
+
+# List pages with status
+riverbankcms page list --json
+```
+
+## Bulk Publishing via Push
+
+When using `riverbankcms push`, the target status is controlled by your config.
+
+### Configure Auto-Publishing
+
+In `riverbank.config.ts`:
+
+```typescript
+export default defineConfig({
+  siteId: '...',
+  sync: {
+    // Automatically publish pushed content
+    contentTarget: 'publish',
+
+    // Or keep as draft (default)
+    contentTarget: 'draft',
+  },
+});
+```
+
+### Push and Publish
+
+```bash
+# With contentTarget: 'publish', this publishes all pushed content
+riverbankcms push
+```
+
+### Push as Draft Then Publish Selectively
+
+```bash
+# Push as drafts (default behavior)
+riverbankcms push
+
+# Then publish specific items
+riverbankcms entry publish blog-post featured-post
+riverbankcms page publish landing-page
+```
+
+## Unpublishing Content
+
+### Unpublish an Entry
+
+```bash
+riverbankcms entry unpublish <content-type> <identifier>
+```
+
+**Example:**
+
+```bash
+riverbankcms entry unpublish blog-post old-post
+```
+
+### Unpublish a Page
+
+```bash
+riverbankcms page unpublish <identifier>
+```
+
+**Example:**
+
+```bash
+riverbankcms page unpublish outdated-landing
+```
+
+Unpublishing reverts content to draft status. The content is preserved but no longer visible on the live site.
+
+## Safe Publishing Workflow
+
+Follow these steps to safely publish content:
+
+### 1. Pull Latest Content
+
+Ensure you're working with the current state:
+
+```bash
+riverbankcms pull
+```
+
+### 2. Make and Verify Changes
+
+```bash
+# Make changes via CLI or edit local files
+riverbankcms entry upsert blog-post my-post --data '...'
+
+# Or edit content/entries/blog-post.json
+```
+
+### 3. Preview Changes
+
+```bash
+# Preview what would be pushed
+riverbankcms push --dry-run
+
+# Preview specific blocks visually
+riverbankcms preview block.hero --data '...' --open
+```
+
+### 4. Push Changes (as Draft)
+
+```bash
+riverbankcms push
+```
+
+### 5. Verify in CMS Dashboard
+
+- Log into the dashboard
+- Review the content in preview mode
+- Check formatting, images, links
+
+### 6. Publish
+
+```bash
+riverbankcms entry publish blog-post my-post
+# or
+riverbankcms page publish my-page
+```
+
+### 7. Verify Live
+
+- Check the live site
+- Confirm content appears correctly
+- Test any links or interactive elements
+
+## Handling Unpublished Changes
+
+When you edit published content, it stays published but gains pending changes.
+
+### Check for Pending Changes
+
+```bash
+riverbankcms entry get blog-post my-post --json | grep hasUnpublishedChanges
+```
+
+- `hasUnpublishedChanges: true` - There are edits not yet live
+- `hasUnpublishedChanges: false` - Live version is current
+
+### Apply Pending Changes
+
+Re-publish to make pending changes live:
+
+```bash
+riverbankcms entry publish blog-post my-post
+```
+
+### Discard Pending Changes
+
+To revert to the published version, you would need to:
+
+1. Pull the published content: `riverbankcms pull`
+2. The local files will have the current (modified) state
+3. Manually revert in the dashboard or re-push the original content
+
+## Publishing to Production
+
+For production environments, use the `--remote` flag:
+
+```bash
+# Pull from production
+riverbankcms pull --remote
+
+# Preview production push
+riverbankcms push --remote --dry-run
+
+# Push to production (requires --yes for safety)
+riverbankcms push --remote --yes
+
+# Publish specific content on production
+riverbankcms entry publish blog-post my-post --remote
+riverbankcms page publish landing --remote
+```
+
+**Safety notes:**
+- `--remote` targets production environment
+- Push to remote requires `--yes` flag to prevent accidents
+- Always preview with `--dry-run` first
+
+## Publishing Checklist
+
+Before publishing content, verify:
+
+- [ ] Content is accurate and complete
+- [ ] Images load correctly
+- [ ] Links work (internal and external)
+- [ ] SEO metadata is set (title, description)
+- [ ] Mobile layout looks good (if applicable)
+- [ ] No placeholder or test content remains
+- [ ] Spell check / grammar check completed
+
+## Troubleshooting
+
+### Content not appearing on live site
+
+1. Check if published: `riverbankcms entry get <type> <id>`
+2. Look for `status: "published"`
+3. If draft, publish it: `riverbankcms entry publish <type> <id>`
+4. Check for caching - may need to wait or clear cache
+
+### Published but showing old content
+
+1. Check for pending changes: `hasUnpublishedChanges: true`
+2. Re-publish to apply changes: `riverbankcms entry publish <type> <id>`
+3. Clear any CDN or browser cache
+
+### Can't publish - validation error
+
+1. Check required fields are filled
+2. Review the error message for specifics
+3. Get full entry data: `riverbankcms entry get <type> <id> --json`
+4. Fix missing/invalid fields and retry

package/dist/client/bookings.d.mts

@@ -23,6 +23,8 @@ type BookingFormProps = {
     className?: string;
     form?: FormConfig | null;
     services?: Service$2[];
+    /** Server-passed spam protection flag. Falls back to NEXT_PUBLIC_SPAM_PROTECTION_ENABLED. */
+    spamProtectionEnabled?: boolean;
 };
 /**
  * BookingFormClient Component

package/dist/client/bookings.d.ts

@@ -23,6 +23,8 @@ type BookingFormProps = {
     className?: string;
     form?: FormConfig | null;
     services?: Service$2[];
+    /** Server-passed spam protection flag. Falls back to NEXT_PUBLIC_SPAM_PROTECTION_ENABLED. */
+    spamProtectionEnabled?: boolean;
 };
 /**
  * BookingFormClient Component