The writing section of the A Master Artificer theme is built across two files that work together.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/a-master-artificer/llms.txt
Use this file to discover all available pages before exploring further.
blogindex.html is the Loose Pages index — a list of all your articles with titles, summaries, and dates. article.html is the individual article view, where a single post is displayed in full. The route for both is under /blog. This two-file structure separates the browsing experience from the reading experience, which keeps each view focused on a single job.
Loose Pages — blogindex.html
The blog index page maps to the route/blog and carries the themed navigation label Loose Pages. Visitors land here first when they navigate to the writing section. They see a list of your articles, with enough information about each one to decide which to read.
File
/blogThemed label: Loose Pages
Asset:
assets/BlogIndex.js
HTML Structure
blogindex.html uses the same HTML shell as the rest of the theme. The article list and summary content are rendered by the React application from assets/BlogIndex.js.
What to Edit
Openassets/BlogIndex.js and replace the sample articles list with your own writing.
Add your article titles
Each entry in the index needs a title. Write titles that are specific and honest about what the article is — avoid vague or clickbait-style titles. A title like “What I Learned Debugging a Memory Leak in a Node.js Application” tells a reader exactly what they are getting.
Write a summary for each article
The summary appears in the index alongside the title. It should be one to three sentences that accurately describe what the article covers and why it is worth reading. Write summaries that help the reader decide — not summaries that just repeat the title.
Add publication dates
Include the date each article was published or last updated. Dates help visitors understand how recent your writing is and whether it is still relevant to current practices.
Confirm each article links to the correct route
Each article entry in the index should link to the individual article view at
/blog/:slug or the equivalent path used in the theme. Check that all links resolve correctly before publishing.Individual Article — article.html
The individual article page displays a single post in full. It maps to the route/blog/:slug (or the equivalent path structure used by the theme’s routing) and shares the Loose Pages navigation context. When a visitor selects an article title in the index, they are taken to this view.
File
/blog/:slugThemed label: Loose Pages
Asset:
assets/Article.js
HTML Structure
article.html uses the same HTML shell as the rest of the theme.
What to Edit
Openassets/Article.js and replace the sample article content with your own writing. Each article is a standalone piece with a title, date, and full body text.
Write or paste your article content
Replace the sample article body with your own writing. You can write directly in the JavaScript module or paste content you have drafted elsewhere.
Set the article title and date
Each article needs a title and a publication date. These appear at the top of the article view and should match the corresponding entry in the blog index.
Review formatting
Check that headings, paragraphs, and any code blocks or lists in your article render correctly in the browser after you save the file.
The Two-File Pattern
The separation betweenblogindex.html and article.html keeps each view focused on a single purpose. The index is for browsing; the article view is for reading. This pattern also makes it easier to add new writing over time — you add a new entry to the index and a new article in the article module without restructuring the HTML.
| blogindex.html | article.html | |
|---|---|---|
| Purpose | Lists all articles for browsing | Displays one article for reading |
| Content | Titles, summaries, dates, links | Full article body, title, date |
| Visitor action | Scans and selects | Reads from top to bottom |