Skip to content

Commit 2230b62

Browse files
committed
landing page firmware analysis
1 parent f4cbd1a commit 2230b62

File tree

1 file changed

+44
-65
lines changed

1 file changed

+44
-65
lines changed

articles/firmware-analysis/index.yml

Lines changed: 44 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -1,84 +1,63 @@
11
### YamlMime:Landing
22

3-
title: service documentation # < 60 chars
4-
summary: summary # < 160 chars
3+
title: Firmware analysis (preview) # < 60 chars
4+
summary: Analyze your firmware images for security vulnerabilities # < 160 chars
55

66
metadata:
7-
title: title # Required; page title displayed in search results. Include the brand. < 60 chars.
8-
description: description # Required; article description that is displayed in search results. < 160 chars.
9-
ms.service: service or ms.prod: product #Required; use either service or product per approved list.
10-
ms.subservice: subservice or ms.technology: technology # Optional; Remove if not applicable.
7+
title: Firmware analysis (preview) # Required; page title displayed in search results. Include the brand. < 60 chars.
8+
description: Analyze your firmware images for security vulnerabilities # Required; article description that is displayed in search results. < 160 chars.
9+
ms.service: service or ms.prod: service #Required; use either service or product per approved list.
1110
ms.topic: landing-page # Required
12-
ms.collection: collection # Optional; Remove if no collection is used.
13-
author: githubauthor #Required; your GitHub user alias, with correct capitalization.
14-
ms.author: msauthor #Required; microsoft alias of author; optional team alias.
15-
ms.date: 01/27/2020 #Required; mm/dd/yyyy format.
11+
author: karengu0 #Required; your GitHub user alias, with correct capitalization.
12+
ms.author: karenguo #Required; microsoft alias of author; optional team alias.
13+
ms.date: 11/11/2024 #Required; mm/dd/yyyy format.
1614

1715
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | tutorial | overview | quickstart | reference | sample | tutorial | video | whats-new
1816

1917
landingContent:
2018
# Cards and links should be based on top customer tasks or top subjects
2119
# Start card title with a verb
22-
# Card
23-
- title: About [service]
24-
linkLists:
25-
- linkListType: overview
26-
links:
27-
- text: What is [service]?
28-
url: file1.md
29-
- text: linktext2
30-
url: file2.md
31-
- linkListType: linkListType
32-
links:
33-
- text: linktext1
34-
url: file1.md
35-
- text: linktext2
36-
url: file2.md
37-
38-
# Card
20+
# Card
3921
- title: Get started
4022
linkLists:
41-
- linkListType: linkListType
42-
links:
43-
- text: linktext1
44-
url: file1.md
45-
- text: linktext2
46-
url: file2.md
47-
- linkListType: linkListType
48-
links:
49-
- text: linktext1
50-
url: file1.md
51-
- text: linktext2
52-
url: file2.md
23+
- linkListType: get-started
24+
links:
25+
- text: What is Firmware analysis (preview)?
26+
url: overview-firmware-analysis.md
27+
- text: Get started with Firmware analysis in the Azure portal
28+
url: tutorial-analyze-firmware.md
29+
- text: What file systems are supported by Firmware analysis?
30+
url: firmware-analysis-faq.md#What-types-of-firmware-images-does-Firmware-analysis-support
31+
- linkListType: concept
32+
links:
33+
- text: What roles and permissions are needed to use Firmware analysis?
34+
url: firmware-analysis-rbac.md
35+
- linkListType: whats-new
36+
links:
37+
- text: What's new in Firmware analysis (preview)?
38+
url: release-notes.md
5339

5440
# Card
55-
- title: cardtitle3
41+
- title: Automate your workflow
5642
linkLists:
57-
- linkListType: linkListType
58-
links:
59-
- text: linktext1
60-
url: file1.md
61-
- text: linktext2
62-
url: file2.md
63-
- linkListType: linkListType
64-
links:
65-
- text: linktext1
66-
url: file1.md
67-
- text: linktext2
68-
url: file2.md
43+
- linkListType: how-to-guides
44+
links:
45+
- text: Automate your workflow using service principals
46+
url: automate-firmware-analysis-service-principals.md
47+
- text: Analyze firmware images using Azure CLI commands
48+
url: quickstart-upload-firmware-using-azure-command-line-interface.md
49+
- text: Analyze firmware images using Azure PowerShell commands
50+
url: quickstart-upload-firmware-using-azure-powershell.md
51+
- text: Analyze firmware images using a Python script
52+
url: quickstart-upload-firmware-using-python.md
6953

70-
# Card (Optional; Remove if not applicable.)
71-
- title: cardtitle4
54+
# Card
55+
- title: Understand the Firmware analysis service
7256
linkLists:
73-
- linkListType: linkListType
74-
links:
75-
- text: linktext1
76-
url: file1.md
77-
- text: linktext2
78-
url: file2.md
79-
- linkListType: linkListType
57+
- linkListType: concept
8058
links:
81-
- text: linktext1
82-
url: file1.md
83-
- text: linktext2
84-
url: file2.md
59+
- text: Understand the resource hierarchy of Firmware analysis
60+
url: firmware-analysis-rbac.md#Understanding-the-Representation-of-Firmware-Images-in-the-Azure-Resource-Hierarchy
61+
- text: Understand and interpret the extractor path results
62+
url: interpreting-extractor-paths.md
63+

0 commit comments

Comments
 (0)