added a !meta page. this proof of concept integrates with the weewiki !zettelkasten I am developing to produce something similar to this !feed.

I am loving how organic this !zettelkasten is in !weewiki. the key value structure I'm using is so simple and allows for many structures to emerge from it.

with the addition of crate in weewiki, I finally found an opportunity to add some words to the !sqlar page #updates

implemented initial crate import in !weewiki. one step closer towards !sample_curation

I've got a good feeling about the !zettelkasten I'm building for !weewiki. I think it is going to grow legs very quickly.

with some scripting, I could probably use my upcoming !weewiki !zettelkasten as a drop-in replacement for !twtxt, and then generate the twtxt file. however, I think I am going to keep them separate for the time being. let them both grow to serve different purposes.

initial crate words imported in to weewiki source repo. no code yet, but it's pretty clear to me what needs to happen next in order to make an MVP. #updates

import functionality now works in the !weewiki zet #updates

some good initial progress with the !weewiki zettelkasten. messages can be made and tied to previous messages by providing partial UUIDs (that then get automatically expanded). basic export also works. #updates

added weewiki and orgparse to the #loom today [[/loom/weewiki]] [[/loom/orgparse]]. #updates

plans for weewiki: a zettelkasten-like interface, a microblogging platform inspired by !twtxt, and some utilities for managing collections of SQLar archives. #updates #halfbakedideas

!weewiki is now MIT licensed! can't believe I forgot to add it, considering the fact that it already has !janet in there. #updates #weewiki

I've recently been reading up on zettelkastens again, since it is very closely related to the ethos of a personal wiki system like !weewiki. The thing that interests me is the emergent patterns that come from linking things to things. Which is exactly the sort of solution I'm looking for !sample_curation. #halfbakedideas

@eli_oat happy to be an enabler :) I keep finding new uses for Janet as well! It has proven to be a remarkable extension language for !weewiki.

I really really need to add page navigation to !worgle programs exported to !weewiki wiki pages.

reworked the CLI argument parsing in !weewiki today. running weewiki with no arguments now prints all available subcommands. #weewiki

all files !monolith written using !worgle have now been automatically HTMLized via !weewiki. the top-level browser can be found [[/proj/monolith/program][here]].

A fragment of my !monolith program has been woven to a !weewiki from !worgle using !sqlite. Find it for now at [[/proj/monolith/wiki/][the monolith project page]].

well, it seems like I managed to automatically weave all the !literate_programming parts into a !weewiki! It's not all that helpful yet though, due to the fact that pages have autogenerated names like 'wm_000_0002'. A table of contents comes next...

Testing @!(ref "weewiki_sql" "page markers" "iterate_over_values")!@.

somehow get !weewiki pages rendered in !btprnt. maybe build a btprnt backend for links browser? #halfbakedideas

The master plan is to export the !worgle bits of !monolith to a !weewiki, then begin adding user-level documentation that is able to dynamically reference bits of source code as another wiki page.

!worgle -> !sqlite -> !worgmap -> !weewiki is kinda working?

while eventually I hope to get all of literate org parts of !monolith posted online as a self contained !weewiki, I've decided to post little pieces as self-contained documents. here is a copy of !trigvm, the toy VM used to power a rhythmic computer-sequencer controlled entirely from the !monome_grid

I really want !btprnt to be integrated into !weewiki somehow. Both can speak !janet, and I already figured how to embed PNG images inside of an HTML document. In small doses, it could be fun. #halfbakedideas

I'm so close to being able to get my literate programs written in !worgle converted into a self-contained !weewiki. #literateprogramming #worgle #weewiki

weewiki uses a custom org markup parser written in ANSI C to render the HTML. No emacs needed! my hope is to introduce a user-defined callback that can process these to allow for custom meta-commands.

a new fix to !weewiki will ignore all org-mode command strings by default. Now things like PROPERTY tags won't show up in the output.

documenting my experiments with twtxt/weewiki integration at the !twtxt_playground

Inline Janet means I should be able to make calls to functions defined in the config file. For example, the =ref= function is how I usually make wiki reference links. This @!(ref "wiki_index" "link right here")!@ should take you to my automatically generated weewiki index of all the wiki pages.

Technically not org, but weewiki org. So this means that I might be able to run inline Janet code? @!(prin "Hello from Janet.")!@

a new twtxt/weewiki feature: any word starting with '!' will translate to an internal weewiki reference in my HTML renderer. Example: here is my !wiki_index

there are also things like using #hashtags, which could be a useful tool to coordinate with weewiki somehow.

in particular, twtxt provides timestamps. weewiki doesn't really track the passage of time. it only wants to be a key/value database with org markup.

building a http server into weewiki has been more useful than I initially expected

weewiki org parser is getting a little bit better. fun bits are long gone, and now it is just tedious bugfixing.

added paragraph blocks and code blocks to weewiki HTML output. things look decent.

it is time to add a test suite for orgparse/weewiki.