aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Smedegaard <dr@jones.dk>2025-05-24 11:14:08 +0200
committerJonas Smedegaard <dr@jones.dk>2025-05-24 11:14:08 +0200
commit85e5c51dab5877362afc3203b84dc56a4e6cf2c8 (patch)
tree0f2c50d18d5f7d689f191e88b048fe17ff58a85e
parent768204fbb166301cc83980c0bbb9f7e57a404706 (diff)
add TODOs for problem formulation
-rw-r--r--_intro.qmd10
1 files changed, 8 insertions, 2 deletions
diff --git a/_intro.qmd b/_intro.qmd
index 5e4e4be..c39a6cd 100644
--- a/_intro.qmd
+++ b/_intro.qmd
@@ -55,13 +55,19 @@ So,
* What are the core qualities of Markdown,
and how can a Markdown dialect express semantic text annotations
while maintaining those qualities?
-* How do Pandoc convert Markdown to HTML or PDF,
- and how can this workflow be extended
+* *TODO: Analysis of spec, phrased as a question*
+* How do Pandoc parse Markdown into a generalised content structure,
+ and how can that process be extended
to handle semantic text annotations?
* Which approach to extending Pandoc
is more likely long-term sustainable?
* How can the reliability of a Pandoc extension be evaluated?
+*TODO: Maybe reframe as investigation of the spec,
+implementing it to identify its strengths and weaknesses*
+
+*FIXME: align above questions with actual findings*
+
## Project constraints
Driven by an interest in sustained development of this research project