Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
+
+
Readability, however, is emphasized above all else. A Markdown-formatted
+document should be publishable as-is, as plain text, without looking
+like it’s been marked up with tags or formatting instructions. While
+Markdown’s syntax has been influenced by several existing text-to-HTML
+filters – including Setext, atx, Textile, reStructuredText,
+Grutatext, and EtText – the single biggest source of
+inspiration for Markdown’s syntax is the format of plain text email.
+
+
Block Elements
+
+
Paragraphs and Line Breaks
+
+
A paragraph is simply one or more consecutive lines of text, separated
+by one or more blank lines. (A blank line is any line that looks like a
+blank line – a line containing nothing but spaces or tabs is considered
+blank.) Normal paragraphs should not be indented with spaces or tabs.
+
+
The implication of the “one or more consecutive lines of text” rule is
+that Markdown supports “hard-wrapped” text paragraphs. This differs
+significantly from most other text-to-HTML formatters (including Movable
+Type’s “Convert Line Breaks” option) which translate every line break
+character in a paragraph into a <br /> tag.
+
+
When you do want to insert a <br /> break tag using Markdown, you
+end a line with two or more spaces, then type return.
+
+
Headers
+
+
Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
+
+
Optionally, you may “close” atx-style headers. This is purely
+cosmetic – you can use this if you think it looks better. The
+closing hashes don’t even need to match the number of hashes
+used to open the header. (The number of opening hashes
+determines the header level.)
+
+
Blockquotes
+
+
Markdown uses email-style > characters for blockquoting. If you’re
+familiar with quoting passages of text in an email message, then you
+know how to create a blockquote in Markdown. It looks best if you hard
+wrap the text and put a > before every line:
+
+
+
This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
+consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
+Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
+
+
Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
+id sem consectetuer libero luctus adipiscing.
+
+
+
Markdown allows you to be lazy and only put the > before the first
+line of a hard-wrapped paragraph:
+
+
+
This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
+consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
+Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
+
+
Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
+id sem consectetuer libero luctus adipiscing.
+
+
+
Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
+adding additional levels of >:
+
+
+
This is the first level of quoting.
+
+
+
This is nested blockquote.
+
+
+
Back to the first level.
+
+
+
Blockquotes can contain other Markdown elements, including headers, lists,
+and code blocks:
Any decent text editor should make email-style quoting easy. For
+example, with BBEdit, you can make a selection and choose Increase
+Quote Level from the Text menu.
+
+
Lists
+
+
Markdown supports ordered (numbered) and unordered (bulleted) lists.
+
+
Unordered lists use asterisks, pluses, and hyphens – interchangably
+– as list markers:
+
+
+
Red
+
Green
+
Blue
+
+
+
is equivalent to:
+
+
+
Red
+
Green
+
Blue
+
+
+
and:
+
+
+
Red
+
Green
+
Blue
+
+
+
Ordered lists use numbers followed by periods:
+
+
+
Bird
+
McHale
+
Parish
+
+
+
It’s important to note that the actual numbers you use to mark the
+list have no effect on the HTML output Markdown produces. The HTML
+Markdown produces from the above list is:
+
+
If you instead wrote the list in Markdown like this:
+
+
+
Bird
+
McHale
+
Parish
+
+
+
or even:
+
+
+
Bird
+
McHale
+
Parish
+
+
+
you’d get the exact same HTML output. The point is, if you want to,
+you can use ordinal numbers in your ordered Markdown lists, so that
+the numbers in your source match the numbers in your published HTML.
+But if you want to be lazy, you don’t have to.
+
+
To make lists look nice, you can wrap items with hanging indents:
+
+
+
Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
+viverra nec, fringilla in, laoreet vitae, risus.
+
Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+
+
+
But if you want to be lazy, you don’t have to:
+
+
+
Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
+viverra nec, fringilla in, laoreet vitae, risus.
+
Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+
+
+
List items may consist of multiple paragraphs. Each subsequent
+paragraph in a list item must be indented by either 4 spaces
+or one tab:
+
+
+
This is a list item with two paragraphs. Lorem ipsum dolor
+sit amet, consectetuer adipiscing elit. Aliquam hendrerit
+mi posuere lectus.
+
+
Vestibulum enim wisi, viverra nec, fringilla in, laoreet
+vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
+sit amet velit.
+
+
Suspendisse id sem consectetuer libero luctus adipiscing.
+
+
+
It looks nice if you indent every line of the subsequent
+paragraphs, but here again, Markdown will allow you to be
+lazy:
+
+
+
This is a list item with two paragraphs.
+
+
This is the second paragraph in the list item. You’re
+only required to indent the first line. Lorem ipsum dolor
+sit amet, consectetuer adipiscing elit.
+
+
Another item in the same list.
+
+
+
To put a blockquote within a list item, the blockquote’s >
+delimiters need to be indented:
+
+
+
A list item with a blockquote:
+
+
+
This is a blockquote
+inside a list item.
+
+
+
+
+
To put a code block within a list item, the code block needs
+to be indented twice – 8 spaces or two tabs:
+
+
+
A list item with a code block:
+
+
<code goes here>
+
+
+
+
Code Blocks
+
+
Pre-formatted code blocks are used for writing about programming or
+markup source code. Rather than forming normal paragraphs, the lines
+of a code block are interpreted literally. Markdown wraps a code block
+in both <pre> and <code> tags.
+
+
To produce a code block in Markdown, simply indent every line of the
+block by at least 4 spaces or 1 tab.
+
+
This is a normal paragraph:
+
+
This is a code block.
+
+
+
Here is an example of AppleScript:
+
+
tell application "Foo"
+ beep
+end tell
+
+
+
A code block continues until it reaches a line that is not indented
+(or the end of the article).
+
+
Within a code block, ampersands (&) and angle brackets (< and >)
+are automatically converted into HTML entities. This makes it very
+easy to include example HTML source code using Markdown – just paste
+it and indent it, and Markdown will handle the hassle of encoding the
+ampersands and angle brackets. For example, this:
Regular Markdown syntax is not processed within code blocks. E.g.,
+asterisks are just literal asterisks within a code block. This means
+it’s also easy to use Markdown to write about Markdown’s own syntax.
+
+
tell application "Foo"
+ beep
+end tell
+
+
+
Span Elements
+
+
Links
+
+
Markdown supports two style of links: inline and reference.
+
+
In both styles, the link text is delimited by [square brackets].
+
+
To create an inline link, use a set of regular parentheses immediately
+after the link text’s closing square bracket. Inside the parentheses,
+put the URL where you want the link to point, along with an optional
+title for the link, surrounded in quotes. For example:
Markdown treats asterisks (*) and underscores (_) as indicators of
+emphasis. Text wrapped with one * or _ will be wrapped with an
+HTML <em> tag; double *’s or _’s will be wrapped with an HTML
+<strong> tag. E.g., this input:
+
+
single asterisks
+
+
single underscores
+
+
double asterisks
+
+
double underscores
+
+
Code
+
+
To indicate a span of code, wrap it with backtick quotes ($$).
+Unlike a pre-formatted code block, a code span indicates code within a
+normal paragraph. For example:
+
+
Use the printf() function.
`, "$$", "`"),
+ },
+ {
+ name: "archive index",
+ dir: filepath.Join("..", "..", "test", "files", "archive"),
+ path: "/archive/",
+ expectHTMLHead: true,
+ },
+ {
+ name: "not found",
+ dir: filepath.Join("..", "..", "test", "files", "minimal"),
+ path: "/does-not-exist",
+ expectStatus: http.StatusNotFound,
+ },
+ }
+
+ for _, tc := range cases {
+ t.Run(tc.name, func(t *testing.T) {
+ _, port := startServer(t, tc.dir)
+
+ body, status := get(t, port, tc.path)
+
+ if tc.expectStatus != 0 {
+ if status != tc.expectStatus {
+ t.Fatalf("expected %d, got %d", tc.expectStatus, status)
+ }
+ return
+ }
+
+ if tc.expectBody != "" {
+ if body != tc.expectBody {
+ t.Fatalf("unexpected body:\n--- got ---\n%s\n--- want ---\n%s", body, tc.expectBody)
+ }
+ return
+ }
+
+ if body == "" && !tc.expectEmpty {
+ t.Fatal("empty response")
+ }
+
+ if tc.expectHTMLHead && len(body) >= 6 && body[:6] != "" {
+ t.Fatal("archive index is not html")
+ }
+ })
+ }
+}
diff --git a/test/files/archive/Fes.toml b/test/files/archive/Fes.toml
new file mode 100644
index 0000000..5acc4c8
--- /dev/null
+++ b/test/files/archive/Fes.toml
@@ -0,0 +1,5 @@
+[app]
+
+name = "archive"
+version = "0.0.1"
+authors = ["fSD"]
diff --git a/test/files/archive/README.md b/test/files/archive/README.md
new file mode 100644
index 0000000..07271ca
--- /dev/null
+++ b/test/files/archive/README.md
@@ -0,0 +1,33 @@
+# archive
+
+```
+fes new archive
+```
+
+> **Know what you are doing?** Delete this file. Have fun!
+
+## Project Structure
+
+Inside your Fes project, you'll see the following directories and files:
+
+```
+.
+├── Fes.toml
+├── README.md
+└── www
+ └── index.lua
+```
+
+Fes looks for `.lua` files in the `www/` directory. Each file is exposed as a route based on its file name.
+
+## Commands
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :------------------------ | :----------------------------------------------- |
+| `fes run .` | Runs the project at `.` |
+
+## What to learn more?
+
+Check out [Fes's docs](https://docs.vxserver.dev/static/fes.html).
\ No newline at end of file
diff --git a/test/files/archive/archive/seal.png b/test/files/archive/archive/seal.png
new file mode 100644
index 0000000..74634c2
Binary files /dev/null and b/test/files/archive/archive/seal.png differ
diff --git a/test/files/archive/www/index.lua b/test/files/archive/www/index.lua
new file mode 100644
index 0000000..d369c0e
--- /dev/null
+++ b/test/files/archive/www/index.lua
@@ -0,0 +1,8 @@
+local fes = require("fes")
+local site = fes.fes()
+
+-- site.copyright = fes.util.copyright("https://example.com", "vx-clutch")
+
+site:h1("Hello, World!")
+
+return site
\ No newline at end of file
diff --git a/test/files/lua-basic/Fes.toml b/test/files/lua-basic/Fes.toml
new file mode 100644
index 0000000..a47b09f
--- /dev/null
+++ b/test/files/lua-basic/Fes.toml
@@ -0,0 +1,5 @@
+[app]
+
+name = "lua-basic"
+version = "0.0.1"
+authors = ["fSD"]
diff --git a/test/files/lua-basic/README.md b/test/files/lua-basic/README.md
new file mode 100644
index 0000000..300a5e8
--- /dev/null
+++ b/test/files/lua-basic/README.md
@@ -0,0 +1,33 @@
+# lua-basic
+
+```
+fes new lua-basic
+```
+
+> **Know what you are doing?** Delete this file. Have fun!
+
+## Project Structure
+
+Inside your Fes project, you'll see the following directories and files:
+
+```
+.
+├── Fes.toml
+├── README.md
+└── www
+ └── index.lua
+```
+
+Fes looks for `.lua` files in the `www/` directory. Each file is exposed as a route based on its file name.
+
+## Commands
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :------------------------ | :----------------------------------------------- |
+| `fes run .` | Runs the project at `.` |
+
+## What to learn more?
+
+Check out [Fes's docs](https://docs.vxserver.dev/static/fes.html).
\ No newline at end of file
diff --git a/test/files/lua-basic/www/index.lua b/test/files/lua-basic/www/index.lua
new file mode 100644
index 0000000..8b68d9d
--- /dev/null
+++ b/test/files/lua-basic/www/index.lua
@@ -0,0 +1,8 @@
+local fes = require("fes")
+local site = fes.fes()
+
+-- site.copyright = fes.util.copyright("https://example.com", "vx-clutch")
+
+site:h1("Hello, World!")
+
+return site
diff --git a/test/files/lua-error/Fes.toml b/test/files/lua-error/Fes.toml
new file mode 100644
index 0000000..2cb1ebe
--- /dev/null
+++ b/test/files/lua-error/Fes.toml
@@ -0,0 +1,5 @@
+[app]
+
+name = "lua-error"
+version = "0.0.1"
+authors = ["fSD"]
diff --git a/test/files/lua-error/README.md b/test/files/lua-error/README.md
new file mode 100644
index 0000000..4bdcb6c
--- /dev/null
+++ b/test/files/lua-error/README.md
@@ -0,0 +1,33 @@
+# lua-error
+
+```
+fes new lua-error
+```
+
+> **Know what you are doing?** Delete this file. Have fun!
+
+## Project Structure
+
+Inside your Fes project, you'll see the following directories and files:
+
+```
+.
+├── Fes.toml
+├── README.md
+└── www
+ └── index.lua
+```
+
+Fes looks for `.lua` files in the `www/` directory. Each file is exposed as a route based on its file name.
+
+## Commands
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :------------------------ | :----------------------------------------------- |
+| `fes run .` | Runs the project at `.` |
+
+## What to learn more?
+
+Check out [Fes's docs](https://docs.vxserver.dev/static/fes.html).
\ No newline at end of file
diff --git a/test/files/lua-error/www/index.lua b/test/files/lua-error/www/index.lua
new file mode 100644
index 0000000..c5aeeb0
--- /dev/null
+++ b/test/files/lua-error/www/index.lua
@@ -0,0 +1,6 @@
+local fes = require("fes")
+local site = fes.fes()
+
+Hello, World!
+
+return site
diff --git a/test/files/lua-include/Fes.toml b/test/files/lua-include/Fes.toml
new file mode 100644
index 0000000..805113e
--- /dev/null
+++ b/test/files/lua-include/Fes.toml
@@ -0,0 +1,5 @@
+[app]
+
+name = "lua-include"
+version = "0.0.1"
+authors = ["fSD"]
diff --git a/test/files/lua-include/README.md b/test/files/lua-include/README.md
new file mode 100644
index 0000000..d537fda
--- /dev/null
+++ b/test/files/lua-include/README.md
@@ -0,0 +1,33 @@
+# lua-include
+
+```
+fes new lua-include
+```
+
+> **Know what you are doing?** Delete this file. Have fun!
+
+## Project Structure
+
+Inside your Fes project, you'll see the following directories and files:
+
+```
+.
+├── Fes.toml
+├── README.md
+└── www
+ └── index.lua
+```
+
+Fes looks for `.lua` files in the `www/` directory. Each file is exposed as a route based on its file name.
+
+## Commands
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :------------------------ | :----------------------------------------------- |
+| `fes run .` | Runs the project at `.` |
+
+## What to learn more?
+
+Check out [Fes's docs](https://docs.vxserver.dev/static/fes.html).
\ No newline at end of file
diff --git a/test/files/lua-include/include/test.lua b/test/files/lua-include/include/test.lua
new file mode 100644
index 0000000..c15aba7
--- /dev/null
+++ b/test/files/lua-include/include/test.lua
@@ -0,0 +1,7 @@
+local test = {}
+
+test.render = function(std)
+ return std.h2("Hello, World!")
+end
+
+return test
diff --git a/test/files/lua-include/www/index.lua b/test/files/lua-include/www/index.lua
new file mode 100644
index 0000000..537e22f
--- /dev/null
+++ b/test/files/lua-include/www/index.lua
@@ -0,0 +1,10 @@
+local fes = require("fes")
+local site = fes.fes()
+
+-- site.copyright = fes.util.copyright("https://example.com", "vx-clutch")
+
+site:h1("Hello, World!")
+
+site:note(fes.app.test.render(fes.std))
+
+return site
diff --git a/test/files/markdown/Fes.toml b/test/files/markdown/Fes.toml
new file mode 100644
index 0000000..f800d4d
--- /dev/null
+++ b/test/files/markdown/Fes.toml
@@ -0,0 +1,5 @@
+[app]
+
+name = "markdown"
+version = "0.0.1"
+authors = ["vx-clutch"]
\ No newline at end of file
diff --git a/test/files/markdown/README.md b/test/files/markdown/README.md
new file mode 100644
index 0000000..3f62240
--- /dev/null
+++ b/test/files/markdown/README.md
@@ -0,0 +1,33 @@
+# markdown
+
+```
+fes new markdown
+```
+
+> **Know what you are doing?** Delete this file. Have fun!
+
+## Project Structure
+
+Inside your Fes project, you'll see the following directories and files:
+
+```
+.
+├── Fes.toml
+├── README.md
+└── www
+ └── index.lua
+```
+
+Fes looks for `.lua` files in the `www/` directory. Each file is exposed as a route based on its file name.
+
+## Commands
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :------------------------ | :----------------------------------------------- |
+| `fes run .` | Runs the project at `.` |
+
+## What to learn more?
+
+Check out [Fes's docs](https://docs.vxserver.dev/static/fes.html).
\ No newline at end of file
diff --git a/test/files/markdown/www/index.md b/test/files/markdown/www/index.md
new file mode 100644
index 0000000..70dbadc
--- /dev/null
+++ b/test/files/markdown/www/index.md
@@ -0,0 +1,310 @@
+# Markdown: Syntax
+
+* [Overview](#overview)
+ * [Philosophy](#philosophy)
+ * [Inline HTML](#html)
+ * [Automatic Escaping for Special Characters](#autoescape)
+* [Block Elements](#block)
+ * [Paragraphs and Line Breaks](#p)
+ * [Headers](#header)
+ * [Blockquotes](#blockquote)
+ * [Lists](#list)
+ * [Code Blocks](#precode)
+ * [Horizontal Rules](#hr)
+* [Span Elements](#span)
+ * [Links](#link)
+ * [Emphasis](#em)
+ * [Code](#code)
+ * [Images](#img)
+* [Miscellaneous](#misc)
+ * [Backslash Escapes](#backslash)
+ * [Automatic Links](#autolink)
+
+
+**Note:** This document is itself written using Markdown; you
+can [see the source for it by adding '.text' to the URL](/projects/markdown/syntax.text).
+
+----
+
+## Overview
+
+### Philosophy
+
+Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
+
+Readability, however, is emphasized above all else. A Markdown-formatted
+document should be publishable as-is, as plain text, without looking
+like it's been marked up with tags or formatting instructions. While
+Markdown's syntax has been influenced by several existing text-to-HTML
+filters -- including [Setext](http://docutils.sourceforge.net/mirror/setext.html), [atx](http://www.aaronsw.com/2002/atx/), [Textile](http://textism.com/tools/textile/), [reStructuredText](http://docutils.sourceforge.net/rst.html),
+[Grutatext](http://www.triptico.com/software/grutatxt.html), and [EtText](http://ettext.taint.org/doc/) -- the single biggest source of
+inspiration for Markdown's syntax is the format of plain text email.
+
+## Block Elements
+
+### Paragraphs and Line Breaks
+
+A paragraph is simply one or more consecutive lines of text, separated
+by one or more blank lines. (A blank line is any line that looks like a
+blank line -- a line containing nothing but spaces or tabs is considered
+blank.) Normal paragraphs should not be indented with spaces or tabs.
+
+The implication of the "one or more consecutive lines of text" rule is
+that Markdown supports "hard-wrapped" text paragraphs. This differs
+significantly from most other text-to-HTML formatters (including Movable
+Type's "Convert Line Breaks" option) which translate every line break
+character in a paragraph into a ` ` tag.
+
+When you *do* want to insert a ` ` break tag using Markdown, you
+end a line with two or more spaces, then type return.
+
+### Headers
+
+Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
+
+Optionally, you may "close" atx-style headers. This is purely
+cosmetic -- you can use this if you think it looks better. The
+closing hashes don't even need to match the number of hashes
+used to open the header. (The number of opening hashes
+determines the header level.)
+
+
+### Blockquotes
+
+Markdown uses email-style `>` characters for blockquoting. If you're
+familiar with quoting passages of text in an email message, then you
+know how to create a blockquote in Markdown. It looks best if you hard
+wrap the text and put a `>` before every line:
+
+> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
+> consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
+> Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
+>
+> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
+> id sem consectetuer libero luctus adipiscing.
+
+Markdown allows you to be lazy and only put the `>` before the first
+line of a hard-wrapped paragraph:
+
+> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
+consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
+Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
+
+> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
+id sem consectetuer libero luctus adipiscing.
+
+Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
+adding additional levels of `>`:
+
+> This is the first level of quoting.
+>
+> > This is nested blockquote.
+>
+> Back to the first level.
+
+Blockquotes can contain other Markdown elements, including headers, lists,
+and code blocks:
+
+> ## This is a header.
+>
+> 1. This is the first list item.
+> 2. This is the second list item.
+>
+> Here's some example code:
+>
+> return shell_exec("echo $input | $markdown_script");
+
+Any decent text editor should make email-style quoting easy. For
+example, with BBEdit, you can make a selection and choose Increase
+Quote Level from the Text menu.
+
+
+### Lists
+
+Markdown supports ordered (numbered) and unordered (bulleted) lists.
+
+Unordered lists use asterisks, pluses, and hyphens -- interchangably
+-- as list markers:
+
+* Red
+* Green
+* Blue
+
+is equivalent to:
+
++ Red
++ Green
++ Blue
+
+and:
+
+- Red
+- Green
+- Blue
+
+Ordered lists use numbers followed by periods:
+
+1. Bird
+2. McHale
+3. Parish
+
+It's important to note that the actual numbers you use to mark the
+list have no effect on the HTML output Markdown produces. The HTML
+Markdown produces from the above list is:
+
+If you instead wrote the list in Markdown like this:
+
+1. Bird
+1. McHale
+1. Parish
+
+or even:
+
+3. Bird
+1. McHale
+8. Parish
+
+you'd get the exact same HTML output. The point is, if you want to,
+you can use ordinal numbers in your ordered Markdown lists, so that
+the numbers in your source match the numbers in your published HTML.
+But if you want to be lazy, you don't have to.
+
+To make lists look nice, you can wrap items with hanging indents:
+
+* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+ Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
+ viverra nec, fringilla in, laoreet vitae, risus.
+* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+ Suspendisse id sem consectetuer libero luctus adipiscing.
+
+But if you want to be lazy, you don't have to:
+
+* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
+viverra nec, fringilla in, laoreet vitae, risus.
+* Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+
+List items may consist of multiple paragraphs. Each subsequent
+paragraph in a list item must be indented by either 4 spaces
+or one tab:
+
+1. This is a list item with two paragraphs. Lorem ipsum dolor
+ sit amet, consectetuer adipiscing elit. Aliquam hendrerit
+ mi posuere lectus.
+
+ Vestibulum enim wisi, viverra nec, fringilla in, laoreet
+ vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
+ sit amet velit.
+
+2. Suspendisse id sem consectetuer libero luctus adipiscing.
+
+It looks nice if you indent every line of the subsequent
+paragraphs, but here again, Markdown will allow you to be
+lazy:
+
+* This is a list item with two paragraphs.
+
+ This is the second paragraph in the list item. You're
+only required to indent the first line. Lorem ipsum dolor
+sit amet, consectetuer adipiscing elit.
+
+* Another item in the same list.
+
+To put a blockquote within a list item, the blockquote's `>`
+delimiters need to be indented:
+
+* A list item with a blockquote:
+
+ > This is a blockquote
+ > inside a list item.
+
+To put a code block within a list item, the code block needs
+to be indented *twice* -- 8 spaces or two tabs:
+
+* A list item with a code block:
+
+
+
+### Code Blocks
+
+Pre-formatted code blocks are used for writing about programming or
+markup source code. Rather than forming normal paragraphs, the lines
+of a code block are interpreted literally. Markdown wraps a code block
+in both `
` and `` tags.
+
+To produce a code block in Markdown, simply indent every line of the
+block by at least 4 spaces or 1 tab.
+
+This is a normal paragraph:
+
+ This is a code block.
+
+Here is an example of AppleScript:
+
+ tell application "Foo"
+ beep
+ end tell
+
+A code block continues until it reaches a line that is not indented
+(or the end of the article).
+
+Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
+are automatically converted into HTML entities. This makes it very
+easy to include example HTML source code using Markdown -- just paste
+it and indent it, and Markdown will handle the hassle of encoding the
+ampersands and angle brackets. For example, this:
+
+
+
+Regular Markdown syntax is not processed within code blocks. E.g.,
+asterisks are just literal asterisks within a code block. This means
+it's also easy to use Markdown to write about Markdown's own syntax.
+
+```
+tell application "Foo"
+ beep
+end tell
+```
+
+## Span Elements
+
+### Links
+
+Markdown supports two style of links: *inline* and *reference*.
+
+In both styles, the link text is delimited by [square brackets].
+
+To create an inline link, use a set of regular parentheses immediately
+after the link text's closing square bracket. Inside the parentheses,
+put the URL where you want the link to point, along with an *optional*
+title for the link, surrounded in quotes. For example:
+
+This is [an example](http://example.com/) inline link.
+
+[This link](http://example.net/) has no title attribute.
+
+### Emphasis
+
+Markdown treats asterisks (`*`) and underscores (`_`) as indicators of
+emphasis. Text wrapped with one `*` or `_` will be wrapped with an
+HTML `` tag; double `*`'s or `_`'s will be wrapped with an HTML
+`` tag. E.g., this input:
+
+*single asterisks*
+
+_single underscores_
+
+**double asterisks**
+
+__double underscores__
+
+### Code
+
+To indicate a span of code, wrap it with backtick quotes (`` ` ``).
+Unlike a pre-formatted code block, a code span indicates code within a
+normal paragraph. For example:
+
+Use the `printf()` function.
diff --git a/test/files/minimal/Fes.toml b/test/files/minimal/Fes.toml
new file mode 100644
index 0000000..6ccae2a
--- /dev/null
+++ b/test/files/minimal/Fes.toml
@@ -0,0 +1,5 @@
+[app]
+
+name = "minimal"
+version = "0.0.1"
+authors = ["fSD"]
diff --git a/test/files/minimal/README.md b/test/files/minimal/README.md
new file mode 100644
index 0000000..8043645
--- /dev/null
+++ b/test/files/minimal/README.md
@@ -0,0 +1,33 @@
+# minimal
+
+```
+fes new minimal
+```
+
+> **Know what you are doing?** Delete this file. Have fun!
+
+## Project Structure
+
+Inside your Fes project, you'll see the following directories and files:
+
+```
+.
+├── Fes.toml
+├── README.md
+└── www
+ └── index.lua
+```
+
+Fes looks for `.lua` files in the `www/` directory. Each file is exposed as a route based on its file name.
+
+## Commands
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :------------------------ | :----------------------------------------------- |
+| `fes run .` | Runs the project at `.` |
+
+## What to learn more?
+
+Check out [Fes's docs](https://docs.vxserver.dev/static/fes.html).
\ No newline at end of file
diff --git a/test/files/minimal/www/index.lua b/test/files/minimal/www/index.lua
new file mode 100644
index 0000000..5e0506d
--- /dev/null
+++ b/test/files/minimal/www/index.lua
@@ -0,0 +1 @@
+return "Hello, World!"