docs: some initial groundwork #2
2 changed files with 13 additions and 3 deletions
|
@ -19,8 +19,6 @@
|
|||
- algebraic enums
|
||||
- traits (`Numeric`...)
|
||||
|
||||
#pagebreak()
|
||||
|
||||
= Execution stages
|
||||
multisamplednight marked this conversation as resolved
Outdated
|
||||
|
||||
#graphics.stages-overview
|
||||
multisamplednight marked this conversation as resolved
Outdated
schrottkatze
commented
This is fine, probably something we can work on further as the project progresses though and it gets more complex... This is fine, probably something we can work on further as the project progresses though and it gets more complex...
|
||||
|
|
|
@ -73,8 +73,10 @@
|
|||
set text(..fonts.main)
|
||||
set heading(numbering: "A.1")
|
||||
|
||||
show link: text.with(fill: blue)
|
||||
show heading: it => text(..fonts.heading, it)
|
||||
// color links
|
||||
show link: text.with(fill: blue)
|
||||
// prettify codeblocks
|
||||
show raw.where(block: true): box.with(
|
||||
fill: luma(95%),
|
||||
inset: 1.25em,
|
||||
|
@ -93,6 +95,16 @@
|
|||
it
|
||||
}
|
||||
|
||||
// semi-strategically place pagebreaks for better orientation
|
||||
let pagebreak-before(it) = pagebreak() + it
|
||||
show heading.where(outlined: true): it => {
|
||||
if it.level <= 2 {
|
||||
pagebreak()
|
||||
}
|
||||
|
||||
it
|
||||
}
|
||||
|
||||
// highlight important terms in bold
|
||||
show raw: it => {
|
||||
// avoid making terms in codeblocks bold
|
||||
|
|
Loading…
Reference in a new issue
I really dislike using the word
execution
here, as it's a very common trigger word. Do you have any alternative ideas?Parsing? Evaluation? Interpretation?
Those are all individual phases of execution.
Hm. Thinking about it,
Evaluation
seems generic enough. I'll use that then.