.buildlist
build/
-src/
+src
help:
@echo "Builds HTML files from MD files. Targets include:"
@echo
- @echo "all Builds the .buildlist and an index. (Top-level)"
+ @echo "all Builds the .buildlist and an index.html. (Top-level)"
@echo "clean Removes build artifacts."
@echo "help Prints this help message."
@echo ".buildlist Defines a list of all files to build. Paths may be relative."
@echo " may create this file manually or override the BUILD_LIST variable when"
@echo " you invoke the make command. The default BUILD_LIST is created from MD files"
@echo " found anywhere under the $(SRC_DIR) directory."
+ @echo "init-demo Creates links from demo to $(SRC_DIR) so you can then build it."
+ @echo "init-altdemo Creates links from demo to $(SRC_DIR) (alternate method) so you can then build it."
+ @echo "rm-src Deletes symlinks in $(SRC_DIR), checking for non-link data."
.PHONY:
all: build/index.html
$(BUILD_DIR)/%.html: $(SRC_DIR)/%.md $(BUILD_DIR)/$(ASSETS_DIR)
@mkdir -p $(dir $@)
- @pandoc \
- --to=html5 \
- --standalone \
- --toc=true \
- --defaults=./defaults.yml \
- --output=$@ $< \
- --lua-filter=scripts/links-to-html.lua
+ @pandoc --defaults=./defaults/md-to-html.yml --output=$@ $<
@echo "Building $@ from $<..."
.PHONY:
+++ /dev/null
-from: markdown+wikilinks_title_before_pipe
-css:
- # ${.} is robust on build, but probably not for deployment
- - ../assets/css/normalize.css
- - ../assets/css/space-sakura.css
-
--- /dev/null
+from: markdown+wikilinks_title_before_pipe
+to: html5
+filters:
+ - ${.}/../filters/links-to-html.lua
+standalone: True
+toc: True
+css:
+ - ../assets/css/normalize.css
+ - ../assets/css/space-sakura.css
+++ /dev/null
-<!DOCTYPE html>
-<html>
-<head>
- <meta content="text/html; charset=utf-8" http-equiv="content-type">
- <title>sakura demo</title>
- <meta content="width=device-width, initial-scale=1" name="viewport">
- <link href='assets/css/normalize.css' rel='stylesheet' type='text/css'>
- <link href='assets/css/space-sakura.css' id="sakura-css" rel='stylesheet' type='text/css'>
-</head>
-<body>
- <div id="top">
- <h1>Space Sakura Demo</h1>
- <p>This is an anchor tag/hyper link: <a href="https://github.com/oxalorg/sakura">sakura - Github Repository</a></p>
- <p>Paragraphs look like this. Font size along with line height and maximum width are optimized for reading.</p>
-
- <p><em>Italic</em>, <strong>bold</strong>, and <code>monospace</code>. Itemized lists look like:</p>
- <ul>
- <li>this one</li>
- <li>that one</li>
- <li>the other one</li>
- </ul>
-
- <p><strong>Here's a block quote</strong>:</p>
- <blockquote>
- <p>Man surprised me most about humanity. Because he sacrifices his health in order to make money. Then he sacrifices money to recuperate his health. And then he is so anxious about the future that he does not enjoy the present; the result being that he does not live in the present or the future; he lives as if he is never going to die, and then dies having never really lived. -James J Lachard</p>
- </blockquote>
-
- <h2 id="an-h2-header">An h2 header</h2>
- <p><strong>Some code blocks</strong></p>
- <pre><code>define foobar() {
- print "Welcome to flavor country!";
-}</code></pre>
- <div class="sourceCode">
- <pre class="sourceCode python"><code class="sourceCode python"><span class="im">import</span> time
-<span class="co"># Quick, count to ten!</span>
-<span class="cf">for</span> i <span class="op">in</span> <span class="bu">range</span>(<span class="dv">10</span>):
- <span class="co"># (but not *too* quick)</span>
- time.sleep(<span class="fl">0.5</span>)
- <span class="bu">print</span> i</code></pre>
- </div>
-
- <h3 id="an-h3-header">An h3 header</h3>
- <p>A nested list:</p>
- <ol style="list-style-type: decimal">
- <li>
- <p>First, get these ingredients:</p>
- <ul>
- <li>carrots</li>
- <li>celery</li>
- <li>lentils</li>
- </ul>
- </li>
- <li>
- <p>Boil some water.</p>
- </li>
- <li>
- <p>Dump everything in the pot and follow this algorithm:</p>
- <pre><code>find wooden spoon
-uncover pot
-stir
-cover pot
-balance wooden spoon precariously on pot handle
-wait 10 minutes
-goto first step (or shut off burner when done)</code></pre>
- <p>Do not bump wooden spoon or it will fall.</p>
- </li>
- </ol>
-
- <h1 id="header-level-1">Header level 1</h1>
- <h2 id="header-level-2">Header level 2</h2>
- <h3 id="header-level-3">Header level 3</h3>
- <h4 id="header-level-4">Header level 4</h4>
- <h5 id="header-level-5">Header level 5</h5>
- <h6 id="header-level-6">Header level 6</h6>
-
- <p>A horizontal line:</p>
- <hr>
-
- <p>Here's a link to <a href="http://foo.bar">a website</a>, to a <a href="local-doc.html">local doc</a>, and to a <a href="#an-h2-header">section heading in the current doc</a>. Here's a footnote <a href="#fn1" id="fnref1"><sup>1</sup></a>.</p>
- <p>Tables can look like this:</p>
-
- <table>
- <caption>
- Shoes, their sizes, and what they're made of
- </caption>
- <thead>
- <tr >
- <th align="left">size</th>
- <th align="left">material</th>
- <th align="left">color</th>
- </tr>
- </thead>
- <tbody>
- <tr >
- <td align="left">9</td>
- <td align="left">leather</td>
- <td align="left">brown</td>
- </tr>
- <tr >
- <td align="left">10</td>
- <td align="left">hemp canvas</td>
- <td align="left">natural</td>
- </tr>
- <tr >
- <td align="left">11</td>
- <td align="left">glass</td>
- <td align="left">transparent</td>
- </tr>
- </tbody>
- </table>
- <p>Multi-line tables:</p>
- <table style="width:46%;">
- <colgroup>
- <col width="13%">
- <col width="31%">
- </colgroup>
- <thead>
- <tr>
- <th align="left">keyword</th>
- <th align="left">text</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td align="left">red</td>
- <td align="left">Sunsets, apples, and other red or reddish things.</td>
- </tr>
- <tr>
- <td align="left">green</td>
- <td align="left">Leaves, grass, frogs and other things it's not easy being.</td>
- </tr>
- </tbody>
- </table>
-
- <p>A horizontal rule follows.</p>
- <hr>
- <p>Images are responsive by default:</p>
- <div>
- <img alt="example image" src="sakura.png" title="An exemplary image">
- <p>example image</p>
- </div>
-
- <hr>
-
- <h1 id="form-elements">Form Elements</h1>
- <form>
- <div id="forms__input">
- <h3>Input fields</h3>
- <p><label for="input__text">Text Input</label> <input id="input__text" placeholder="Text Input" type="text"></p>
- <p><label for="input__password">Password</label> <input id="input__password" placeholder="Type your Password" type="password"></p>
- <p><label for="input__webaddress">Web Address</label> <input id="input__webaddress" placeholder="http://yoursite.com" type="url"></p>
- <p><label for="input__emailaddress">Email Address</label> <input id="input__emailaddress" placeholder="name@email.com" type="email"></p>
- <p><label for="input__phone">Phone Number</label> <input id="input__phone" placeholder="(999) 999-9999" type="tel"></p>
- <p><label for="input__search">Search</label> <input id="input__search" placeholder="Enter Search Term" type="search"></p>
- <p><label for="input__text2">Number Input</label> <input id="input__text2" placeholder="Enter a Number" type="number"></p>
- <p><label for="input__text3">Error</label> <input id="input__text3" placeholder="Text Input" type="text"></p>
- <p><label for="input__text4">Valid</label> <input id="input__text4" placeholder="Text Input" type="text"></p>
- </div>
- <p><a href="#top">[Top]</a></p>
- <div id="forms__select">
- <h3>Select menus</h3>
- <p><label for="select">Select</label> <select id="select">
- <optgroup label="Option Group">
- <option>
- Option One
- </option>
- <option>
- Option Two
- </option>
- <option>
- Option Three
- </option>
- </optgroup>
- </select></p>
- </div>
- <p><a href="#top">[Top]</a></p>
- <div id="forms__checkbox">
- <h3>Checkboxes</h3>
- <ul style="list-style:none;">
- <li><label for="checkbox1"><input checked="checked" id="checkbox1" name="checkbox" type="checkbox"> Choice A</label></li>
- <li><label for="checkbox2"><input id="checkbox2" name="checkbox" type="checkbox"> Choice B</label></li>
- <li><label for="checkbox3"><input id="checkbox3" name="checkbox" type="checkbox"> Choice C</label></li>
- </ul>
- </div>
- <p><a href="#top">[Top]</a></p>
- <div id="forms__textareas">
- <h3>Textareas</h3>
- <p><label for="textarea">Textarea</label>
- <textarea cols="48" id="textarea" placeholder="Enter your message here" rows="8"></textarea></p>
- </div>
- <p><a href="#top">[Top]</a></p>
- <div id="forms__html5">
- <div id="forms__action">
- <h3>Action buttons</h3>
- <p><input type="submit" value="input type=submit"> <input type="button" value="input type=button"> <input type="reset" value="input type=reset"> <input disabled type="submit" value="input disabled"></p>
- <p><button type="submit"><button type=submit></button> <button type="button"><button type=button></button> <button type="reset"><button type=reset></button> <button disabled type="button"><button disabled></button></p>
- </div>
- <p><a href="#top">[Top]</a></p>
- </div>
- </form>
- <div>
- <hr>
- <ol>
- <li id="fn1"><p>Footnote text goes here.<a href="#fnref1">↩</a></p></li>
- </ol>
- </div>
-</div>
-</body>
-</html>
+++ /dev/null
-# Experiments with Publishing My Markdown Notes
-
-## Summary
-
-* Turns out I don't need an app, I need a renderer.
-* Pandoc can render Markdown well. And now, it supports wikilinks. I might be
-able to have "internal" linking.
-* Find | Pandoc can work with a weird lambda-function kind of approach.
-* Make files also work pretty well.
-* I like sakura.css as a starting point: https://github.com/oxalorg/sakura
-for styling.
-
-## Find | Pandoc
-
-Single doc:
-
-``` bash
-pandoc --from=markdown+wikilinks_title_before_pipe --to=html5 -o build/note2 src/note2.md
-```
-
-Note: Pandoc complains if the build directory doesn't already exist.
-
-I think this should work. It grabs all the files in the src directory.
-For each file it finds, run `pandoc ... ` and output to build/note1 or
-build/note2.
-``` bash
-find . -path './src/*' -exec pandoc --from=markdown+wikilinks_title_before_pipe --to=html5 -o build/$(basename -s .md {}) {} \
-```
-
-Output
-```
-pandoc: build/./src/note2.md: withFile: does not exist (No such file or directory)
-pandoc: build/./src/note1.md: withFile: does not exist (No such file or directory)
-```
-
-To confirm that the basename shenanigans is doing what I want:
-``` bash
-find . -path './src/*' -exec basename -s .md {} \;
-# Output: note2\nnote1
-```
-
-Furthermore, without the output specified, it concatenates the input files and writes to stdout:
-```
-find . -path './src/*' -exec pandoc --from=markdown+wikilinks_title_before_pipe --to=html5 {} \;
-```
-
-This seems to identify the culprit! Something about passing
-the found files into a subshell.
-``` bash
-find . -path './src/*' -exec echo build/$(basename -s .md {}) \;
-# Output build/./src/note2.md...
-```
-
-This does it!
-``` bash
-find . -path './src/*' -exec sh -c 'pandoc --from=markdown+wikilinks_title_before_pipe --to=html5 -o build/$(basename -s .md $1) $1' _ {} \;
-```
-
-This is a pattern that I didn't expect for shells, but it's used elsewhere.
-It's like defining a lambda function and applying it in one step. Only we are
-using a subshell to define the lambda function. Here's the source from
-[Stack Overflow](https://stackoverflow.com/questions/13833824/how-to-run-a-subcommand-inside-find-exec).
-
-1. In a subshell, *define a function* that you want to run.
-2. When you close the subshell, the rest of the exec function applies the function.
-
-There is no passing the `{}` into the subshell. The `{}` exists in the original
-`-exec` shell. Instead, you're doing some kooky function definition.
-
-Note: We are using `$1` to align with the convention that `$0` is the name and
-`$1` is the first argument.
-
-From the man page of bash (emphasis mine):
-
->-c If the -c option is present, then commands are read from the first
-non-option argument command_string. If there are arguments after the command_string, *the first argument is assigned to $0 and any remaining
-arguments are assigned to the positional parameters*. The assignment to $0 sets
-the name of the shell, which is used in warning and error messages.
-
-# Regarding Map in Bash
-
-Map would be nice because then you don't have to loop inside definitions
-But looping doesn't play nice with spaces.
-I was pleasantly suprised it worked. Maybe there's a way around the
-space issue, but today isn't the day for that.
-
-``` bash
-map() {
- for item in $2; do
- # shellcheck disable=SC2005
- echo "$("$1" "$item")"
- done
-}
-```
-
-## BUG: Map breaks on spaces
-Context `map "make_li" "$1"`.
-
-When `$1` contains a space, it breaks there. *e.g.* when it contains
-`<a href=...`, the `make_li` function creates `<li><a</li>\n<li>href=...</li>`
-and so on. To be clear, this is not the fault of `make_li`.
-This is due to `$1` begin a space-delimited list and `map` breaking
-on spaces. Also, to be fair, that's just the way shells work by default.
-There's probably a clever way to manipulate lists as strings, but I don't know
-what the idiomatic shell way of doing it is.
-
-## Cut Fiasco
-`cut ... $1` reads the file itself.
-`echo $1 | cut ...` reads the string in `$1`.
-
-# Conclusion
-After tidying it all up, this command builds my entire stack of HTML and the links work!
-
-``` bash
-find ~/notes/rocketbowman/tiddlers/ -path '*.md' -exec sh -c 'pandoc --from=markdown+wikilinks_title_before_pipe --to=html5 -o ~/tmp/build/$(basename -s .md $1) $1' _ {} \;
-```
-
-## A better conclusion
-Turns out that a Makefile is the way to go. Create a rule for a 1-1 conversion. Then add a `make all` command.
\ No newline at end of file
--- /dev/null
+-- links-to-html.lua
+-- From https://stackoverflow.com/a/49396058
+function Link(el)
+ el.target = string.gsub(el.target, "%.md", ".html")
+ return el
+end
\ No newline at end of file
+++ /dev/null
-import subprocess
-import re
-from pathlib import Path
-
-# Motivating Question: Can I develop a dependency list for a file based on
-# the wikilinks within?
-
-
-def extract_substrings(input_string):
- # Get substrings between [[ and ]]
- pattern = r'\[\[(.*?)\]\]'
- matches = re.findall(pattern, input_string)
- return matches
-
-def process_strings(string_list):
- # If we are taking everything up to the pipe, we don't need if/else.
- return [s.split('|')[0] for s in string_list]
-
-def test_extract_substrings():
- assert extract_substrings("Here are some substrings: [[first]], [[second]]") == ["first", "second"]
-
-def test_process_strings():
- assert process_strings(["wikilink|title","WikiLinkOnly"]) == ["wikilink","WikiLinkOnly"]
-
-def test_integration():
- extracted = extract_substrings("Titled Wikilink: [[wikilink|title]]; untitled Wikilink: [[WikilinkOnly]]")
- processed = process_strings(extracted)
- assert processed == ["wikilink", "WikiLinkOnly"]
-
-def run_pandoc(input_file, output_file, format='html'):
- """
- Runs the pandoc command to convert a file to a different format.
-
- Parameters:
- - input_file (str): Path to the input file.
- - output_file (str): Path to the output file.
- - format (str): Desired output format. Default is 'pdf'.
- """
-
- # Construct the command
- command = [
- 'pandoc',
- input_file,
- '-o',
- output_file,
- '-t',
- format
- ]
-
- try:
- result = subprocess.run(command, check=True, text=True, capture_output=True)
-
- # Print stdout and stderr
- print("stdout:", result.stdout)
- print("stderr:", result.stderr)
-
- except subprocess.CalledProcessError as e:
- print("Error occurred while running pandoc:")
- print(e.stderr)
- except FileNotFoundError:
- print("The 'pandoc' command was not found. Please make sure it is installed and in your PATH.")
- except Exception as e:
- print(f"An unexpected error occurred: {e}")
-
-# Example usage
-
-
-if __name__=="__main__":
- #test_extract_substrings()
- #test_process_strings()
- #print("all tests passed")
-
- base_dir = Path("/home/kyle/notes/rocketbowman/tiddlers")
- file = base_dir / "ElectricityAndMagnetism.md"
- with open(file, "r") as f:
- content=f.read()
- raw = extract_substrings(content)
- processed = process_strings(raw)
- print(f"Raw strings: {raw}")
- print(f"Processed strings: {processed}")
-
- # Run pandoc
-
- input_path = base_dir / (processed[1] + ".md")
- output_path = f"/home/kyle/tmp/{processed[1]}"
- run_pandoc(input_path, output_path)
\ No newline at end of file
+++ /dev/null
-#!/bin/bash
-basenames="$(find ./tiddlers -name '*.md' -exec basename -s .md {} \;)"
-outdir="./test"
-
-if [ ! -d "$outdir" ]; then
- mkdir "$outdir"
-fi;
-
-for file in $basenames; do
- {
- echo "---"
- cat "./tiddlers/$file.md.meta"
- echo; echo "---"; echo;
- cat "./tiddlers/$file.md"
- } > "$outdir/$file.md"
-done
\ No newline at end of file
+++ /dev/null
--- links-to-html.lua
--- From https://stackoverflow.com/a/49396058
-function Link(el)
- el.target = string.gsub(el.target, "%.md", ".html")
- return el
-end
\ No newline at end of file
+++ /dev/null
-$-- This is a comment; Use $$ for literal $
-$-- Details for writing this template can be found: https://pandoc.org/MANUAL.html#templates
-$-- ${foo} or $foo$ is an interpolated variable
-$-- variables come from YAML front matter (or command line)
-$-- ${if(variable)} conditional text ${endif}
-$-- ${for(foo)} do thing $foo$ ${endfor}
-$-- ${template-name.html} includes another template
-$-- You can use pipes to transform variables if needed
-<!DOCTYPE html>
-<html>
- <head>
- <meta content="text/html; charset=utf-8" http-equiv="content-type">
- <title>$title$</title>
- <meta content="width=device-width, initial-scale=1" name="viewport">
- <!--<link href='../../assets/css/normalize.css' rel='stylesheet' type='text/css'>
- <link href='../../assets/css/space-sakura.css' id="sakura-css" rel='stylesheet' type='text/css'>
- -->
-$for(author-meta)$
- <meta name="author" content="$author-meta$">
-$endfor$
-$if(date-meta)$
- <meta name="dcterms.date" content="$date-meta$">
-$endif$
-$if(description)$
- <meta name="description" content="$description$">
-$endif$
-$if(tags)$
- <meta name="keywords" content="$for(tags)$$tags$$sep$, $endfor$">
-$endif$
-$-- <link href="atom.xml" type="application/atom+xml" rel="alternate" title="Sitewide Atom feed" />
- </head>
- <body>
- <nav>
- $navigation$
- <div style="text-align: right">
- <a href="../index.html">Index</a>
- </div>
- </nav>
- <header>
- <h1>$title$</h1>
- </header>
-$body$
- </body>
-</html>
\ No newline at end of file
+++ /dev/null
-# Design philosophy
-* Few dependencies
- * use pandoc features itself when possible
- * use pandoc filters for structured processing
- * use pandoc-lua for general-purpose scripting
-* Separate framework from content.
- * You can link content into the main content directory
-
-# To Do
-
-## Figure out Images
-
-* Images are part of content and should be linked in.
-* Images might be their own thing or part of a subdirectory. (e.g. public/private)
-* Figuring out how, in the Makefile, to copy images/assets might be tricky.
-
-## Improve Index
-
-* index.sh is hardcoded and janky - it should probaby leverage a pandoc-lua
- and/or pandoc templates.
-* (Stretch) Should acknowledgements be a template?
-
-
-## Navigation Improvements:
-* Enhancement: Create an index/nav item per directory (and eventually keywords?)
- * (Defer) About - add acknowledgements
- * (Defer) Summaries - index
- * (Defer) Figure out other categories.
-
-## Make Deploy
-* Figure out a `make deploy` with a `.env` file.
- * Serve on push. (If using git hook in rb, use .env file)
-
-## Clean up / Refactor
-* Try to decouple hardcoded things
- * index and template use different hardcoded paths to CSS.
- * (Stretchier) Should I mention Pandoc (def), GNU Make (prob), VSCodium (prob not), Foam (prob not), Debian(very prob not)?
-* Can I centralize config? A `make config` would be nice if it includes
- static content (like `author="Kyle Bowman"`) and dynamic content like
- `files=$(ls build)`.
-* Index.html will eventually need to be renamed b/c it's an "index", not the landing page.
-* (Stretch) Reformulate my templates based on jgm's templates so I can
- merge updates easily.
-* Extract lessons from `experiments.md`.
- * I'm torn about where to put these. In the project or in my notes?
-* (Stretch) Formalize demo and add tests
-* (Stretch) Add a hotkey to strike through a line in a to-do list.
-* (Stretch) Start building a CLI library that helps me manage md files.
- * Hard wrap the MD files themselves.
- * When a bullet point wraps, the first letter of the wrapped line ought to
- align with the first letter of the leading line instead of aligning with
- the bullet point. (Like this really long bullet point.)
- * Spell check
-
-# Feature: Interactive Terminal/Markdown Experience
-
-I want my editor to be able to send and receive info from my terminal in
-order to create an interactive writing/experimenting experience. Here are some
-ideas:
-
-* For many things, I want to target a line, for others an inline element,
-and still others, a block element.
-* From an editor, I want to be able to do the following to each target
- * Copy a target to the clipboard
- * Send a target to the terminal (and run it?)
-* From a terminal, I want to be able to:
- * Copy a command to the clipboard
- * Send a command to the active tab.
- * Copy the output to a clipboard
- * Send stdout to the active tab.
-
-# Feature: Tangle and Weave
-* When rendering my notes, I want to be able to tangle and weave the notes in
-the sense of Knuth's Web literate programming framework.
- * Weave creates doc from source
- * Tangle creates a program from source
- * Code blocks should support filename
- * Bash should support setting PWD before running. (And probably env vars
- in general.)
- * I have no idea how this would work.
- * Maybe, you ought to just supply a .env file whenever you run the
- command to extract the code.
- * Both should be able to be supplied as a variable so it's executable from
- another machine.
\ No newline at end of file
projects / jetsam.git / commitdiff