mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-12-15 15:59:23 -05:00
Remove redundant h1 titles using # syntax
https://github.com/QubesOS/qubes-issues/issues/6701#issuecomment-862060759
This commit is contained in:
parent
a4cbb51092
commit
4ff7430960
80 changed files with 0 additions and 80 deletions
|
|
@ -10,7 +10,6 @@ ref: 66
|
|||
title: Development Workflow
|
||||
---
|
||||
|
||||
# Development Workflow
|
||||
|
||||
A workflow for developing Qubes OS+
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,6 @@ title: Qubes Builder
|
|||
|
||||
**Note: See [ISO building instructions](/doc/qubes-iso-building/) for a streamlined overview on how to use the build system.**
|
||||
|
||||
# Building Qubes from scratch
|
||||
|
||||
We have a fully automated build system for Qubes, that downloads, builds and
|
||||
packages all the Qubes components, and finally should spit out a ready-to-use
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 51
|
|||
title: Code Signing
|
||||
---
|
||||
|
||||
# Code Signing
|
||||
|
||||
All contributions to the Qubes OS [source code](/doc/source-code/) must be cryptographically signed by the author's PGP key.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ ref: 45
|
|||
title: Automated Tests
|
||||
---
|
||||
|
||||
# Automated Tests
|
||||
|
||||
## Unit and Integration Tests
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 46
|
|||
title: Mount LVM image
|
||||
---
|
||||
|
||||
# How to mount LVM image
|
||||
|
||||
You want to read your LVM image (e.g., there is a problem where you can't start any VMs except dom0).
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 48
|
|||
title: Profiling
|
||||
---
|
||||
|
||||
# Profiling
|
||||
|
||||
This is a python profiling primer.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 44
|
|||
title: Test Bench
|
||||
---
|
||||
|
||||
# Test bench for Dom0
|
||||
|
||||
This guide shows how to set up simple test bench that automatically test your code you're about to push. It is written especially for `core3` branch of `core-admin.git` repo, but some ideas are universal.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 47
|
|||
title: VM Configuration Interface
|
||||
---
|
||||
|
||||
# VM Configuration Interface
|
||||
|
||||
Qubes VM have some settings set by dom0 based on VM settings. There are multiple configuration channels, which includes:
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 50
|
|||
title: Windows Debugging
|
||||
---
|
||||
|
||||
# Debugging Windows HVMs
|
||||
|
||||
Debugging Windows code can be tricky in a virtualized environment. The guide below assumes Xen hypervisor and Windows 7 VMs.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 30
|
|||
title: Documentation Guidelines
|
||||
---
|
||||
|
||||
# Documentation guidelines
|
||||
|
||||
All Qubes OS documentation pages are stored as plain text files in the dedicated [qubes-doc](https://github.com/QubesOS/qubes-doc) repository.
|
||||
By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the web.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 242
|
|||
title: Google Season of Docs
|
||||
---
|
||||
|
||||
# 2021 Google Season of Docs
|
||||
|
||||
Thank you for your interest in participating in the [2021 Google Season of Docs](https://developers.google.com/season-of-docs/) program with the [Qubes OS team](/team/). You can read more about the Google Season of Docs in the official [guides](https://developers.google.com/season-of-docs/docs/) and [FAQ](https://developers.google.com/season-of-docs/docs/faq).
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 31
|
|||
title: Usability & UX
|
||||
---
|
||||
|
||||
# Usability & UX
|
||||
|
||||
Software that is too complicated to use, is often unused. Because we want as many people as possible to benefit from its unique security properties, the usability and user experience of Qubes OS is an utmost priority!
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 18
|
|||
title: Qubes R1.0 Release Notes
|
||||
---
|
||||
|
||||
# Qubes R1.0 Release Notes
|
||||
|
||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2012/09/03/introducing-qubes-10.html).
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ ref: 25
|
|||
title: Qubes R2.0 Release Notes
|
||||
---
|
||||
|
||||
# Qubes R2.0 Release Notes
|
||||
|
||||
Detailed release notes in [this blog post](https://blog.invisiblethings.org/2014/09/26/announcing-qubes-os-release-2.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 16
|
|||
title: Qubes R3.1 release notes
|
||||
---
|
||||
|
||||
# Qubes R3.1 release notes
|
||||
|
||||
## New features since 3.0
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 21
|
|||
title: Qubes R3.2 release notes
|
||||
---
|
||||
|
||||
# Qubes R3.2 release notes
|
||||
|
||||
## New features since 3.1
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 36
|
|||
title: Admin API
|
||||
---
|
||||
|
||||
# Qubes OS Admin API
|
||||
|
||||
## Goals
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 39
|
|||
title: 'Qrexec: Qubes RPC internals'
|
||||
---
|
||||
|
||||
# Qubes RPC internals
|
||||
|
||||
(*This page details the current implementation of qrexec (qrexec3).
|
||||
A [general introduction](/doc/qrexec/) to qrexec is also available.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ ref: 42
|
|||
title: 'Qrexec: Socket-based services'
|
||||
---
|
||||
|
||||
# Qrexec: Socket-based services
|
||||
|
||||
*This page describes how to implement and use new socket-backed services for qrexec. See [qrexec](/doc/qrexec/) for general overview of the qrexec framework.*
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 38
|
|||
title: Qrexec2
|
||||
---
|
||||
|
||||
# Command execution in VMs #
|
||||
|
||||
(*This page is about qrexec v2. For qrexec v3, see [here](/doc/qrexec3/).*)
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ ref: 59
|
|||
title: Networking
|
||||
---
|
||||
|
||||
# VM network in Qubes
|
||||
|
||||
## Overall description
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ ref: 58
|
|||
title: Template Implementation
|
||||
---
|
||||
|
||||
# Overview of VM block devices
|
||||
|
||||
Every VM has 4 block devices connected:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue