migrate blog
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- html, latex, markdown, python, r, typescript
- Domain
- content, documentation, web-dev
Research direction
Start by reviewing the new branch, the old blog backup tag, and the content under /posts, attic, about, and the home page. Check old URLs, image URLs, and posts containing LaTeX, R, Python, inline HTML, and Markdown tables. Done means the remaining checklist items are resolved, old URLs and images work where feasible, and the migrated pages render correctly.
Written by the indexing model from the issue text.
Description
- backup old blog to a tag
- push empty quartz website onto
newbranch - migrate old content to
newbranch- ultimate goal here is to preserve old URLs if possible
- maybe I can just configure some specific URLs to redirect to preserve those old URLs?
- naive move
- recover old URLs
- fix inline images
- recover image URLs? not sure if feasible?
- I think we might be good to go here, just need to double check
- Reconsider "attic" subfolder
- double check old posts look fine
- latex
- r code
- python code
- inline html
- images
- markdown tables
- might just need to activate https://quartz.jzhao.xyz/plugins/HardLineBreaks ?
- update home page
- update social links
- add blog auto TOC (?)
- quick and easy solution: just move the attic content to a
blogorpostssubfolder or something like that, and then link to the blog on the front page or insert some sort of redirect from the index page to theblogpage
- quick and easy solution: just move the attic content to a
- fix favicon
- add DigThatData pfp
- update
aboutpage - integrate
benchwarmerscontent authoring mechanism- might not even need to go that fancy, can probably just write markdown directly into
/posts, right? - conversely, this could be an obsidian plugin? my preference is to not need to use obsidian for authorship though. I guess quartz supports certain plugins or something? Maybe deal with TOC stuff later
- might not even need to go that fancy, can probably just write markdown directly into
- rename branch
mastertomain
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·