Fix #367: Add upcoming documentation files

.github/dev-docs/README.markdown

@@ -0,0 +1,5 @@
+# Upcoming Hyde Documentation
+
+## WARNING You're browsing the documentation for an upcoming version of HydePHP.
+
+### The documentation and features of this release are subject to change without notice.

.github/dev-docs/architecture-concepts.md

@@ -0,0 +1,94 @@
+---
+priority: 5
+category: "Getting Started"
+---
+
+# Some key concepts in Hyde
+
+## The HydeCLI
+
+When you are not writing Markdown and Blade, most of your interactions with Hyde will be through the
+Hyde Command Line Interface (CLI). 
+Since the CLI is based on the Laravel Artisan Console, so you may actually already be familiar with it.
+
+You should take a look at [the Console Commands page](console-commands.html)
+to learn more and see the available commands and their usage.
+
+```bash
+php hyde <command> [--help]
+```
+
+## Directory structure
+
+To take full advantage of the framework, it may first be good to familiarize ourselves with the directory structure.
+
+```
+// torchlight! {"lineNumbers": false}
+├── _docs  // For documentation pages              
+├── _posts // For blog posts
+├── _pages // For static Markdown and Blade pages
+├── _media // Store static assets to be copied to the build directory
+├── _site  // The build directory where your compiled site will be stored
+├── config // Configuration files for Hyde and integrations
+├── resources/assets // Location for Laravel Mix source files (optional)
+└── resources/views/components // Location for Blade components (optional)
+```
+
+> Note that the `_site` directory is emptied every time you run the `hyde build` command.
+> It's intended that you keep the directory out of your VCS, for example by adding it to your .gitignore file.
+
+
+## File Autodiscovery
+
+Content files, meaning source Markdown and Blade files, are automatically
+discovered by Hyde and compiled to HTML when building the site.
+This means that you don't need to worry about routing and controllers!
+
+The directory a source file is in will determine the Blade template that is used to render it.
+
+Here is an overview of the content source directories, the output directory of the compiled files,
+and the file extensions supported by each. Files starting with an `_underscore` are ignored.
+
+| Page/File Type | Source Directory | Output Directory | File Extensions     |
+|----------------|------------------|------------------|---------------------|
+| Static Pages   | `_pages/`        | `_site/`         | `.md`, `.blade.php` |
+| Blog Posts     | `_posts/`        | `_site/posts/`   | `.md`               |
+| Documentation  | `_docs/`         | `_site/docs/`    | `.md`               |
+| Media Assets   | `_media/`        | `_site/media/`   | See full list below |
+
+<small>
+<blockquote>
+Media file types supported: `.png`, `.svg`, `.jpg`, `.jpeg`, `.gif`, `.ico`, `.css`, `.js`
+</blockquote>
+</small>
+
+## Convention over Configuration
+
+Hyde favours the "Convention over Configuration" paradigm and thus comes preconfigured with sensible defaults.
+However, Hyde also strives to be modular and endlessly customizable hackable if you need it. 
+Take a look at the [customization and configuration guide](customization.html) to see the endless options available!
+
+## Front Matter
+
+All Markdown content files support Front Matter. Blog posts for example make heavy use of it.
+
+The specific usage and schemas used for pages are documented in their respective documentation,
+however, here is a primer on the fundamentals.
+
+- Front matter is stored in a block of YAML that starts and ends with a `---` line.
+- The front matter should be the very first thing in the Markdown file.
+- Each key-pair value should be on its own line.
+
+**Example:**
+```markdown
+---
+title: "My New Post"
+author:
+  name: "John Doe"
+  website: https://mrhyde.example.com
+---
+
+## Markdown comes here
+
+Lorem ipsum dolor sit amet, etc.
+```

.github/dev-docs/blog-posts.md

