Set meta.description tag correctly

This commit is contained in:
Philipp Oppermann
2020-02-03 17:13:28 +01:00
parent 174d695512
commit 5276972c67
7 changed files with 16 additions and 1 deletions

View File

@@ -1,5 +1,6 @@
title = "Writing an OS in Rust" title = "Writing an OS in Rust"
base_url = "https://os.phil-opp.com" base_url = "https://os.phil-opp.com"
description = "This blog series creates a small operating system in the Rust programming language. Each post is a small tutorial and includes all needed code, so you can follow along if you like."
highlight_code = true highlight_code = true
highlight_theme = "visual-studio-dark" highlight_theme = "visual-studio-dark"

View File

@@ -6,6 +6,8 @@ weight = 3
I finally managed to get `blog_os` building on my Android phone using [termux](https://termux.com/). This post explains the necessary steps to set it up. I finally managed to get `blog_os` building on my Android phone using [termux](https://termux.com/). This post explains the necessary steps to set it up.
<!-- more -->
<img src="building-on-android.png" alt="Screenshot of the compilation output from android" style="height: 50rem;" > <img src="building-on-android.png" alt="Screenshot of the compilation output from android" style="height: 50rem;" >

View File

@@ -10,6 +10,8 @@ The [red zone] is an optimization of the [System V ABI] that allows functions to
[red zone]: http://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64#the-red-zone [red zone]: http://eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64#the-red-zone
[System V ABI]: http://wiki.osdev.org/System_V_ABI [System V ABI]: http://wiki.osdev.org/System_V_ABI
<!-- more -->
![stack frame with red zone](red-zone.svg) ![stack frame with red zone](red-zone.svg)
The image shows the stack frame of a function with `n` local variables. On function entry, the stack pointer is adjusted to make room on the stack for the return address and the local variables. The image shows the stack frame of a function with `n` local variables. On function entry, the stack pointer is adjusted to make room on the stack for the return address and the local variables.

View File

@@ -9,6 +9,8 @@ template = "second-edition/extra.html"
[Single Instruction Multiple Data (SIMD)]: https://en.wikipedia.org/wiki/SIMD [Single Instruction Multiple Data (SIMD)]: https://en.wikipedia.org/wiki/SIMD
<!-- more -->
- [MMX]: The _Multi Media Extension_ instruction set was introduced in 1997 and defines eight 64 bit registers called `mm0` through `mm7`. These registers are just aliases for the registers of the [x87 floating point unit]. - [MMX]: The _Multi Media Extension_ instruction set was introduced in 1997 and defines eight 64 bit registers called `mm0` through `mm7`. These registers are just aliases for the registers of the [x87 floating point unit].
- [SSE]: The _Streaming SIMD Extensions_ instruction set was introduced in 1999. Instead of re-using the floating point registers, it adds a completely new register set. The sixteen new registers are called `xmm0` through `xmm15` and are 128 bits each. - [SSE]: The _Streaming SIMD Extensions_ instruction set was introduced in 1999. Instead of re-using the floating point registers, it adds a completely new register set. The sixteen new registers are called `xmm0` through `xmm15` and are 128 bits each.
- [AVX]: The _Advanced Vector Extensions_ are extensions that further increase the size of the multimedia registers. The new registers are called `ymm0` through `ymm15` and are 256 bits each. They extend the `xmm` registers, so e.g. `xmm0` is the lower half of `ymm0`. - [AVX]: The _Advanced Vector Extensions_ are extensions that further increase the size of the multimedia registers. The new registers are called `ymm0` through `ymm15` and are 256 bits each. They extend the `xmm` registers, so e.g. `xmm0` is the lower half of `ymm0`.

View File

@@ -6,7 +6,7 @@
<meta charset="UTF-8"> <meta charset="UTF-8">
<meta name="apple-mobile-web-app-capable" content="yes"> <meta name="apple-mobile-web-app-capable" content="yes">
<meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="{{ config.description }}"> <meta name="description" content="{% block description %}{{ config.description }}{% endblock description %}">
<meta name="author" content="{{ config.extra.author.name }}"> <meta name="author" content="{{ config.extra.author.name }}">
{% if current_url %} {% if current_url %}

View File

@@ -4,6 +4,10 @@
{% block title %}{{ page.title }} | {{ config.title }}{% endblock title %} {% block title %}{{ page.title }} | {{ config.title }}{% endblock title %}
{% block description -%}
{{ page.summary | safe | striptags }}
{%- endblock description %}
{% block main %} {% block main %}
<h1>{{ page.title }}</h1> <h1>{{ page.title }}</h1>
{{ page.content | safe }} {{ page.content | safe }}

View File

@@ -7,6 +7,10 @@
<aside id="all-posts-link"><a href="{{ config.base_url | safe }}" title="All Posts">« All Posts</a></aside> <aside id="all-posts-link"><a href="{{ config.base_url | safe }}" title="All Posts">« All Posts</a></aside>
{% endblock header %} {% endblock header %}
{% block description -%}
{{ page.summary | safe | striptags }}
{%- endblock description %}
{% block main %} {% block main %}
<h1>{{ page.title }}</h1> <h1>{{ page.title }}</h1>
<time datetime="{{ page.date | date(format="%Y-%m-%d") }}" class="post-date"> <time datetime="{{ page.date | date(format="%Y-%m-%d") }}" class="post-date">