How to make author info and blog categories appear in built html?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- markdown, python
- Domain
- documentation, web-dev
Research direction
Start by inspecting a generated post under the built _website directory and comparing its HTML with the Markdown front matter shown in the issue. Then review the ablog and myst_parser configuration, including the post patterns; done means author, date, and category information appears beneath each blog post.
Written by the indexing model from the issue text.
Description
Hi
I have now deployed my blog here (still a WIP).
Ideally I would like the author info, date and topic categoies to appear under each post. See this example from pydata-sphinx-theme.
I'm not sure what I've missed. The categorised files are in the built _website directory but the info does not display with the posts.
I have the following front matter in my markdown source files
---
blogpost: true
date: Sep 8, 2023
author: Callum Macpherson
category: Release
---
# September Release Notes (pytket)
I have the following ablog configuation settings
# ----- ablog config settings -----
ablog_website = "_website"
ablog_builder = "dirhtml"
blog_path = "blog"
blog_baseurl = "https://tket.quantinuum.com/tket-blog/"
blog_title = "TKET Developer Blog"
blog_authors = {
"Callum Macpherson": ("Callum Macpherson", None),
}
blog_post_pattern = ["posts/*.rst", "posts/*.md"]
blog_feed_archives = True
blog_post_pattern = "blog/*/*"
blog_feed_fulltext = True
# List of Sphinx extensions used
extensions = ["ablog", "myst_parser", "sphinx_copybutton"]
# ----- MyST parser config -----
myst_enable_extensions = ["dollarmath", "html_image"]
myst_update_mathjax = False
Any help would be really appreaciated. Thanks in advance.
- Dominant language
- Python
- Stars
- 196
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sunpy/ablog
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100