@@ -0,0 +1,221 @@
+---
+label: "Creating Blog Posts"
+priority: 10
+category: "Creating Content"
+---
+
+# Creating Blog Posts
+
+## Introduction to Hyde Posts
+
+Making blog posts with Hyde is easy. At the most basic level,
+all you need is to add a Markdown file to your `_posts` folder.
+
+To use the full power of the Hyde post module however,
+you'll want to add YAML Front Matter to your posts.
+
+You can scaffold posts with automatic front matter using the HydeCLI:
+```bash
+php hyde make:post
+```
+Learn more about scaffolding posts, and other files, in the [console commands](console-commands.html) documentation.
+
+
+## Short Video Tutorial
+
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/gjpE1U527h8" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+## Best Practices and Hyde Expectations
+
+Since Hyde does a lot of things automatically, there are some things you may need
+to keep in mind when creating blog posts so that you don't get unexpected results.
+
+### Filenames
+
+- Markdown post files are stored in the `_posts` directory
+- The filename is used as the filename for the compiled HTML
+- Filenames should use `kebab-case-slug` followed by the extension `.md`
+- Files prefixed with `_underscores` are ignored by Hyde
+- Your post will be stored in `_site/posts/<slug>.html`
+
+**Example:**
+```bash
+✔ _posts/hello-world.md # Valid and will be compiled to _site/posts/hello-world.html
+```
+
+### Front Matter
+
+Front matter is optional, but highly recommended for blog posts.
+
+You can read more about the Front Matter format in the [Front Matter documentation](architecture-concepts.html#front-matter).
+Here is a quick primer:
+
+- Front matter is stored in a block of YAML that starts and ends with a `---` line.
+- The front matter should be the very first thing in the Markdown file.
+- Each key-pair value should be on its own line.
+- The front matter is used to construct dynamic HTML markup for the post as well as meta tags and post feeds.
+  You are encouraged to look at the compiled HTML to learn and understand how your front matter is used.
+
+
+**Example:**
+```markdown
+---
+title: "My New Post"
+---
+
+## Markdown comes here
+```
+
+You can use the `php hyde make:post` command to automatically generate the front matter based on your input.
+
+
+## A first look at Front Matter
+
+Before digging in deeper on all the supported front matter options,
+let's take a look at what a basic post with front matter looks like.
+
+This file was created using the `make:post` by hitting the `Enter` key to use
+all the defaults (with some extra lorem ipsum to illustrate).
+
+```markdown {: filepath="_posts/my-new-post.md"}
+---
+title: My New Post
+description: A short description used in previews and SEO
+category: blog
+author: Mr. Hyde
+date: 2022-05-09 18:38
+---
+
+## Write your Markdown here
+
+Lorem ipsum dolor sit amet, consectetur adipisicing elit.
+Autem aliquid alias explicabo consequatur similique,
+animi distinctio earum ducimus minus, magnam.
+```
+
+### How the Front Matter is used
+
+The front matter is used to construct dynamic HTML markup for the post as well as meta tags and post feeds.
+
+You are encouraged to look at the compiled HTML to learn and understand how your front matter is used.
+
+### Front matter syntax
+
+Here is a quick reference of the syntax Hyde uses and expects:
+
+```markdown
+---
+key: value
+string: "quoted string"
+boolean: true
+integer: 100
+array:
+  key: value
+  key: value
+---
+```
+
+## Supported Front Matter properties
+
+### Post Front Matter Schema
+
+Here is a quick reference of the supported front matter properties.
+Keep on reading to see further explanations, details, and examples. 
+
+
+| **KEY NAME**   | **VALUE TYPE** | **EXAMPLE / FORMAT**             |
+|----------------|----------------|----------------------------------|
+| `title`        | string         | "My New Post"                    |
+| `description`  | string         | "A short description"            |
+| `category`     | string         | "my favorite recipes"            |
+| `date`         | string         | "YYYY-MM-DD [HH:MM]"             |
+| `author`       | string/array   | _See [author](#author) section_  |
+| `image`        | string/array   | _See [image](#image) section_    |
+
+
+Note that YAML here is pretty forgiving. In most cases you do not need to wrap strings
+in quotes, but it can help in certain edge cases, thus they are included here.
+
+In the examples below, when there are multiple keys, they signify various ways to use the parameter.
+
+### Title
+
+```yaml
+title: "My New Post"
+```
+
+
+### Description
+
+```yaml
+description: "A short description used in previews and SEO"
+```
+
+
+### Category
+
+```yaml
+category: blog
+category: "My favorite recipes"
+```
+
+
+### Date
+
+```yaml
+date: "2022-01-01 12:00" 
+date: "2022-01-01" 
+```
+
+
+### Author
+
+```yaml
+author: "Mr. Hyde" # Arbitrary name displayed "as is"
+author: mr_hyde # Username defined in `authors.yml` config
+author: # Array of author data
+  name: "Mr. Hyde" 
+  username: mr_hyde 
+  website: https://mrhyde.example.com 
+```
+
+When specifying an array you don't need all the sub-properties.
+The example just shows all the supported values. Array values here
+will override the values in the `authors.yml` config.
+
+### Image
+
+```yaml
+image: image.jpg # Expanded by Hyde to `_media/image.jpg` and is resolved automatically
+image: https://cdn.example.com/image.jpg # Full URL starting with `http(s)://`)
+image:
+  path: image.jpg
+  uri: https://cdn.example.com/image.jpg # Takes precedence over `path`
+  description: "Alt text for image"
+  title: "Tooltip title"
+  copyright: "Copyright (c) 2022"
+  license: "CC-BY-SA-4.0"
+  licenseUrl: https://example.com/license/
+  credit: https://photographer.example.com/
+  author: "John Doe"
+```
+
+When supplying an image with a local image path, the image is expected to be stored in the `_media/` directory.
+
+The image will be used as the cover image, and any array data is constructed into a dynamic fluent caption,
+and injected into post and page metadata.
+
+> See [posts/introducing-images](https://hydephp.com/posts/introducing-images.html)
+> for a detailed blog post with examples and schema information!
+{ .info }
+
+
+## Using images in posts
+
+To use images stored in the `_media/` directory, you can use the following syntax:
+
+```markdown
+![Image Alt](../media/image.png "Image Title") # Note the relative path
+```
+
+To learn more, check out the [chapter in managing assets](managing-assets.html#managing-images)