experimental 'microwiki implementation' / 'mini CMS'
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Takumi 6b4fec4d3a activitypub: version entry URIs, correct post body, thread entries 2 weeks ago
core activitypub: version entry URIs, correct post body, thread entries 3 days ago
core-ext-shortcuts publish only desired pages using tags 3 weeks ago
installer mostly finish debian installer 4 months ago
issues.bop activitypub: version entry URIs, correct post body, thread entries 3 days ago
render activitypub: version entry URIs, correct post body, thread entries 3 days ago
render-ext-ap activitypub: version entry URIs, correct post body, thread entries 3 days ago
render-ext-pubgroup publish only desired pages using tags 3 weeks ago
rules separate out meta line parsers 2 months ago
template.bop complete opt-in formatting rules, atom feeds 6 months ago
tests activitypub: version entry URIs, correct post body, thread entries 3 days ago
.gitignore create simple Makefile installer 4 months ago
COPYING manually excerpt entries, publish single directory 5 months ago
LICENSE add README & LICENSE 1 year ago
Makefile create simple Makefile installer 4 months ago
README.md add publish targets 2 months ago
TODO publish only desired pages using tags 3 weeks ago
bop port to proper asdf system 6 months ago
main.lisp activitypub: version entry URIs, correct post body, thread entries 3 days ago

README.md

bopwiki (/'bop') is meant to be a simple "microwiki" implementation ─ a wiki-like system designed for recording very small thoughts and contextual connections between things.

the idea is to make something useful for concise summaries of complex knowledge, very simple issue trackers, a way to organise your mastodon threads, a place to draft ideas for longer webpages without publicly microblogging, etc.
(a teeny bit like tiddlywiki, but much more friendly to opening raw pages in a separate text editor and not necessarily needing both an entire backend engine + browser to view.)

it's fairly similar to a Zettelkasten system.

(for more on "microwikis", see the original mastodon thread:)
unrolled / original


"Documentation"

code files

bop has just been ported to a proper asdf system structure. This new code structure will be internally documented some time soon as it goes through the process of being fully cleaned up.

working features

(possibly incomplete list)

  • microwiki pages - simple text files named as their created time with optional metadata lines at bottom
    • open a new page in external editor - bop new
    • manually nickname a page outside of bop, e.g. "1602312899_test.txt"
    • list all pages visible from current directory - bop list
  • renaming pages
    • changing page nickname - bop rename test newname renames 1602312899_test.txt to 1602312899_newname.txt
    • changing page date - bop rename test 1412952899 renames 1602312899_test.txt to 1412952899_test.txt
  • edit pages by either their ID or nickname - bop open test opens 1602312899_test.txt
  • features for journalling
    • mark a page as today, or open it - bop today pagename, bop today
  • render page + replies to simple webpage - bop publish
    • publish specific defined groups of directories to a format, or to multiple formats in sequence (extension)
    • render pages to atom feed (experimental)

in-progress / planned features

Currently in-progress tasks are in the TODO file, and longer-term tasks are in the "issue tracker" folder, issues.bop.
You can use bop publish in that directory and open file:///tmp/issues-bop/index.htm to see an overview.

(An end-user documentation thread is also under construction inside issues.bop, though far from finished - see "0947217626_docs.htm" in the issues-bop folder.)

branches & updates

bop technically has two branches - my private branch unstable, and the public branch main.
This is mainly so I can endlessly amend commits on unstable until I lock them in, 'release' them to my public forge page, and start the next update.
so, if the README you see here looks suspiciously outdated, it's somewhat likely I'm sitting on an unfinished update that will release later, and you only need to be patient. (or bug me with questions)

bop is now almost able to install all its dependencies using the installer directory.
This is not quite ready, but when it is, you will be able to install a "development" version of bop on either manjaro/arch or debian using make && make install.

PKGBUILDs for building bop-related arch/debian packages live at codeberg.org/...bop-ytp-pkgbuild.
There may also eventually be a regularly-updated place to get binary "non-development" packages (like a PPA), but my system for putting one up on a git host is still too experimental right now.

License

bop is released under the GPL3 in anticipation of it either integrating with or replacing spectrom.