@terrymooreii/sia 2.1.13 → 2.3.0

package/bin/cli.js

@@ -15,6 +15,7 @@ import { buildCommand } from '../lib/build.js';
 import { newCommand } from '../lib/new.js';
 import { initCommand } from '../lib/init.js';
 import { themeCommand } from '../lib/theme.js';
+import { migrateCommand } from '../lib/migrate.js';
 
 program
   .name('sia')
@@ -54,5 +55,11 @@ program
   .option('-q, --quick', 'Skip prompts and use defaults')
   .action(themeCommand);
 
+program
+  .command('migrate')
+  .description('Migrate standalone .md files to folder-based structure (folder/index.md)')
+  .option('--dry-run', 'Preview changes without applying them', false)
+  .action(migrateCommand);
+
 program.parse();
 

package/docs/README.md

@@ -10,6 +10,8 @@ Welcome to the Sia documentation. Sia is a simple, powerful static site generato
 | [Markdown Guide](markdown-guide.md) | Markdown syntax and all supported plugins |
 | [Front Matter Reference](front-matter.md) | YAML front matter options for posts, pages, and notes |
 | [Creating Themes](creating-themes.md) | How to create and customize themes |
+| [Plugin System](plugins.md) | Extend Sia with plugins - hooks, API, and configuration |
+| [Creating Plugins](creating-plugins.md) | Guide to creating local and npm package plugins |
 
 ## Quick Links
 
@@ -58,6 +60,7 @@ npm run build
 - **Live Reload** - Development server with hot reloading
 - **Multiple Themes** - Built-in themes (main, minimal, developer, magazine) with light/dark mode
 - **Custom Theme Packages** - Create and share themes as npm packages (`sia-theme-*`)
+- **Plugin System** - Extend functionality with local or npm plugins (`sia-plugin-*`)
 - **RSS Feed** - Automatic RSS feed generation
 - **SEO Ready** - Open Graph and Twitter Card meta tags included
 
@@ -68,8 +71,17 @@ my-site/
 ├── _config.yml          # Site configuration
 ├── src/
 │   ├── posts/           # Blog posts (markdown)
+│   │   └── 2024-12-17-my-post/
+│   │       ├── index.md
+│   │       └── (assets can go here)
 │   ├── pages/           # Static pages
+│   │   └── about/
+│   │       ├── index.md
+│   │       └── (assets can go here)
 │   ├── notes/           # Short notes/tweets
+│   │   └── 2024-12-17-note-1234567890/
+│   │       ├── index.md
+│   │       └── (assets can go here)
 │   └── images/          # Images
 ├── assets/              # Static assets (optional)
 ├── static/              # Static assets (optional)
@@ -77,10 +89,14 @@ my-site/
 ├── favicon.ico          # Site favicon (optional)
 ├── _layouts/            # Custom layouts (optional)
 ├── _includes/           # Custom includes (optional)
+├── _plugins/            # Local plugins (optional)
+│   └── my-plugin.js
 ├── styles/              # Custom CSS (optional)
 └── dist/                # Generated output
 ```
 
+Each post, page, and note is created as a folder containing an `index.md` file. This allows you to organize assets (images, PDFs, etc.) alongside your content in the same folder.
+
 ## Configuration
 
 Edit `_config.yml` to customize your site:
@@ -125,6 +141,12 @@ server:
 assets:
   css: []  # Custom CSS files (paths relative to root)
   js: []   # Custom JavaScript files (paths relative to root)
+
+plugins:
+  enabled: true          # Master switch for plugins
+  strictMode: false      # Fail build on plugin errors
+  order: []              # Explicit plugin execution order (optional)
+  config: {}             # Plugin-specific configuration
 ```
 
 ## Custom CSS and JavaScript
@@ -162,6 +184,40 @@ This will:
 
 And inject them into all pages automatically.
 
+## Plugin System
+
+Sia includes a powerful plugin system that allows you to extend functionality at key points in the build lifecycle. Plugins can:
+
+- Transform content during parsing
+- Generate additional files (search indexes, sitemaps, etc.)
+- Add custom Marked extensions for markdown processing
+- Register custom Nunjucks template filters and functions
+- Modify site data before rendering
+- Perform post-build tasks
+
+### Using Plugins
+
+Plugins can be local (in `_plugins/` directory) or npm packages (with `sia-plugin-*` naming):
+
+```bash
+# Install an npm plugin
+npm install sia-plugin-search
+
+# Or create a local plugin in _plugins/my-plugin.js
+```
+
+Configure plugins in `_config.yml`:
+
+```yaml
+plugins:
+  enabled: true
+  config:
+    sia-plugin-search:
+      outputPath: search-index.json
+```
+
+See the [Plugin System documentation](plugins.md) for complete details and the [Creating Plugins guide](creating-plugins.md) for examples.
+
 ## Static Assets
 
 Sia automatically copies static assets during the build process. You can place static files in any of these locations:
@@ -225,6 +281,7 @@ dist/
 | `sia new page "Title"` | Create a new page |
 | `sia new note "Content"` | Create a new note |
 | `sia theme <name>` | Create a new theme package |
+| `sia migrate` | Migrate standalone .md files to folder structure |
 
 ## License
 

package/docs/creating-plugins.md

@@ -0,0 +1,509 @@
+# Creating Plugins
+
+This guide explains how to create plugins for Sia, both as local plugins in your project and as npm packages that can be shared with others.
+
+## Plugin Types
+
+Sia supports two types of plugins:
+
+1. **Local plugins**: JavaScript files in your project's `_plugins/` directory
+2. **NPM package plugins**: Published npm packages with the `sia-plugin-*` naming convention
+
+## Local Plugins
+
+Local plugins are perfect for project-specific functionality that you don't need to share.
+
+### Creating a Local Plugin
+
+1. Create a `_plugins/` directory in your project root (if it doesn't exist)
+2. Create a JavaScript file (`.js` or `.mjs`) in that directory
+3. Export a plugin object
+
+**Example: `_plugins/search-index.js`**
+
+```javascript
+export default {
+  name: 'search-index',
+  version: '1.0.0',
+  hooks: {
+    afterBuild: async (siteData, config, api) => {
+      // Generate search index
+      const searchData = {
+        pages: siteData.collections.pages.map(item => ({
+          title: item.title,
+          url: item.url,
+          excerpt: item.excerpt,
+          tags: item.tags
+        })),
+        posts: siteData.collections.posts.map(item => ({
+          title: item.title,
+          url: item.url,
+          date: item.date.toISOString(),
+          excerpt: item.excerpt,
+          tags: item.tags
+        })),
+        notes: siteData.collections.notes.map(item => ({
+          title: item.title,
+          url: item.url,
+          date: item.date.toISOString(),
+          excerpt: item.excerpt
+        }))
+      };
+      
+      // Write search index file
+      const outputPath = api.joinPath(config.outputDir, 'search-index.json');
+      api.writeFile(outputPath, JSON.stringify(searchData, null, 2));
+      api.log('Generated search index', 'info');
+    }
+  }
+};
+```
+
+### Local Plugin with Configuration
+
+You can access plugin-specific configuration from `config.plugins.config`:
+
+```javascript
+export default {
+  name: 'search-index',
+  version: '1.0.0',
+  configSchema: {
+    outputPath: { type: 'string', default: 'search-index.json' },
+    includeContent: { type: 'boolean', default: false }
+  },
+  hooks: {
+    afterBuild: async (siteData, config, api) => {
+      const pluginConfig = config.plugins?.config?.['search-index'] || {};
+      const outputPath = pluginConfig.outputPath || 'search-index.json';
+      const includeContent = pluginConfig.includeContent || false;
+      
+      const searchData = {
+        pages: siteData.collections.pages.map(item => ({
+          title: item.title,
+          url: item.url,
+          excerpt: item.excerpt,
+          ...(includeContent && { content: item.content })
+        })),
+        // ... posts, notes
+      };
+      
+      api.writeFile(
+        api.joinPath(config.outputDir, outputPath),
+        JSON.stringify(searchData, null, 2)
+      );
+    }
+  }
+};
+```
+
+Configure in `_config.yml`:
+
+```yaml
+plugins:
+  config:
+    search-index:
+      outputPath: search-index.json
+      includeContent: false
+```
+
+## NPM Package Plugins
+
+NPM package plugins can be shared with the community and installed via npm.
+
+### Creating an NPM Package Plugin
+
+1. Create a new npm package with name starting with `sia-plugin-`
+2. Set up the package structure
+3. Export the plugin object
+
+### Package Structure
+
+```
+sia-plugin-example/
+├── package.json
+├── index.js
+├── README.md
+└── LICENSE
+```
+
+### package.json
+
+```json
+{
+  "name": "sia-plugin-example",
+  "version": "1.0.0",
+  "description": "Example Sia plugin",
+  "main": "index.js",
+  "type": "module",
+  "keywords": [
+    "sia",
+    "sia-plugin",
+    "static-site-generator"
+  ],
+  "author": "Your Name",
+  "license": "MIT",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "peerDependencies": {
+    "@terrymooreii/sia": "^2.0.0"
+  }
+}
+```
+
+### index.js
+
+```javascript
+export default {
+  name: 'sia-plugin-example',
+  version: '1.0.0',
+  configSchema: {
+    enabled: { type: 'boolean', default: true },
+    outputFile: { type: 'string', default: 'example-output.json' }
+  },
+  hooks: {
+    afterBuild: async (siteData, config, api) => {
+      const pluginConfig = config.plugins?.config?.['sia-plugin-example'] || {};
+      
+      if (pluginConfig.enabled === false) {
+        return;
+      }
+      
+      const output = {
+        buildDate: new Date().toISOString(),
+        totalPages: siteData.collections.pages.length,
+        totalPosts: siteData.collections.posts.length,
+        totalNotes: siteData.collections.notes.length,
+        totalTags: siteData.allTags.length
+      };
+      
+      api.writeFile(
+        api.joinPath(config.outputDir, pluginConfig.outputFile || 'example-output.json'),
+        JSON.stringify(output, null, 2)
+      );
+      
+      api.log(`Generated ${pluginConfig.outputFile}`, 'info');
+    }
+  }
+};
+```
+
+### Installing and Using
+
+Users install your plugin:
+
+```bash
+npm install sia-plugin-example
+```
+
+Then configure it in `_config.yml`:
+
+```yaml
+plugins:
+  config:
+    sia-plugin-example:
+      enabled: true
+      outputFile: stats.json
+```
+
+## Advanced Examples
+
+### Content Transformation Plugin
+
+Transform content during parsing:
+
+```javascript
+export default {
+  name: 'content-transformer',
+  version: '1.0.0',
+  hooks: {
+    beforeMarkdown: (markdown, context) => {
+      // Replace custom syntax
+      return markdown.replace(/\[TOC\]/g, '<!-- Table of Contents -->');
+    },
+    afterMarkdown: (html, context) => {
+      // Inject custom HTML
+      return html.replace(
+        '<!-- Table of Contents -->',
+        '<nav class="toc">...</nav>'
+      );
+    }
+  }
+};
+```
+
+### Custom Template Filter Plugin
+
+Add custom Nunjucks filters:
+
+```javascript
+export default {
+  name: 'custom-filters',
+  version: '1.0.0',
+  hooks: {
+    addTemplateFilter: (env, config) => {
+      // Add a filter to format numbers
+      env.addFilter('formatNumber', (num) => {
+        return new Intl.NumberFormat().format(num);
+      });
+      
+      // Add a filter to truncate text
+      env.addFilter('truncate', (str, length = 50) => {
+        if (str.length <= length) return str;
+        return str.substring(0, length) + '...';
+      });
+    }
+  }
+};
+```
+
+Use in templates:
+
+```nunjucks
+{{ post.wordCount | formatNumber }}
+{{ post.excerpt | truncate(100) }}
+```
+
+### Custom Marked Extension Plugin
+
+Add custom markdown syntax:
+
+```javascript
+import { addMarkedExtension } from '@terrymooreii/sia';
+
+export default {
+  name: 'custom-markdown',
+  version: '1.0.0',
+  hooks: {
+    beforeBuild: (config, api) => {
+      addMarkedExtension({
+        renderer: {
+          // Custom blockquote renderer
+          blockquote(quote) {
+            return `<blockquote class="custom-quote">${quote}</blockquote>`;
+          }
+        }
+      });
+    }
+  }
+};
+```
+
+### Sitemap Generator Plugin
+
+Generate a sitemap.xml:
+
+```javascript
+export default {
+  name: 'sitemap-generator',
+  version: '1.0.0',
+  hooks: {
+    afterBuild: async (siteData, config, api) => {
+      const siteUrl = config.site.url.replace(/\/$/, '');
+      const basePath = config.site.basePath || '';
+      
+      const urls = [];
+      
+      // Add homepage
+      urls.push({
+        loc: `${siteUrl}${basePath}/`,
+        lastmod: new Date().toISOString().split('T')[0],
+        changefreq: 'daily',
+        priority: '1.0'
+      });
+      
+      // Add all content items
+      for (const [collectionName, items] of Object.entries(siteData.collections)) {
+        for (const item of items) {
+          urls.push({
+            loc: `${siteUrl}${item.url}`,
+            lastmod: item.date.toISOString().split('T')[0],
+            changefreq: 'monthly',
+            priority: collectionName === 'pages' ? '0.8' : '0.6'
+          });
+        }
+      }
+      
+      // Generate XML
+      const sitemap = `<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+${urls.map(url => `  <url>
+    <loc>${url.loc}</loc>
+    <lastmod>${url.lastmod}</lastmod>
+    <changefreq>${url.changefreq}</changefreq>
+    <priority>${url.priority}</priority>
+  </url>`).join('\n')}
+</urlset>`;
+      
+      api.writeFile(
+        api.joinPath(config.outputDir, 'sitemap.xml'),
+        sitemap
+      );
+      
+      api.log('Generated sitemap.xml', 'info');
+    }
+  }
+};
+```
+
+### Plugin with Dependencies
+
+Plugins can depend on other plugins:
+
+```javascript
+export default {
+  name: 'enhanced-search',
+  version: '1.0.0',
+  dependencies: ['search-index'], // Requires search-index plugin
+  hooks: {
+    afterBuild: async (siteData, config, api) => {
+      // This plugin enhances the search index created by search-index plugin
+      // It runs after search-index because of the dependency
+    }
+  }
+};
+```
+
+## Best Practices
+
+### 1. Error Handling
+
+Always handle errors gracefully:
+
+```javascript
+hooks: {
+  afterBuild: async (siteData, config, api) => {
+    try {
+      // Plugin logic
+    } catch (err) {
+      api.log(`Plugin error: ${err.message}`, 'error');
+      // Don't throw - let the build continue
+    }
+  }
+}
+```
+
+### 2. Configuration Validation
+
+Validate plugin configuration:
+
+```javascript
+hooks: {
+  beforeBuild: (config, api) => {
+    const pluginConfig = config.plugins?.config?.['my-plugin'] || {};
+    
+    if (pluginConfig.requiredOption === undefined) {
+      throw new Error('my-plugin: requiredOption is required');
+    }
+  }
+}
+```
+
+### 3. Async Operations
+
+Use async/await for asynchronous operations:
+
+```javascript
+hooks: {
+  afterBuild: async (siteData, config, api) => {
+    const data = await fetchExternalData();
+    // Process data
+  }
+}
+```
+
+### 4. Logging
+
+Use the API's logging function:
+
+```javascript
+api.log('Processing complete', 'info');
+api.log('Warning: something unusual', 'warn');
+api.log('Error occurred', 'error');
+```
+
+### 5. Documentation
+
+Document your plugin:
+
+- Explain what it does
+- List configuration options
+- Provide usage examples
+- Include version compatibility
+
+### 6. Testing
+
+Test your plugin:
+
+1. Create a test Sia site
+2. Add your plugin
+3. Run `sia build`
+4. Verify the output
+
+### 7. Version Compatibility
+
+Specify Sia version requirements in your plugin's README:
+
+```markdown
+## Requirements
+
+- Sia >= 2.0.0
+- Node.js >= 18.0.0
+```
+
+## Publishing NPM Plugins
+
+1. **Prepare your package:**
+   - Write a clear README
+   - Add a LICENSE file
+   - Test thoroughly
+
+2. **Publish to npm:**
+   ```bash
+   npm login
+   npm publish
+   ```
+
+3. **Tag your releases:**
+   ```bash
+   git tag v1.0.0
+   git push --tags
+   ```
+
+4. **Update documentation:**
+   - Add to Sia's plugin list (if applicable)
+   - Share on social media/forums
+
+## Troubleshooting
+
+### Plugin Not Loading
+
+- Check that the plugin file is in `_plugins/` or installed via npm
+- Verify the plugin exports a default object with `name` and `version`
+- Check console output for error messages
+
+### Hook Not Executing
+
+- Verify the hook name is correct
+- Check that the hook function is properly defined
+- Ensure the plugin is enabled (`plugins.enabled: true`)
+
+### Configuration Not Working
+
+- Verify configuration is in `config.plugins.config[pluginName]`
+- Check that plugin name matches exactly (case-sensitive)
+- Validate configuration structure matches `configSchema`
+
+### Build Failing
+
+- Set `plugins.strictMode: false` to see detailed error messages
+- Check plugin dependencies are installed
+- Verify Node.js version compatibility
+
+## Resources
+
+- [Plugin System Documentation](./plugins.md) - Complete hook reference
+- [Sia GitHub Repository](https://github.com/terrymooreii/sia) - Source code and issues
+- [Marked Documentation](https://marked.js.org/) - For custom markdown extensions
+- [Nunjucks Documentation](https://mozilla.github.io/nunjucks/) - For custom template filters/functions
+

package/docs/front-matter.md

@@ -366,19 +366,27 @@ permalink: /featured/special-post/
 
 ## Date from Filename
 
-Sia can extract dates from filenames using this pattern:
+Sia can extract dates from filenames (or folder names when using `index.md`) using this pattern:
 
 ```
 YYYY-MM-DD-slug.md
 ```
 
+or for folder-based content:
+
+```
+YYYY-MM-DD-slug/index.md
+```
+
 ### Examples
 
-| Filename | Extracted Date | Extracted Slug |
-|----------|----------------|----------------|
-| `2024-12-17-my-post.md` | December 17, 2024 | `my-post` |
-| `2024-01-05-new-year.md` | January 5, 2024 | `new-year` |
-| `about.md` | Current date | `about` |
+| Filename/Folder | Extracted Date | Extracted Slug |
+|-----------------|----------------|----------------|
+| `2024-12-17-my-post/index.md` | December 17, 2024 | `my-post` |
+| `2024-01-05-new-year/index.md` | January 5, 2024 | `new-year` |
+| `about/index.md` | Current date | `about` |
+| `2024-12-17-my-post.md` | December 17, 2024 | `my-post` (backward compatible) |
+| `about.md` | Current date | `about` (backward compatible) |
 
 ### Priority
 
@@ -391,8 +399,8 @@ Date resolution follows this priority:
 Slug resolution:
 
 1. `slug` in front matter (highest priority)
-2. Slug extracted from filename (after date prefix)
-3. Slugified filename
+2. Slug extracted from filename or folder name (after date prefix if present)
+3. Slugified filename or folder name
 
 ---