Add blog generator feature with storage-first virtual IFolder pattern #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add WacsdkBlogCommands.cs aggregator - Add PostPage/PostPageCommand.cs CLI command - Add PostPage/PostPageGenerator.cs transformation logic - Add PostPage/PostPageDataModel.cs Scriban data contract Nested structure isolates scenarios, prevents interdependencies. Implementation separate from commands for reusability by future scenarios.
- Implemented PostPageGenerator with 3 partial files: - PostPageGenerator.Markdown.cs: ParseMarkdown, TransformMarkdown, ParseFrontmatter - PostPageGenerator.Template.cs: ResolveTemplate, CopyAssets, RenderTemplate - PostPageGenerator.cs: CreateDataModel, CreateOutputFolder, WriteIndexHtml, GenerateAsync orchestrator - Implemented PostPageCommand with CLI interface: - 4 options: --markdown, --template, --output, --template-file - Path resolution using SystemFile/SystemFolder constructors - Template type detection via Directory.Exists - Generator invocation with proper error handling - Applied all 12 gap resolutions from planning: - Markdig Advanced Extensions, YamlDotNet error handling, template conventions - DepthFirstRecursiveFolder for asset copying, path sanitization - Exception-based error handling, silent overwrite behavior - Ready for testing & validation
…plate file handling
- Replaced side-effect orchestrator with virtual IFolder implementation - Enables Multi-Page composition (prerequisite for PagesFolder) - Backward compatible: PostPageCommand behavior unchanged - Manual validation: Output matches pre-refactor baseline Components: - PostPageFolder: Virtual IFolder wrapping markdown source - IndexHtmlFile: Lazy generation on content access - PostPageAssetFolder: Recursive template asset mirroring Removed: - PostPageGenerator.cs (3 partials) Modified: - PostPageCommand.cs: Direct PostPageFolder integration Refs: - planning,post-page,refactor.md (requirements) - planning,post-page,refactor,execution.md (implementation tracking)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds blog generator feature with storage-first virtual IFolder pattern for markdown-to-HTML transformation. Implements Single-Page (Post/Page) scenario with PostPageFolder virtual IFolder architecture, enabling future Multi-Page composition.
Features
filename/index.htmlstructure for clean URLsImplementation
New Components:
Architecture:
Validation
Documentation
The planning and execution docs in their completed states, rendered to webpages using the finished code they represent:
Next Steps