From: "John O'Regan" <john.a.oregan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: cmdPost - a Windows command line blogging client for WordPress.com
Date: Thu, 15 Jun 2017 15:15:37 +0100 [thread overview]
Message-ID: <CALwjjMinavd8iNvQH5aP5G-Pj4-LqrMrZhAt6kopDbrHnSU8Cg@mail.gmail.com> (raw)
Hello All!
I've been working on this on and off for far too long, but cmdPost 0.1
is finally here. As the Subject line says, cmdPost is a command line
blogging client that runs from the Windows cmd prompt.
Q: What is cmdPost?
cmdPost is capable of creating new blog posts, or updating existing
ones. In the latter case, only the details that have changed since the
last update will be uploaded.
cmdPost enables you to keep a copy of your blog posts on your local
system. This allows you to edit posts offline and upload the changes
later. It also has the advantage of making it easier for you to
migrate from one blog host to another, or to post to multiple blogs at
once.
Q: How does it work?
cmdPost works by opening the markdown file containing your blog post
and looks for a specially formatted header block at the start of the
file. It scans the headers for meta information such as title, date,
status, etc.
The program then passes the body of the file (ie, the markdown
content) to Pandoc for conversion to HTML.
Lastly, the meta information extracted from the header block along
with the HTML is assembled into an XML document, which is posted to
your WordPress.com blog.
Q: What are the prerequisites for cmdPost?
To run cmdPost, you'll need:
- Windows XP or later
- a free WordPress.com blog
- Pandoc installed on your computer
- a working knowledge of markdown
Q: Where can I find out more?
Don't panic! Full documentation explaining everything is on the
cmdPost website:
https://johnoregan.github.io/cmdPost/
Setting up cmdPost isn't too difficult, and you only have to do it once! ;)
Q: Where can I download the latest release of cmdPost?
The direct download link to v0.1 is:
https://github.com/johnoregan/cmdPost/releases/download/v0.1/cmdPost.zip
Happy blogging! :)
Constructive feedback would be gratefully appreciated.
John
reply other threads:[~2017-06-15 14:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALwjjMinavd8iNvQH5aP5G-Pj4-LqrMrZhAt6kopDbrHnSU8Cg@mail.gmail.com \
--to=john.a.oregan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).