From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from alexa-out-sd-01.qualcomm.com (alexa-out-sd-01.qualcomm.com [199.106.114.38])
 by mx.groups.io with SMTP id smtpd.web11.17952.1670514823210787445
 for <devel@edk2.groups.io>;
 Thu, 08 Dec 2022 07:53:43 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@quicinc.com header.s=qcdkim header.b=AqYE7/Ce;
 spf=permerror, err=parse error for token &{10 18 %{ir}.%{v}.%{d}.spf.has.pphosted.com}: invalid domain name (domain: quicinc.com, ip: 199.106.114.38, mailfrom: quic_rcran@quicinc.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim;
  t=1670514823; x=1702050823;
  h=from:message-id:date:mime-version:subject:to:cc:
   references:in-reply-to:content-transfer-encoding;
  bh=CO5STO9F1/FHYREENV08CUqj9akGJcp0Dk8crAUbYiQ=;
  b=AqYE7/CeKHA2tHPrJpsLG5x0/QJrMptYhIJcjGjQiSsPbmT5mqw9Wg4U
   nOpsyt6tR8Q4xShTuV6OS4Bsv8sdyz8p/PvwFpZUYU6ZplDe04eSnxkdU
   H9xpx2nfwPVcWJanqipCJEcx2axuzpRzkxIgfJQWZo9BPCm+CTZHduSOG
   E=;
Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30])
  by alexa-out-sd-01.qualcomm.com with ESMTP; 08 Dec 2022 07:53:42 -0800
From: "Rebecca Cran" <quic_rcran@quicinc.com>
X-QCInternal: smtphost
Received: from nasanex01b.na.qualcomm.com ([10.46.141.250])
  by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Dec 2022 07:53:42 -0800
Received: from [10.110.73.72] (10.80.80.8) by nasanex01b.na.qualcomm.com
 (10.46.141.250) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Thu, 8 Dec 2022
 07:53:42 -0800
Message-ID: <b5c0aade-8ae7-366d-3206-fc6d8978102e@quicinc.com>
Date: Thu, 8 Dec 2022 08:53:41 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.5.1
Subject: Re: [edk2-devel] [edk2-wiki][PATCH v3 1/4] Add initial How to Build with Stuart Document
To: Michael Kubacki <mikuback@linux.microsoft.com>, <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>
References: <20221207162403.337-1-mikuback@linux.microsoft.com>
 <20221207162403.337-2-mikuback@linux.microsoft.com>
 <e3bec8ba-18f8-fc40-7241-d3e90107e0cb@quicinc.com>
 <c47e517d-cac9-1a99-4d86-c355093385c4@linux.microsoft.com>
In-Reply-To: <c47e517d-cac9-1a99-4d86-c355093385c4@linux.microsoft.com>
Return-Path: rebecca@quicinc.com
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To
 nasanex01b.na.qualcomm.com (10.46.141.250)
Content-Language: en-US
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit

Ah, thanks for the explanation!

On 12/8/22 07:21, Michael Kubacki wrote:
> 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.
>>