Writing Markdown Blogging Guide

本文是使用Markdown撰写博客的指南。介绍了Markdown的概念,对比了传统的所见即所得(WYSIWYG)编辑器发布HTML的方式,指出其易产生劣质HTML、不便于移植和速度慢等问题。阐述了使用Markdown的优势,并说明了将Markdown转换为HTML发布到博客的几种方法。

title: “Writing Markdown Blogging Guide”
date: 2021-01-12T10:42:25+08:00
draft: true
tags: [‘markdown’]
author: “dadigang”
author_cn: “大地缸”
personal: “http://www.real007.cn”

关于作者

http://www.real007.cn/about

A guide to using Markdown to write blog posts

Introduction: What is Markdown?

Markdown makes it possible for anybody to structure their text and publish it in an electronic format. The most common electronic format is HTML, but you can also use Markdown to produce other formats, such as PDF.

For the purposes of this guide we’ll stick to HTML.

Markdown is simple, quick, portable and efficient. To really appreciate why you should use Markdown, it’s best to take a look at the old fashioned way of publishing websites.

Publishing HTML the old fashioned way: WYSIWYG editors

If you publish a web page you publish HTML. This may come as a surprise – when you wrote that blog post you didn’t write this:

<h1>Why writers should use Markdown</h1>
<p>Markdown is quick, simple and portable. It's also extremely elegant and very cool. You need to know Markdown.</p>
<p>WYSIWYGs are the past. They're slow and bloated.</p>

But that’s what you ended up publishing.

What happened?

Let’s say you use WordPress. When you write a post in WordPress you use a What you see is what you get (WYSIWYG) editor, which is like a simple word processor. You write text, select bits of it and then make those bits a heading, list or quote.

WordPress then takes your text and converts it to HTML. Why? Because browsers need HTML to understand the structure of your article. HTML is the language of web pages.

Why use WYSIWYG editors?

HTML isn’t code. Anyone can look at HTML and understand what it’s doing.

Take our example. The text between the

tags is a first level heading, which the browser will display in a large, bold style. The text between the

tags is a parapgraph ( p for paragraph, see) which the browser will display in a normal style.

There are 5 or so commonly used tags. Once you know these you can pretty much write HTML.

However, writing HTML is laborious. As most people have some experience of using a word processor, it makes sense to replicate the Word experience online.

Problems with WYSIWYG editors

WYSIWYG makes it easy to write poor HTML

Writing HTML is simple, but it is important to follow the rules.

When you use a WYSIWYG editor, it’s easy to get hung up on the text’s appearance rather than its structure.

In order to make their text look right, writers can misuse headings, quotes and blockquotes. A first level heading not only looks bigger than a paragraph, it has a different meaning to a browser.

This might not seem a huge problem, but think about who – and what – might read your web page.

If it’s a visitor using a screen reader a misplaced

will make your page confusing. If it’s a search engine trying to figure out what your page is actually about, it may get the wrong idea, making your page hard to find.

WYSIWYG isn’t portable

Let’s say you have to move to a new blogging system, or you want publish some of your blog posts in another format, such as PDF or ePub.

If you’ve used the WordPress WYSIWYG editor all your posts are in WordPress’s own format.

Now, WordPress is a good web citizen. It makes it easy to export your posts in an open XML format. But you’ll still need to find a tool that can convert this complex XML into your new system’s format, or into another file format.

It’s far easier to move plain text, Markdown or HTML between systems and formats.

You can also store all your content on a USB or in a Dropbox folder.

WYSIWYG isn’t that quick

If you write a lot chances are you’ve got used to using your keyboard to select bits of text and copy and paste.

Although WYSIWYG editors are quicker than writing HTML, you still have to navigate your way round a web page and select formatting options from a dropdown menu. You’ll be switching between keyboard and mouse a lot.

The more you keep to the keyboard, the more efficient your writing.

Enter Markdown: A quicker, more efficient way to publish web texts

You write Markdown in a text editor. Think of it as an easy to use shorthand for HTML.

Take our HTML example. In Markdown, it would look like this:

# Why writers should use Markdown

Markdown is quick, simple and portable. It's also extremely elegant and very cool. You need to know Markdown.

WYSIWYGs are the past. They're slow and bloated.

Note the # we used. That tells the Markdown editor (or programme you’re using to convert Markdown to HTML) to wrap to the following line in

tags.

Markdown knows you’re writing a paragraph when you leave a line between blocks of text.

To make a second level heading, we use 2 ##s:

## This is a subheading

There are lots of little characters we use to structure our text. For example:

> This makes a blockquote. A blockquote is a long piece of quoted text. Blockquotes are often indented and occasionally italicised.

Which a browser will make look something like this:

This makes a blockquote. A blockquote is a long piece of quoted text. Blockquotes are often indented and occasionally italicised.

Why write in Markdown

Once you understand Markdown’s syntax it’s easy – and quick – to write web documents. Using a WYSIWYG editor will seem cumbersome.

Markdown mirrors HTML. When you write in Markdown you’re thinking about structure and meaning, not appearance. Quality control is easier in Markdown than WYSIWYG.

From Markdown to your blog

OK, so that all sounds grand. You’ve written your first blog post in Markdown in record time. How do you actually convert it to HTML and get it on the internet?

You’ve got a few options. You can either do the conversion before you open your blogging software, or you can do it in your blogging software.

Let’s take a look at WordPress again.

Converting Markdown to HTML before opening WordPress

You can write Markdown in any text editor, but you’ll need some software to convert it to HTML.

The best way to do this is to use a Markdown editor, which’ll let you edit and convert in one program. Lots of editors will show you what your HTML will look like as you write Markdown.

There are lots of good Markdown editors out there. I use:

The process is simple. Write in Markdown then choose Export from your file menu. At the very least you’ll get the option to export HTML. Some editors also let you export to a PDF file.

Once you have some HTML to work with, login to your website, select New post and paste your HTML into the Text tab in the WYSIWYG editor pane. Press Publish and you’re done.

Writing Markdown in WordPress

You can bypass Markdown editors altogether. This will make for a more streamlined workflow, but you won’t have any local copies of your blog posts. Remember, one of the weaknesses of WYSIWYG editors was the lack of portability.

You’ll still write better quality posts more quickly.

However, if exporting and copying and pasting HTML is too time consuming, then it makes sense to use Markdown in WordPress. To do that, you’ll need a plugin. You could try wp-markdown.

This time, you’ll login to your website and select New post. Instead of using the WYSIWYG editor you’ll chose the Text editor and write in Markdown.

Using an app like Blogeasy

Blogeasy offers the best of both worlds. Write local Markdown files and hit the Publish button to send them straight to your WordPress powered website.

The future

As you’ve probably figured out, the Markdown/WordPress workflow isn’t perfect at the moment. Although there are some advantages to using a Markdown editor you may well find the whole export/copy/login/paste process too time consuming.

There are some desktop apps out there that let you write Wordpress posts in a WYSIWYG editor on your computer before uploading to your site. A few (such as Blogeasy) let you write in Markdown. This is ideal.

We need more Markdown editors that connect directly to websites, whether they’re built on WordPress, Blogger or Drupal.

Alternatively, you could try a different blogging engine. There are lots of static site generators out there which take Markdown files and convert them to complete websites. The likes of Jekyll (which runs this site) are super fast, secure and portable, but they do take quite a bit of technical know how.

数据集介绍:电力线目标检测数据集 一、基础信息 数据集名称:电力线目标检测数据集 图片数量: 训练集:2898张图片 验证集:263张图片 测试集:138张图片 总计:3299张图片 分类类别: 类别ID: 0(电力线) 标注格式: YOLO格式,包含对象标注信息,适用于目标检测任务。 数据格式:JPEG/PNG图片,来源于空中拍摄或监控视觉。 二、适用场景 电力设施监控与巡检: 数据集支持目标检测任务,帮助构建能够自动识别和定位电力线的AI模型,用于无人机或固定摄像头巡检,提升电力设施维护效率和安全性。 能源与公用事业管理: 集成至能源管理系统中,提供实时电力线检测功能,辅助进行风险 assessment 和预防性维护,优化能源分配。 计算机视觉算法研究: 支持目标检测技术在特定领域的应用研究,促进AI在能源和公用事业行业的创新与发展。 专业培训与教育: 数据集可用于电力行业培训课程,作为工程师和技术人员学习电力线检测与识别的重要资源。 三、数据集优势 标注精准可靠: 每张图片均经过专业标注,确保电力线对象的定位准确,适用于高精度模型训练。 数据多样性丰富: 包含多种环境下的电力线图片,如空中视角,覆盖不同场景条件,提升模型的泛化能力和鲁棒性。 任务适配性强: 标注格式兼容YOLO等主流深度学习框架,便于快速集成和模型开发,支持目标检测任务的直接应用。 实用价值突出: 专注于电力线检测,为智能电网、自动化巡检和能源设施监控提供关键数据支撑,具有较高的行业应用价值。
【弹簧阻尼器】基于卡尔曼滤波弹簧质量阻尼器系统噪声测量实时状态估计研究(Matlab代码实现)内容概要:本文围绕“基于卡尔曼滤波的弹簧质量阻尼器系统噪声测量与实时状态估计”展开研究,利用Matlab代码实现对系统状态的精确估计。重点在于应用卡尔曼滤波技术处理系统中存在的噪声干扰,提升对弹簧质量阻尼器系统动态行为的实时观测能力。文中详细阐述了系统建模、噪声特性分析及卡尔曼滤波算法的设计与实现过程,展示了滤波算法在抑制测量噪声、提高状态估计精度方面的有效性。同时,该研究属于更广泛的信号处理与状态估计技术应用范畴,适用于复杂动态系统的监控与控制。; 适合人群:具备一定控制系统理论基础和Matlab编程经验的高校研究生、科研人员及工程技术人员,尤其适合从事动态系统建模、状态估计与滤波算法研究的相关人员。; 使用场景及目标:①应用于机械、航空航天、自动化等领域中对振动系统状态的高精度实时估计;②为噪声环境下的传感器数据融合与状态预测提供算法支持;③作为卡尔曼滤波算法在实际物理系统中应用的教学与科研案例。; 阅读建议:建议读者结合Matlab代码实践,深入理解系统建模与滤波器设计的关键步骤,关注噪声建模与滤波参数调优对估计性能的影响,并可进一步拓展至扩展卡尔曼滤波(EKF)或无迹卡尔曼滤波(UKF)在非线性系统中的应用。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值