|
1 | | - |
2 | 1 | --- |
3 | | -# ^ DON'T REMOVE the "---" above! |
4 | | -# ============================================================================== |
5 | | -# WEBSITE HEADER |
6 | | -# ============================================================================== |
7 | | -# These variables are shown in the website header. |
8 | | -# ------------------------------------------------------------------------------ |
9 | 2 | website_title: 'Proxy Pattern' |
10 | 3 | website_tagline: 'Ein Einblick in die Welt des Proxies in PHP' |
11 | | -# ============================================================================== |
12 | | -# GITHUB LINKS |
13 | | -# ============================================================================== |
14 | | -# The following variables are used for automagically creating links to your repo |
15 | | -# on GitHub, and for the .zip and .tar download links. |
16 | | -# Substitute sample values with your username and repository name as they appear |
17 | | -# on GitHub (CASE SENSITIVE!!!) |
18 | | -# ------------------------------------------------------------------------------ |
19 | | -# Example: https://github.com/jasonlong/architect-theme |
20 | 4 | your_github_username: it4need |
21 | 5 | your_github_reponame: php-proxy-pattern |
22 | | -# |
23 | | -# ============================================================================== |
24 | | -# HTML META |
25 | | -# ============================================================================== |
26 | | -# HTML Metadata -- for <head> section |
27 | | -# If you don't need a variable, delete its line or comment it out with a `#`! |
28 | | -# ------------------------------------------------------------------------------ |
29 | 6 | title: 'Proxy Entwurfsmuster - Einführung in PHP' |
30 | 7 | lang: de |
31 | 8 | date: 30.12.2018 |
32 | 9 | author: |
33 | 10 | - Jan André Schlösser |
34 | 11 | description: 'Proxy ist ein GoF-Strukturmuster und stellt ein Stellvertreter-Objekt oder Platzhalter (Proxy) für ein anderes Objekt zur Verfügung. Es bietet dadurch Kontrolle über die Objekterzeugung und dessen Zugriff.' |
35 | | -# ============================================================================== |
36 | | -# EXTRA CSS STYLESHEETS |
37 | | -# ============================================================================== |
38 | | -# An optional list of extra CSS stylesheets to include from the "/stylesheets/" |
39 | | -# theme's subfolder. Just place your custom stylesheets in that folder and add |
40 | | -# their filenames to this list. |
41 | | -# DON'T USE ABSOLUTE URLs (ie: "https://" or "http://")!!! If you do it, the |
42 | | -# template will break badly. For includind CSS files with absolute URLs, use the |
43 | | -# "header-includes:" scalar instead (see below). |
44 | | -# ------------------------------------------------------------------------------ |
45 | | -#css: |
46 | | -# - your_custom.css |
47 | | -# - another_stylesheet.css |
48 | | -# ============================================================================== |
49 | | -# CUSTOM HTML TO INJECT IN HEADER |
50 | | -# ============================================================================== |
51 | | -# This optional indented block literal scalar can be used to inject (verbatim) |
52 | | -# raw html at the end of the head section, just before the closing </head> tag. |
53 | | -# This can be used to include CSS with absolute URLs, or JavaScript files -- or |
54 | | -# anything you want, without actually editing the template file. |
55 | | -# ------------------------------------------------------------------------------ |
56 | 12 | header-includes: | |
57 | | - <!-- anything you put here will go verbatim in the header section |
58 | | - Useful for adding javascripts, custom metadata, and so on... --> |
59 | | -# ****************************************************************************** |
60 | | -# * INSERT BEFORE BODY * |
61 | | -# ****************************************************************************** |
62 | | -# You can inject some extra contents after the opening <body> tag and before the |
63 | | -# contents of your 'README.md' file. It will be parsed as markdown and converted |
64 | | -# to html by pandoc. Use raw html if you need advanced features, but remember |
65 | | -# that all loose text will be enclosed in <p> tags -- wrap it inside a <div> if |
66 | | -# you don't want it parsed as markdown! |
67 | | -# ------------------------------------------------------------------------------ |
68 | 13 | include-before: | |
69 | | - <!-- anything you put here will go before the opening <body> tag |
70 | | - (ie: before the README’s contents) Markdown will become HTML --> |
71 | | -# ****************************************************************************** |
72 | | -# * INSERT AFTER BODY * |
73 | | -# ****************************************************************************** |
74 | | -# You can also inject extra contents after those of your 'README.md' file and |
75 | | -# before the closing </body> tag. Same rules as for 'include-before' variable. |
76 | | -# ------------------------------------------------------------------------------ |
77 | 14 | include-after: | |
78 | | - <!-- anything you put here will go before the closing </body> tag |
79 | | - (ie: after the README’s contents) Markdown will become HTML --> |
80 | | - --- |
81 | | -# ------------------------------------------------------------------------------ |
82 | | -# DON'T REMOVE the "..." below: |
83 | 15 | ... |
0 commit comments