Model site archetypes in Front Matter CMS and ease article submission#12
Merged
Conversation
Replace the single generic `default` content type with five typed ones (article, podcast, event, page, author) mapped to their content folders, so the Front Matter editor matches what contributors actually write. - frontmatter.json: per-folder content types + mappings, auto date-prefixed filenames, RFC3339 dateFormat, authors custom taxonomy - archetypes: convert default.md to YAML; add articles/podcast/calendar/ authors templates named to match Hugo sections - taxonomyDb.json: seed authors dropdown from existing content - add-article.yml: turn an approved guest-post issue into a front-mattered article file + PR (mirrors add-event.yml) - guest-blog-post.yml: add Description, Category, and Tags inputs - CONTRIBUTING.md: include description in the front matter template Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for powershellorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
* Introduced a new `.vscode/extensions.json` file. * Added recommendations for essential extensions to enhance development experience.
* Prevent local Netlify folder from being tracked by Git.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s authoring workflow for the Hugo site by modeling the site’s real content archetypes in Front Matter CMS, adding matching Hugo archetypes, and automating “approved” guest-article issue submissions into PRs.
Changes:
- Adds a multi–content-type
frontmatter.json(article/podcast/event/page/author) plus seeded taxonomy DB entries for categories/authors. - Adds Hugo archetypes for section-based content creation and converts the default archetype to YAML.
- Introduces an
add-articleGitHub Actions workflow and expands the guest blog post issue form to capture description/category/tags.
Reviewed changes
Copilot reviewed 12 out of 13 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
frontmatter.json |
Defines Front Matter CMS content types/fields and folder mappings for Hugo sections. |
CONTRIBUTING.md |
Updates the front-matter template and documents a Front Matter CMS submission tip. |
archetypes/default.md |
Converts default archetype front matter from TOML to YAML. |
archetypes/articles.md |
Adds an articles section archetype with expected front matter. |
archetypes/podcast.md |
Adds a podcast section archetype including podcast_url. |
archetypes/calendar.md |
Adds a calendar/events section archetype matching existing event fields. |
archetypes/authors.md |
Adds an authors section archetype for author taxonomy pages. |
.vscode/extensions.json |
Recommends VS Code extensions (Front Matter CMS + Markdown tooling). |
.gitignore |
Ignores local Netlify artifacts. |
.github/workflows/add-article.yml |
Creates a PR automatically from an approved guest-article issue submission. |
.github/ISSUE_TEMPLATE/guest-blog-post.yml |
Adds description/category/tags fields to support automated article generation. |
.frontmatter/database/taxonomyDb.json |
Seeds categories and the custom authors taxonomy options for Front Matter CMS. |
.frontmatter/database/pinnedItemsDb.json |
Adds a pinned-items DB placeholder for Front Matter CMS. |
KennyNeal
approved these changes
Jun 19, 2026
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
- frontmatter.json: write event startDate/endDate as date-only (yyyy-MM-dd) so Front Matter CMS doesn't add a time component and drift from existing calendar files - add-article.yml: strip HTML from scalar front matter fields (parity with add-event.yml), normalize CRLF and tolerate whitespace around the markdown content fences, and fall back to article-<issue#> when a title produces an empty slug Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
Author
|
Addressed the review feedback in
Verified with a parser unit test (CRLF body, HTML in description, fenced content with blank lines, and a punctuation-only title) plus JSON/YAML validation. |
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
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
The Front Matter CMS config (
frontmatter.json) was scaffolded with a single genericdefaultcontent type mapped to all ofcontent/, but the site has five distinct archetypes whose real fields (author/authors,aliases,podcast_url, the event fields,layout) weren't modeled at all. This reworks the config to match reality and smooths the path for submitting new content.Content types & config
defaulttype with article, podcast, event, page, author, each mapped to its content folder viapageFolders.filePrefix: {{year}}-{{month}}-{{day}}so theYYYY-MM-DD-slugconvention is automatic.author/authorswired to a seeded custom taxonomy;categoriesis a closed multiselect from the existing 15-term list.dateFormatset to RFC3339 to match existing content (prevents Hugo parse drift); requireddescriptionfield for SEO/social cards/list excerpts.Archetypes
archetypes/default.mdfrom TOML to YAML (all content uses YAML).articles.md,podcast.md,calendar.md,authors.md— named to match Hugo section dirs sohugo newpicks them up.Submission flow
.github/workflows/add-article.yml: an approved guest-post issue is parsed into a front-matteredcontent/articles/YYYY-MM-DD-slug.mdand opened as a PR (mirrors the existingadd-event.yml).guest-blog-post.ymlissue template gains Description, Category (dropdown), and Tags inputs.CONTRIBUTING.mdfront-matter template now includesdescription+ a Front Matter tip.Verification
frontmatter.jsonandtaxonomyDb.jsonare valid JSON; both workflow/template YAML files validate with PyYAML.hugo --gcbuilds clean.hugo newforarticles/podcast/calendar/authorseach produces a file matching its archetype.🤖 Generated with Claude Code