bunki 0.18.0 → 0.18.5

package/README.md

@@ -541,6 +541,54 @@ This is useful for:
 - Testing uploads for specific years
 - Managing large image collections across multiple uploads
 
+#### `--content-assets`
+
+Upload images that are co-located with markdown files instead of the top-level `assets/` directory.
+
+When content is organized with images living alongside the markdown:
+
+```
+content/
+├── 2024/
+│   └── _assets/
+│       ├── paris-cafe.webp
+│       └── eiffel-tower.webp
+└── 2025/
+    └── _assets/
+        └── tokyo-ramen.webp
+```
+
+Run:
+
+```bash
+bunki images:push --content-assets
+```
+
+This uploads each file with the S3 key `{year}/{filename}` — the `_assets/` segment is stripped. For example, `content/2024/_assets/paris-cafe.webp` becomes key `2024/paris-cafe.webp`, accessible at `https://cdn.example.com/2024/paris-cafe.webp`.
+
+> [!IMPORTANT]
+> Always use CDN URLs in your markdown, not relative `_assets/` paths. Relative paths cause the image files to be bundled into your Cloudflare Workers deployment instead of served from R2.
+
+```markdown
+<!-- ❌ Causes image to be bundled into Workers -->
+![Paris](../2024/_assets/paris-cafe.webp)
+
+<!-- ✅ Served from R2 CDN -->
+![Paris](https://cdn.example.com/2024/paris-cafe.webp)
+```
+
+#### `--content-assets-dir <dir>`
+
+Override the assets subdirectory name. Defaults to `_assets` (or `contentAssets.assetsDir` in `bunki.config.ts`).
+
+```bash
+# Use _images instead of _assets
+bunki images:push --content-assets --content-assets-dir _images
+
+# Use any custom name
+bunki images:push --content-assets --content-assets-dir media
+```
+
 ### Complete Examples
 
 #### Cloudflare R2 Setup
@@ -746,6 +794,56 @@ Ensure all required environment variables are set. Check `bunki.config.ts` and y
 
 ### Advanced Configuration
 
+#### Content Assets Configuration
+
+Configure co-located content assets in `bunki.config.ts`:
+
+```typescript
+import { SiteConfig } from "bunki";
+
+export default (): SiteConfig => ({
+  title: "My Blog",
+  baseUrl: "https://example.com",
+  domain: "example.com",
+
+  // Default S3 config (used by bunki images:push)
+  s3: {
+    accessKeyId: process.env.S3_ACCESS_KEY_ID || "",
+    secretAccessKey: process.env.S3_SECRET_ACCESS_KEY || "",
+    bucket: "my-site-assets",
+    endpoint: process.env.S3_ENDPOINT,
+    region: "auto",
+    publicUrl: "https://assets.example.com",
+  },
+
+  // Content assets: images stored alongside markdown in content/{year}/_images/
+  contentAssets: {
+    // Directory name within content/{year}/ (default: "_assets")
+    assetsDir: "_images",
+
+    // Optional: use a separate R2 bucket for content assets
+    s3: {
+      accessKeyId: process.env.IMG_ACCESS_KEY_ID || "",
+      secretAccessKey: process.env.IMG_SECRET_ACCESS_KEY || "",
+      bucket: "my-blog-images",
+      endpoint: process.env.S3_ENDPOINT,
+      region: "auto",
+      publicUrl: "https://img.example.com",
+    },
+  },
+});
+```
+
+Then upload content assets:
+
+```bash
+# Uses contentAssets.assetsDir and contentAssets.s3 from config
+bunki images:push --content-assets
+
+# Override the directory name at the CLI level
+bunki images:push --content-assets --content-assets-dir _media
+```
+
 #### Custom Domain per Bucket
 
 If you have multiple S3 buckets with different custom domains:
@@ -806,10 +904,12 @@ Bunki supports incremental builds for significantly faster rebuild times during
 ### Performance Impact
 
 **Large site example (455 posts):**
+
 - Full build: 3,128ms
 - Incremental build (no changes): 985ms (**3.2x faster**)
 
 **Speedup breakdown:**
+
 - Markdown parsing: 1,202ms → 55ms (**22x faster**)
 - CSS processing: 1,024ms → 1ms (**1024x faster**)
 - Overall: **68% faster builds**
@@ -873,11 +973,13 @@ echo ".bunki-cache.json" >> .gitignore
 ### When to Use
 
 **Recommended for:**
+
 - Large sites (100+ posts)
 - Development workflow with frequent rebuilds
 - Sites with slow CSS processing (Tailwind, PostCSS)
 
 **Not needed for:**
+
 - Small sites (<50 posts) - already fast enough
 - CI/CD builds - prefer clean full builds
 - Production deployments - always use full builds
@@ -912,6 +1014,7 @@ Version 2.0.0 cache structure:
 ### Future Optimizations
 
 Current implementation (v0.18.0) optimizes parsing and CSS processing. Future versions may add:
+
 - Selective page regeneration (only rebuild changed posts)
 - Incremental sitemap/RSS updates
 - Smart index page regeneration
@@ -1092,7 +1195,20 @@ bunki/
 
 ## Changelog
 
-### v0.18.0 (Current)
+### v0.18.1 (Current)
+
+- **Page Generation Optimization**: Cache JSON-LD schemas and metadata during initialization
+  - Eliminates 910 redundant operations per build (455 posts × 2)
+  - `extractFirstImageUrl()` called once during initialization, cached in `post.image`
+  - Word count calculated once, cached in `post.wordCount`
+  - JSON-LD schemas pre-generated and cached in `post.jsonLd`
+  - Removed duplicate schema generation from page and feed generators
+- **Deployment Optimization**: All deploy commands now use incremental builds by default
+  - `deploy:all` now builds incrementally for faster deployments
+  - Individual site deployments also use incremental builds
+  - Full builds available via `build:full` when needed
+
+### v0.18.0
 
 - **Incremental Builds**: Smart caching for 3.2x faster development builds
   - File change detection using content hashing and modification times

package/dist/cli/commands/images-push.d.ts

@@ -7,9 +7,11 @@ interface ImagesPushDeps {
 }
 export declare function handleImagesPushCommand(options: {
     domain?: string;
-    images: string;
+    images?: string;
     outputJson?: string;
     minYear?: string;
+    contentAssets?: boolean;
+    contentAssetsDir?: string;
 }, deps?: ImagesPushDeps): Promise<void>;
 export declare function registerImagesPushCommand(program: Command): Command;
 export {};

package/dist/cli/commands/validate-media.d.ts

@@ -0,0 +1,9 @@
+import { Command } from "commander";
+export declare function handleValidateMediaCommand(options: {
+    contentDir?: string;
+    fix?: boolean;
+}, deps?: {
+    logger: Console;
+    exit: (code: number) => never;
+}): Promise<void>;
+export declare function registerValidateMediaCommand(program: Command): Command;