olav

I wonder what makes this a _knowledge base_ as opposed to a flat file CMS?

A few months ago I left Evernote for my own implementation because I felt that Evernote gave me too little expressive power: No hierarchy, no typed relationships, no plugins. Basically, I was looking for a combination of outliner and concept map, combined with easy image handling. Plus, I wanted to easily add _applications_ like an ebook library, journaling, timelines of events, and generation of static websites and presentations.

I am a huge fan of simplicity and even toyed with PicoCMS by the same author as Raneto. Ultimately though, at least for me, a combination of a simple mysql database with markdown as content format gave me the power I wanted for my personal knowledge base, https://knowfox.com

I collect appointments from Outlook (sigh!) and set a theme for the day in my private journal, using my own https://knowfox.com for this.

I remember the joy of writing a 200 page book in FrameMaker on a smallish SPARCstation in 1994. Even in 1998 it was easy to convince my boss to license FrameMaker for Windows as writing software. Word was still too buggy to write anything exceeding a few pages or with embedded images with it. Sadly, Adobe never marketed FrameMaker to a mass market.

Paul, thank your for your reply. I currently go through the tutorials at https://microbit-micropython.readthedocs.io/en/latest/tutori... and think they are a good starting point for me. One thing I am a bit nervous about is whether a block-based environment would be helpful for the first steps. Espruino with its Blockly-based editor has a slight head start here.

Chosenreich is my port of the Storyworth site by Nick Baum to the German language. It got conceived when my mother gifted me one of those printed Books "Papa, erzähl aus deinem Leben" that seem quite popular in Germany.

I find the topic of entangled lifelines quite fascinating, and actually have another project that shows key events in multiple lifelines concurrently on a single page: https://entangle.de/

Two thoughts:

(1) Much of the complexity of the OP's example is due to the fact that the template language they use, Twig, does not abstract HTML. If they would use a higher level templating language, e.g. Jade (http://jade-lang.com/) much of the need to have such things as his proton pattern, would not even arise. Another attempt at a living styleguide generator, http://bedrock.mono.company/ does just that.

(2) The very necessity to discuss atom vs. molecule makes me think that maybe the distinction is not such a good idea after all. Harry Roberts in his ITCSS has just "components" https://www.youtube.com/watch?v=1OKZOV-iLj4 . The other layer that Harry has, "objects", is subsumed under "atoms". This leads to another round of fruitless discussions.

What a sharp observation. I had one at http://dreitipps.de (yes, German). when I worked with my colleague of sweetbits at a startup for generation 50plus.

In my eyes, using CamelCase is a kind of cargo cult, based on the fact that the programming language Smalltalk used it. C++ adopted the style and moved away from the predominant use of underscores in C. So, people who want to be seen as modern and object-oriented, are biased to use CamelCase to stress their competence in things OO.

Strange, I made a very similar thing a few years ago at http://dankbarkeit-ist-nicht-erforderlich.de/

Even if the quote is by Elon Musk, I assume it is not him personally that works like this, but maybe some of his co-workers, certainly not for prolonged periods of time.

Does the new outlook.com support tags in addition to hierarchical folders? This is what I love about GMail. Plus, I generally hate the way the MS WYSIWYG editor has a live of its own and makes quoting of passages from received emails into multi-font nightmares.

-- Olav

Does the new outlook.com support tags in addition to hierarchical folders? This is what I love about GMail. Plus, I generally hate the way the MS WYSIWYG editor has a live of its own and makes quoting of passages from received emails into multi-font nightmares.