From 80211e054064e1ae8486bfb9edbba1d958e96827 Mon Sep 17 00:00:00 2001 From: Jose Falanga Date: Mon, 13 Oct 2025 18:33:49 -0300 Subject: [PATCH] testing --- .../rehosted/vertical-vs-horizontal/index.md | 2 +- arise-source/test/index.md | 76 +++--------------- arise-source/test/styles/index.md | 80 +++++++++++++++++++ 3 files changed, 92 insertions(+), 66 deletions(-) create mode 100644 arise-source/test/styles/index.md diff --git a/arise-source/rehosted/vertical-vs-horizontal/index.md b/arise-source/rehosted/vertical-vs-horizontal/index.md index 7290653..d18fefc 100644 --- a/arise-source/rehosted/vertical-vs-horizontal/index.md +++ b/arise-source/rehosted/vertical-vs-horizontal/index.md @@ -24,7 +24,7 @@ Now, you and I well know in the real world there are often constraints and exter My diagram-fu is weakened when working on my laptop’s track-pad, but the diagram below still serves to illustrate a few key points. -![[graph.jpg]] +![[./graph.jpg]] First, components of the game (Single Player, Tutorial, etc) differ in the amount of work and are so represented by different width blocks. As each HL is complete quality goes up. The VS sits on top of the HL and therefore is elevated in quality by it. In this diagram two vertical slices are created for two different portions of the game; single player and multiplayer. You can see that the slices themselves are of different widths. This represents the amount of the component the VS is meant to demonstrate. For example the single player VS may only be showing off one portion of one campaign mission, whereas the multiplayer VS might be demonstrating nearly fully functional gameplay on a variety of maps. Also note that each slice was started during a different HL iteration. Had the VS for single player began on the 3rd HL iteration it would have achieved a higher quality level. diff --git a/arise-source/test/index.md b/arise-source/test/index.md index 096f747..8dffb2c 100644 --- a/arise-source/test/index.md +++ b/arise-source/test/index.md @@ -1,67 +1,13 @@ -# Sample Markdown Test + diff --git a/arise-source/test/styles/index.md b/arise-source/test/styles/index.md new file mode 100644 index 0000000..27dffb8 --- /dev/null +++ b/arise-source/test/styles/index.md @@ -0,0 +1,80 @@ + +# Sample Markdown Test + +Welcome to the **Markdown style test** for your library-themed site. +This file includes headings, text formatting, lists, links, images, code, blockquotes, tables, and horizontal rules. + +--- + +## Text Styles + +**Bold text** +*Italic text* +***Bold + Italic*** +~~Strikethrough~~ +`Inline code` +> Blockquote text for testing. The border and color should reflect your library style. + +--- + +## Links + +[Internal link](/posts) +[External link](https://spectrasecu.re) + +Hover over links to see color transition. + +--- + +## Lists + +### Unordered List +- Item 1 +- Item 2 + - Nested item +- Item 3 + +### Ordered List +1. First +2. Second +3. Third + 1. Nested first + 2. Nested second + +--- + +## Images + +![Sample image](https://via.placeholder.com/300x150) + +Check image border radius, spacing, and responsiveness. + +--- + +## Code Blocks + +### Inline code + +Use `` `inline code` `` inside text. + +### Fenced code block + +```bash +# Bash example +echo "Hello, world!" +for file in *.txt; do + echo "Processing $file" +done +``` \ No newline at end of file