From 6053d313ce3abe876c7d05574effab438ce5e410 Mon Sep 17 00:00:00 2001 From: Zhiming Wang Date: Fri, 8 Jan 2016 11:21:54 -0800 Subject: Markdown source files: Use ... to end YAML metadata block Also add a newline after the metadata block. ... is easier on markdown-mode; if --- is used, the line immediately above it will be treated as a setext header and highlighted, which isn't so easy on the eyes. --- source/blog/2015-06-23-all-problems-solved.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'source/blog/2015-06-23-all-problems-solved.md') diff --git a/source/blog/2015-06-23-all-problems-solved.md b/source/blog/2015-06-23-all-problems-solved.md index 3894246b..f3d162f7 100644 --- a/source/blog/2015-06-23-all-problems-solved.md +++ b/source/blog/2015-06-23-all-problems-solved.md @@ -2,7 +2,8 @@ title: "All problems solved!?" date: 2015-06-23T21:47:07-07:00 date_display: June 23, 2015 ---- +... + The project I've been working on intermittently over the past month, [`pyonedrive`](https://github.com/zmwangx/pyonedrive), a OneDrive API v1.0 API/CLI client, is now quite satisfactory in terms of its feature set[^1], so today I'm thinking about what I should work on next. Of course there's [a lot more I can do](https://github.com/zmwangx/pyonedrive/labels/enhancement), but what is done already encapsulates 95%+ of my daily usage; moreover, as everyone knows, refining an existing project is not as exciting as starting a new one and making something happen that is previously tedious or impossible. [^1]: In fact it already exceeded my original expectations — `pyonedrive` started out as a [bare bones batch uploader](https://github.com/zmwangx/pyonedrive/blob/4d21308545ec1462c3892b9ca25300042f1ccb81/README.rst). -- cgit v1.2.1