From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io, quic_rcran@quicinc.com
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [edk2-wiki][PATCH v3 1/4] Add initial How to Build with Stuart Document
Date: Thu, 8 Dec 2022 09:21:08 -0500 [thread overview]
Message-ID: <c47e517d-cac9-1a99-4d86-c355093385c4@linux.microsoft.com> (raw)
In-Reply-To: <e3bec8ba-18f8-fc40-7241-d3e90107e0cb@quicinc.com>
I write it by hand. HTML comes in because I'm using collapsing content
via <summary> sections. Once in those sections, normal markdown
formatting does not apply. I've limited HTML usage in those sections to
very simple tags that mostly map directly to features allowed in
markdown formatting as well (<strong> -> **, <a> -> [](), <code> -> ``,
etc.)
Thanks,
Michael
On 12/7/2022 11:47 PM, Rebecca Cran wrote:
> What tool do you use to write the pages?
>
> It seems to be a mixture of markdown and HTML: for example I'm surprised
> to see things like "<strong>C Compiler</strong>" - I'd expect something
> like "**C Compiler**" instead.
>
next prev parent reply other threads:[~2022-12-08 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 16:23 [edk2-wiki][PATCH v3 0/4] Add new edk2 build instructions Michael Kubacki
2022-12-07 16:24 ` [edk2-wiki][PATCH v3 1/4] Add initial How to Build with Stuart Document Michael Kubacki
2022-12-08 4:47 ` [edk2-devel] " Rebecca Cran
2022-12-08 14:21 ` Michael Kubacki [this message]
2022-12-08 15:53 ` Rebecca Cran
2022-12-13 5:25 ` Rebecca Cran
2022-12-13 14:17 ` Michael Kubacki
2022-12-07 16:24 ` [edk2-wiki][PATCH v3 2/4] Add initial container usage instructions Michael Kubacki
2022-12-07 16:24 ` [edk2-wiki][PATCH v3 3/4] Add top-level build instructions file Michael Kubacki
2022-12-07 16:24 ` [edk2-wiki][PATCH v3 4/4] Update existing build instructions Michael Kubacki
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-list 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=c47e517d-cac9-1a99-4d86-c355093385c4@linux.microsoft.com \
--to=devel@edk2.groups.io \
/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