mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #1711] Website: Broken Markdown (un-formatted links and code) in accordions on main ArchiveBox website #2535
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#2535
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tatianaanthony on GitHub (Nov 17, 2025).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1711
Originally assigned to: @pirate on GitHub.
What is the URL of the page you'd like to see improved?
archivebox.io
What is the title of the relevant section?
Comparison to Other Options
What is the suggested edit?
The accordions/dropdowns in the ArchiveBox.io main website appear to not parse markdown. See image, in the bottom paragraph, where the links to other sites are showing the

()[]formatting used in markdown.The same sort of thing occurs in the Markdown Development section: Within the accordion, the subheadings are shown as
#s and the code sections are shown with their enclosing ````` marks.Based on the website theme, I suspect you're using Jekyll with Kramdown. But when using
<details><summary>blocks for the accordions, I've found that you need to do one of the following:<span markdown="1">content with [markdown](markdownguide.org) **formatting**</span>around any sections that need markdown formatting<details markdown="span">or<details markdown="block">(though theses can potentially cause other unwanted behaviorOther accordion formatting likely needs similar fixes.
Hope this helps!
@pirate commented on GitHub (Nov 18, 2025):
yah I know it's been like this for years, it's auto-generated from the README and I couldn't be bothered to hand-write custom html for all of it because the markdown is easier to edit and maintain