Blogging from an outliner

If you want to blog from an outliner, I suggest the first step is to get the outline data to flow out of your editing tool in OPML, and then write your publishing software to build the blog from the OPML. That way you won’t be locked into your editor or publishing software.
There are lots of approaches to both writing and publishing. You won’t get the benefit if you don’t have a strong basis for interop.
Silos have a long history of being bad for progress.
For most of the last 26 years I’ve been writing my blog in an outliner. I’m glad that other people are interested in this now. Let’s build a new community around this idea. 😉
The rest is in a Twitter thread.

Original URL:

Original article

Microsoft’s GitHub Releases ‘Visual Studio Code’ Extension Allowing Editing Without Cloning Repositories

A new extension for Microsoft’s code-editing tool, Visual Studio Code, “allows you to open, edit, and commit back to source-control repos without having to clone them on your local machine,” explains a new video.

A Microsoft blog post calls it “a new experience that we’ve been building in partnership with our friends at GitHub to enable working with source code repositories quickly and safely inside VS Code.”

In VS Code, we’ve offered integrated support for Git from the very beginning, and we’ve been supporting many other source control management (SCM) providers through extensions. This has allowed developers to clone and work with repositories directly within VS Code.

However, a large part of what developers do every day involves reading other people’s code: reviewing pull requests, browsing open-source repositories, experimenting with new technologies or projects, inspecting upstream dependencies to debug applications, etc. What all of these have in common is that as

Original URL:

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: