vanderwal.net

Markdown Apps Loosely Joined

I recently posted about the different web browsers I regularly use, My Browser Family, and it makes sense to go through my different apps I use for Markdown in a similar way. My use is very closely tied to my Small Apps Loosely Joined mindset (part of the Shift Happed series on Personal InfoCloud). “Small apps loosely joined” focusses on having a core adaptable data structure (like markdown) and use different apps with written content where the app has helpful capabilities that are needed in a workflow or to focus on a type of work as a step in a workflow. Much like a woodworker picks up different tools to perform different tasks and doesn’t use a saw or chisel for all tasks, the small apps loosely joined model is similar. This works and has worked insanely well for 15+ years that I’ve leaned heavily on markdown.

I end up in markdown discussions rather easily it seems. The way I have taken notes in text apps with asterisks or dashes for bullets and the octothorp (you know, this thing #) for headings goes a long way back for me (starting somewhere in the 1990s). When I came across markdown in the early 2000s, after I had looked at and tried Textile Markup, but markdown didn’t fully connect. It echoed what I had done and offered more, but at the time I didn’t see the advantage of the added capabilities.

In 2010 and 2011 I started to shift much of my note taking and writing away from apps that were siloed and lock-in models. The flow from notes from a meeting, to my personal notes and annotations, and on to writing that gets shared out was a series of less than optimal apps that all had lock-in and heavy friction. Microsoft products not only had intentional lock-in but were continually buggy. I loved (and still do) Scrivener for writing longer pieces in it due to its managing notes and scraps related to the longer writing piece, but getting things in, as well as getting things out into my various sharing / publishing workflows had a lot of friction. At this time my parents were sick and passed on. When my mom passed my laptop hard drive took it as a hint and it too left the living world. I had everything backed up and I was working off the back up drive hanging off my Mac, and was waiting on a hard drive replacement, but needed something for notes for meetings (with banks, lawyers, and so much more) that I could move across everything. I nabbed an iPad for that mobility to take to meetings have files move across and back to my Mac. This tipped me into a full markdown life.

Like Many, Not All Markdown Goes to the Web

Markdown started by John Gruber to be an easy means of writing with light structure, while maintaining decent readability and to fit his model notes, which Textile didn’t fully fit. John created markdown and the markdown conversion to HTML as a matched set. Over the years many write markdown that gets converted to HTML, but around 2010 I’d see people were using markdown that never was converted to HTML. Markdown was what they wrote in as it was highly portable and editable from any text tool or markdown app and not in buggy and lock-in software. I noticed this in San Francisco on a trip where I stopped in a couple law offices to visit friends and the receptionist and legal assistants were mostly using markdown. This surprised me, as it wasn’t something I expected. Largely markdown for writing has been in tech adjacent roles and organizations. Later year seeing high school kids and college kids using markdown for their notes and paper drafts, then pasting to Google Docs was really impressive with the deftness they worked and how they managed everything. (A funny sidenote is many who went through school this way were appalled that Microsoft Word didn’t natively understand markdown). Markdown isn’t the parent’s use case any longer.

Today markdown for me only has around 20% that gets turned into HTML. Most are notes and documents that stay in markdown or turned into Google Docs, PDFs, text in Keynote presentations, and much more. Markdown is incredibly flexible with just enough structure to get converted as needed.

At First Many Apps Only Sort of Joined

This 2011 timeframe was the heyday of small light markdown apps. I picked up many apps and found a few that worked well. I was knee-deep in the markdown matrix table that Brett Terpstra maintained that showed the markdown app and the capabilities and compared what seemed like well over 60 apps. I used Simplenote, Byword, 1Writer, Ulysses, and Bear notes quite a bit and have kept them around but don’t use them as much due to friction for where and how they keep markdown files and some interfaces didn’t evolve. I also have used Working Copy, Git on iOS on Mac and iOS (iPad) for working on larger documents across devices and with others.

Moving to Less Friction for Markdown Loosely Joined

Apps that stayed around and were added in respected where I kept my notes and work. Most of the notes and writing stayed in a notes directory, but also were in project work. My notes directory on my Mac was linked out to iCloud so I could have access from my iPad or other devices. For a long stretch my basic notes app on my Mac was NVAlt, which allowed for tagging the markdown files, which meant that while they lived in my notes directory, I could aggregate all project work in the project folders, other media, and notes all with a file tag on Mac. This was fine until NVAlt stopped opening.

My Menagerie of Markdown Apps Now

My markdown notes that NVAlt sat over (which also included a folder from Notional use) had a few thousand notes when it stopped opening. But, the markdown notes weren’t owned and controlled by NVAlt and I could use nearly any markdown app I had to open and edit them. I wanted something very close to NVAlt.

Obsidian

In June 2020, after trying to find a replacement for how I worked with NVAlt I tried a few apps, but the one standout was Obsidian which slid perfectly into the exact role that NVAlt had for me. This role was to sit over the directory of notes and oversee them, but functionality on top of the markdown notes. Obsidian added even more capabilities (which most of my other markdown apps also adopted portions of over time). Obsidian is where my daily notes, drafts of longer pieces, meeting notes, and so much more go. Everything is relatively findable and refindable through backlinks (wikilinks) that are bridges between notes (but also with a plug-in Strange New Worlds - Obsidian Plugin I can see what other notes link to the note I’m linking to, and part of the magic is the note I’m pointing to doesn’t need to exist to see those links), tags to aggregate related notes with that tag, and search.

The other great advantage of Obsidian is transclusion, where one note can be added in as a view into another note. I can start a note in a meeting note or a daily note, then highlight a section and extract that section as its own note, but then transclude that note back in to show it where it was. This extraction and transclusion allows for that one piece of notes to mature and / or be included as a transclusion into other notes. The transclusions can also bring in a sub-heading into another note to show the section in the sub-heading. (I have a longer take on how and why I don’t use zettelkasten, which is similar to what I learned going into college for how to have far better study habits and write papers far more easily, but it also broke contextual understanding and really broke multiple contextual relationships).

iA Writer

My longer form markdown writing app is iA Writer. Often an idea for writing will start as something small in Obsidian (often in a larger note) and gets fleshed out a little there. But, when it starts getting longer I will extract it as its own note and then pick it up in iA Writer to take it farther. I love iA Writer as the interface is quite plain and it is just me and words and minimal structure. I often will create sub-headings early in longer pieces as outline structure to be filled in. Then it is just writing. The iA Writer app also has some light grammar checking (which fits my needs well), a quick preview to see your work as output that has some design and layout in the UI. It can be turned into a very minimal interface as well with focus on the line your cursor is on and just a few lines around that active line.

By and large, iA Writer replaced Scrivener and Ulysses as my longer writing app. The segmentation and notes capability in these other apps have made their way in as sort of similar forms into iA Writer (not everything, but enough for me). What largely caused iA Writer to replace the other two was very little friction getting my writing out into other outputs. Dragging the proxy icon to Marked (now Marked 3) is all that I need to get to HTML, styled PDF, or Word.

Marked (now Marked 3)

The Marked app, which is now in its 3rd major version, is the markdown conversion and clean-up app of choice. Marked has a lot of different capabilities, including proofing, writing statistics (like readability score and much more), writing support with proof reading, linting, and support for a wide set of markdown capabilities. Everything for using Marked for converting markdown to other formats is quite customizable and rather straight forward if you have some skills.

MarkEdit

The MarkEdit. app is one app I use as my default markdown file opener. It is like Mac’s TextEdit app, but focuses on markdown. It shows all of the markdown marks in plain sight. I find the showing everything raw is a good thing for review and understanding structure quickly.

I receive markdown files from others quite a bit, I also have access to other’s Obsidian vaults, and I have many markdown files that are spread all around my Mac and cloud environments. When opening one of these from search or a link I want to keep it outside of my Obsidian so they don’t get included and intermingled. This is really helpful reading and editing other’s shared Obsidian vaults as I can open, read, edit, and then close it while keeping clear of my Obsidian. If I want to copy something from my notes in Obsidian to another’s Obsidian, the two apps for two different environments look different, which helps reduce errors.

BBEdit

Another plain interface for markdown I use is BBEdit by Bare Bones Software, which supports markdown, but is the jack-of-all-trades text and basic coding tool. BBEdit is a go to for a lot of different text and coding needs where clearing out the cruft of an IDE or app is needed. I often open markdown documents in BBEdit when there are a lot of consistent text modifications I need to make. I have pulled in large outlines I have made in markdown and I need to do much work with nested levels in the outline.

Drafts App

I use Drafts for text and idea capture when I am away from my Mac. Everything from quick atomic notes (like where I parked, name of a book mentioned when at coffee, etc.). Drafts has long had solid voice-to-text for all Apple devices (iPhone, Watch, iPad, Mac) so it a great capture application. Drafts also has a highly adaptable capability for what to do with the note once captured, like sending it to my notes directory that Obsidian sits over. It is fully markdown capable. I can take a voice-to-text note on my Watch when driving, or invoke Siri and have it open Drafts to a blank not and tap the mic and leave a voice-to-text note that automatically is save and I can open it when I park and add some markdown elements and use and action to send it off to Obsidian, text message, or so many different end points.

iPad Apps

I started using markdown heavily, largely because my Mac hard drive crashed and I was taking notes on an iPad. I’ve gone through a lot of different iPad apps for markdown.

I have Obsidian, iA Writer, and Drafts, which I use pretty much the same way as how I use them on the Mac. Obsidian on iPad is a bit more limited, but still good for capture and modifications of notes in the directories I have it sitting over. I have Drafts always available as a slideover option off to the right of the screen.

I have Editorial for iOS as a relatively plain markdown editor. I don’t use it as much as I used to, but good to know it is there and it is quite capable.

The iPad also has small focussed apps for certain tasks. I use TextCase for changing capitalization in notes. I use Terminology by Agile Tortoise, which is the same developer as Drafts, as a really good reference tool when writing on iPad.

Trying a Couple Apps

There are a couple of apps that I’ve been trying on Mac, which may have a place. The first is Lettera, which is a markdown editor for Mac by the makers of Bear, which is currently in a limited beta. When I was using Bear notes app I loved the interface as it was clean, but what I didn’t like about Bear was the lock-in of notes in the app, as there was too much friction to use a note outside of Bear. Lettera is the markdown editor that is free of Bear. It still seems to default to a Lettera folder in iCloud, but opens markdown notes from anywhere. This may be a better reading and annotation app (it has easy to use callouts) for some of the uses I’ve used MarkEdit.

The other app is one I’m trying again as I used it 8 years ago (or so) when it was in beta and free, but became fragile, buggy, and would crash. It looked good and was rather simple. They changed from the free app to a paid app with the same name. I ended up with two versions with the same app with the icon and it was difficult to discern which was the flakey app and which was the good. Once the good version became pay, so I had neither working. This was Typora. In recent months many new to markdown have been talking about Typora and I get asked about it. Today I finally downloaded it again after deleting both of my instances of it a few years ago.

The current Typora has a lot of capabilities now, far beyond what it used to have. It has a similar interface, until you open settings then it has a lot of customizations. Typora can now cover a lot of ground. Much of it is covered in other apps I have, but I may find my current model of having different apps for different uses that are incredibly good for the purpose I use them is my preferred way of working. Having different apps helps me focus on what I am doing in that app to the markdown file and the task and focus needed from me for that task. To get to the same thing in Typora I would have to go to settings and make changes to keep that focus, but the context of the different app isn’t there. Moving between apps I will also keep the markdown file in multiple apps and see an edit in one instantly show in all the other apps (what good magic is this). Typora nice interface with additions for math UI (through LaTex) and charts (through Mermaid) may be a draw to keep it around.

Adjusting Daily Aggregation for Less Friction

Sunday I hit a point where my daily automations (which I layout in part here - My Automations Over the Ages and Today’s View in my morning process and weekly process) and placing the outputs into my Daily Dump note sections was really making for a lot of friction in my note taking / note making. Additionally, it was breaking focus and holding my concentration on what I was trying to capture in my note’s sections.

How Daily Dump Notes are Setup

My Daily Dump has 14 sections: Plans, Thoughts, Review, Read, Talked With, Listened, Watched, Productivity, Worked, Learned, Played, Ate, Health, Bought, and Added to a wishlist.

The intent with the subheads in my note is to quickly jump to the section as I run across something or am thinking through and idea or concept and capture the thoughts or what I consumed and ideas from it, so I can get back to it later in my notes. But, since this is markdown and in Obsidian I can take the notes with its subheading and text, extract it, and then transclude it (move it out and link it back in to show it in another note). But, having each day’s note relatively clean (the exception is the Plans section for things brewing and on the front burner to do are moved from the prior day’s note to the current day’s with a python script that keeps the completed tasks on the prior day and removes things not completed and moved them to today).

Friction from Adding Aggregation to the Sections

The daily aggregations pulled in things captured from various reading and copying or favoriting tasks that get automatically captured in Instapaper and Pinboard, as well as all the files I created and modified. I also have notes from Drafts that I capture on the go and tagged to get pulled in aggregated, as well as a list of things I watched online that I want to track, but also list of videos watched where I’ve captured the transcript in Readwise I may want to review (and likely do a further clean-up step).

All of this was getting aggregated into collective notes by type and transcluded into the relevant groups in my Daily Dump note. This added a lot of friction to the intent of my Daily Dump for quick easy drop into a section and capture a note and then after sort out how I may handle it. Add to this, Sunday my Weekly Review runs and captures all of this from the week and compiles it into one note so with a heat map at the top so I can review it to see what I’ve been doing and find things to cut back on or put focus on for the upcoming week. The Weekly Review was transcluded into Productivity, which is ironic as all of this adding of aggregation transclusions was making me really unproductive.

The Fix to Bring Back Focus and Quick Capture

On Sunday I had enough of the friction and took time to sort out a solution. I liked the capture and the ability to scan through and find things I need to continue working on or make a change on, but having it in my quick capture notes area made it tough.

I added a “Review” section just under Plans and now all aggregations and transclusions go there. The best part is when I’m not reviewing it, a heading in Obsidian can be collapsed, which gives me focus on everything else.

On Sunday I did a quick manual restructuring of my note by putting everything aggregated into the Review section and then collapsed it. This was a magical focus trick.

Updating the Python Script that Automates Transclusion

Sunday I did the first edit of the python script that takes the aggregations notes created earlier in the moring and transcludes them in and repointed them to not go into the other categories, but all go into Review. This hasn’t run perfectly yesterday nor today (it works when I trigger it to run manually, but not from the trigger to run the script), but it is getting closer.

Protecting Focus is Key

Protecting focus and being able to quickly shift focus and be productive is key and has been something I’ve been working to do since I was a kid. Over the years I’ve learned the distractions and how to pull focus and calm back in. Removing the friction from abundance of information already in where I needed clean space to quickly capture created the large problem.

Now my big next step is sorting out the time to actually get a good weekly review done from what I’ve aggregated. The capture has been really good, but I just need to get better about protecting time on Sunday (or move this to Saturday) so I can sit and focus on what was done, what I can reduce and what needs focus to get done.

My Automations Over the Ages and Today’s View

For a few decades I’ve converted regular manual tasks into automated tasks for many things. I use short code keyboard conversions with TextExpander (TextExpander), Alfred (Alfred), Keyboard Maestro (Keyboard Maestro), Hazel (Hazel by Noodlesoft), Apple Shortcuts, and a couple other small apps and services. But, I also have quite a few scripts in python and Ruby, but a few pure bash scripts. I have a handful of apps that use Claude Cowork (Claude Cowork | Claude by Anthropic) on a schedule and used where the data is not always standard, so it aggregates and structures the data where it often later gets processed by python.

I started building and running automation scripts in the 1990s to handle tedious tasks with multiple steps, or would likely be victims for typos, and which I was handling daily. A task that would take 3 or more minutes (often longer) and had structured stable data I could search made it viable to become a script and automated. I had them to filter email to folders, filter downloads to common folders / directories, and one to turn off audio for the evening which monitored Twitter every 30 minutes for my nightly signoff (“off to read and sleep - zzzz”) and it would mute audio. I’ve had a few for audio that would capture podcasts I was on for a local copy during recording that took just one button click to set Audio Hijack Pro properly and it just worked.

Moving to the Current Adaptive Flows

The last six months (or a little more) I’ve been building aggregators to capture what I’ve done the day before (and the week prior for a manual review). I’ve also automated my morning Obsidian (Obsidian) setup, so that my daily note (or Daily Dump for my notes, in my vocabulary) templates are created for the week ahead with a python script, rather than creating a new note and use a TextExpander snippet to build the structure each morning. But, doing this I realized that I could take my daily task list and the list of potential tasks I keep at the top of my Daily Dump and script the moving uncompleted items to that day’s Daily Dump from the day prior, but also quickly run a calendar scan for the day with Claude and the BusyCal MCP to have my known items at the top of the note written directly in the note. The completed items and checked off were left on the prior day’s Daily Dump in their sections.

In order to run the scheduled python scripts I need my laptop to be awake in the background (but it still the screen remain locked) so to run early morning tasks. I found PMSET as the key to handle the wake-up for the first run and have a python script handle the remaining wake-up processes for that day.

I now have a mix of Claude Cowork Skills (which if I sort out the data is stable enough I convert them to python for consistency, speed, and sustainability) and python scripts that pull my prior day’s files created and worked on list, my items in a feed of the prior day’s additions to Instapaper, Pinboard, and a list of new items in DevonThink as PDF (with links to the PDF as well as a working URL to the source of the item), a list of Readwise articles and video transcripts, and videos I liked and sent to my personal instance of Slack. These lists are in markdown and placed into the directory Obsidian watches over. Most of them a little later in the morning are transcluded into my Daily Dump note for the day where I read through them.

Morning Process

My morning process is to read through what was done the day before and edit them to add links to other resources in Obsidian and write notes. Often I have some entries that will turn into that day’s list of things to do or one of the “potentials” list. I will take items that need to be their own item note or be included into a concept note. This keeps the items fresh on my brain and connecting things to where I can get back to them more easily.

I write this today, as this morning I found my morning automation hadn’t fully run properly, because my Sunday evening script to create the week’s Daily Dump notes didn’t run as it was a cronjob and I was cooking with the laptop asleep so the job didn’t kick off. This morning I converted the cronjob to a launchd task instead and to run on Sunday during another automated wake open window.

Weekly Aggregation

Sunday’s I also run a weekly wrap-up, that pulls everything done for the week. I’m finding this is a bit too much information for a quick review and a manual assessment for the week where I aim to map out things for the upcoming week. It is a bit too much information overload. I don’t know what I’m going to do about it. Now that I have things automated and aggregated I need to rework my human side of things.

The Value of the Automation

The goal of my automations is to give me time back and remove the manual and grunt work so I can do the thinking work. I’ve done this with personal life and work life (and large systems and projects). The current round of automation and aggregation surfaced that I am doing more than I thought I was doing. Another goal is to give more time to do the human thinking and the projects and work needed. I do this so I can do the creative human work and the human thinking work (I find large errors in summarization in nearly all generative AI and creative work so I keep that at bey and use it for grunt work that I check). The scripted automations don’t need the hand holding and I have some occasional test run to check on them to see if they need attention and honing.

Weeknote Considerations

One of the things I deeply enjoy reading each week is other people’s weeknotes. Well, not everybodies weeknotes. I have 4 to 8 different people who share weeknotes that I check in on. It is like getting the weekly catch-up and it is calm and quaint (in the good way). I really like them and I get concerned if they miss a week.

For a while I was posting weeknotes (found with the tag: Weeknote :: Off the Top :: vanderwal.net). I posted 25 of them. They were recaps of things I found of interest and wanted to share in that prior week (or so). I stopped posting them as the timing was tough at the end of the week, but the creation was getting easier as they just were things I’d pull out of my daily notes to myself in roughly the same categories.

Not Sure If I’ll Return to Posting Weeknotes Again

I am really not sure that I will return to posting weeknotes again, but it is a rather Ouroboros-shaped reason. In the past year or so I set up local (on my laptop) search of my own blog, which moved to the Lab - vanderwal.net, and then on to my blog portion of my site.

In searching my own content to see if I’ve posted on a subject before, I would find what I was looking for in a weeknote post. But, going to the post it was buried in the muddle with other things. I also was finding using categories to find related content when it was surfacing weeknotes and I’d have to dig in the weeknote to find the relevance it was connecting to. Both of these bothered me and from a finding, pointing to, and sharing with others perspective. I really think it is a less than good experience.

The weeknote for me was a means to get back to posting to my blog more regularly. I joked that Twitter ate my blog in 2006 (I’ve seen my data and it sure did). Then moving to a better note tool and note making daily that had me writing again in pretty much my old manner like blogging, but I just wasn’t posting. I didn’t complete the workflow for it to be a blog post. I would write and reuse locally, but the next steps in a blogging / sharing workflow did’t happen. A little over a year ago when I updated my blog management tool, that was part of the backend update, that made posting easier and I was posting a little more. But, when I’d look it was a week or more stretches between posts and I’d been writing like I was blogging, but I was my own reader.

Using Blaugust (Going in on Blaugust :: Off the Top :: vanderwal.net) as impetus to get the workflow back part of my habit of finishing the steps is a good thing for posting, I think.

My Notes to Post Workflow

I’ve kept notes in text in a directory since 2003. It started as plain text along with dash or asterisk bullets. That turned into using Notional and then NVAlt at some point. When NVAlt stopped opening I set Obsidian to watch over the directory in June 2020 and I’ve not looked back. I did a quick modification and the notes that weren’t in markdown (I fully shifted my writing to markdown in 2011 when I had a hard drive crash and access to application that wrapped notes made my notes something I couldn’t open for a few days and with my parents passing and needing notes, a proprietary container was no longer an option – actually it is a bad idea from the start).

I keep a Daily Dump markdown note that is structured with sub-headings as prompts and keep notes in there. One of the things I love about Obsidian is the ability to have transclusions, so when I am writing in my daily note, but it makes sense to have it as a stand alone note to reference, or to become a blog post, I just highlight the segment and right click to export that to a new note and it links to with a backlink (think wiki link), but putting an exclamation mark in front of it brings that note into the daily note to show it.

This means I can create a note that has a “blog-shape” to it that started in my daily note. It is in markdown and I have a title on it and other metadata. It lives in my note directory. I click the ellipses in Obsidian’s right corner of the panel to “Show in Finder”. The finder window for Mac opens with the markdown note highlighted. I right click on it (I don’t use a mouse, so double finger tap is actually what I do) and select to open the file in iA Writer. iA Writer is my longer writing app, but also what I review and edit something that I will post (or transform to a more formal document). When that is done I drag the proxy icon for the file in the titlebar of iA Writer to the icon for the Marked app (Marked 3) in my Dock and it opens and I select “preview toggle” and it shows me very well structured HTML (it matches the scripting I did years ago to do much the same, but is much less hassle) then I highlight and copy and paste into my site’s blog management tool, add the title and select categories and it is posted.

The multiple apps all are working with regular markdown all in the same file. I modify something in one and it changes in all the other interfaces. I own the files and they can be opened in any text app or any markdown focussed app. IA Writer I really like for calm focussed writing, reading what I’ve written, and editing. Marked (now Marked 3) just does a nice markdown conversion to very good standards compliant HTML, plus adds the sub-header IDs for anchor links, which I used to do mostly by hand when I ran my own convert to HTML scripts. Marked also can transform markdown to structured Word, well designed PDF, and more, yet I use it for the one simple task.

In my blog management screen, I manually trigger the build of my RSS and then trigger syndication notifications after I have run a manual visual check and test all the links. Once I’ve finished writing it is 2 to 5 minutes to edit in iA Writer and post.

My Writing Process with Obsidian

A few times lately my writing process has come up as it relies heavily on markdown for portability, longevity access, flexibility, and using the Shift Happened – Part 2: Small Apps Loosely Joined – Personal InfoCloud. The Small Apps Loosely Joined concept is something I use heavily for many things, but for writing the use of markdown I use the concept quite heavily.

Recently in a IndieWeb gathering, James who runs and writes James’ Coffee Blog shared his process and workflow for writing through to posting on his site, which was similar to my own process, but uses different tools along the way. He had something in his process he was looking to improve upon so I walked through my process.

My Process has Morphed Over the Years

My current writing process is an extension and evolution from my initial processes that trace back to college. But, it was in the late 1990s and early 2000s that my current process formed iterated upon. My early writing for blog posts and articles all start in markdown, which years back was well structured text and sometimes HTML for the structure.

My notes prior to formal blogging (started at the tail end of 2000) that I posted to my site were all hand coded HTML (or raw coding). If a note was going to turn into a blog post it quickly was marked up, and often as I was making the note or post.

Automate Early

One of the core elements I learned in the 1990s was to automate early for anything you can automate, use the tools you have at hand to help yourself be more productive. Most of my writing up through around 2010 was text and then quickly turned into HTML markup, as it is simple to do. But, the tough part is connecting related content, which is why I created my personal content management system (CMS) to run this vanderwal.net blog in 2000 and fully put it to use in 2001 (I used Blogger for a bit early on). Taking rote patterns and automating them was a great addition to help my process in 2000 to now.

In 2010 I shifted all of my note taking to markdown as moving across apps and devices made using other note making methods difficult to access and use. This shift to full markdown for notes, helped my writing move from notes to posts and articles much easier.

Markdown Workflow Process

Today and the last 5 years my notes start most often in Obsidian (and on mobile in Drafts, which is great for the good practice of get it out of your head and then sort out what to do with it). I have many notes flagged as “blogfodder” and track those through the writing process and moving them from a stub of an idea, to draft, not posted but ready, and posted (which includes a link to where it was posted). I’ll have another post about my new blogfodder process, which I’m really liking.

The writing starts as a note and gets fleshed out, if it is needed. If it is a short item I may stay in Obsidian and then grab and drag the markdown file in the Finder to the next step (I will get to this shortly).

Quite often I will leave Obsidian and from it click to open the Finder with the markdown file highlighted and then open that file in iA Writer - iA Writer, which is a nice focussed writing app for markdown, with additional capabilities. I often use the old journalism marker for needs attention (tk!) or “to correct” for things that need links, fact checks, or reference notes. Once I’m happy with the writing and structure in iA Writer (or Obsidian) I move to the next step.

Move to Prep for Posting

In years past I would take the markdown and quickly take the markdown structure and convert it to HTML markup by hand. Around 2013 or so I started scripting this transition, but the script was fussy. I’m not sure when, but it wasn’t long after this, I ran across Marked 2 - Marked 2. I think I started using Marked to convert markdown to PDFs and Word documents (for things that need to be sent out for formal article transformation in publications from Word). But, I realized Marked 2 had really good markdown to HTML conversion that was as good as my script, but not fussy. As I moved to Obsidian with properties in front matter and a footer with blogfodder tracking, it can remove all of that with ease, translate external links very nicely, and remove all backlink notation.

It is often in Marked 2 that I find markdown problems or the tk! marks. Marked 2 also includes some light grammar checking, which I appreciate and I’ll work through those suggestions. Then I flip to the HTML markup view and make edits, if needed, there.

Open My Blog Entry Form

Once I’m happy enough with the post I open my blog entry for for vanderwal.net or Personal InfoCloud and paste the HMTL into the form for the body of the post. On vanderwal.net I add in the title, location, type of post (these days everything is a weblog, but in the past it was more diverse), then select the related categories and submit it. Then I just to look at the post and review it again. If it needs an edit (up until July 5th) I would go into the database and make edits to the post there, but now have an edit process in my CMS (after 25 years, I figured it was about time). Once that is done, I go click to generate the RSS feed for the site, and send out alerts to services that share out links and summaries farther.

Wrap-up of the Workflow

This workflow is now done, except for seeing spelling errors or things not right and needing tweaks.

The process that starts in a markdown note, then progresses through to a more formal writing process and flow. I replaced a lot of manual steps that I didn’t think were difficult nor took a lot of time and automated the steps that do exactly what I had been doing with the same level of care, but saving time and reducing errors.

I don’t use AI in any of this writing process. I run across too much AI written content that is lifeless and doesn’t sound like the writer any longer. I’ve stopped reading many colleagues who used to have great ideas and a great personal voice, but are now just bland slop through the use of AI that tilts at, but doesn’t achieve mediocrity.

I have my own quirks and writing patterns, which I am fine with. I don’t write to impress, but to get honest ideas and understandings out. I blog and write to find connection with others of like or similar minds.