How to correct the links in my built html pages?

Open
#245 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
markdown, python
Domain
documentation

Research direction

Start with the reported conf.py, index.rst, Markdown sources, and the generated HTML structure, then compare the link targets with the ABlog, Sphinx, and MyST configuration. Done means identifying a reproducible configuration issue or documenting the expected output and the specific setting that needs correction.

Written by the indexing model from the issue text.

Description

Bug Help Wanted

Hi,

This is more of a question rather than a bug report. If preferred I can ask elsewhere instead of raising an issue here.

I'm trying to build and deploy a simple blog using ablog with the pydata sphinx theme. Everything is going well except the links in the built html are broken and I can't seem to fix them.

I have a main blog folder with my conf.py and an index.rst file. I have some blog source files in markdown format (I'm using the myst parser).

The built html looks like this

Screenshot 2023-08-16 at 16 48 27

If I click on the links to the different posts I see this page

Screenshot 2023-08-16 at 16 56 49

It seems each post has its own directory and contains a single index.html file which I did not expect. Clicking on the index.html link does take me to the expected post.

I suspect something has gone with the file structure of my project. I don't think there should be a new directory for every single blog post with a single index.html file in each directory.

Any idea what I've done wrong? I'm sure I'm just missing something.

Any help would be appreciated. Thanks in advance.

Dominant language
Python
Stars
196
Forks
64
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sunpy/ablog

All issues in sunpy/ablog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.