You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _drafts/how-does-it-work.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,13 @@
1
+
# How does it work
1
2
2
-
The directory you place your file in will determine what Blade template to render the content into, as well as the filepath for the compiled file.
3
+
## Hyde is installed similarly to Laravel
4
+
Installation is easy by using composer. The installer creates a directory with all the files you need to get started, including Blade views and compiled Tailwind assets.
5
+
6
+
## Creating content is easy with Markdown
7
+
Put your Markdown or Blade content in the source directories. The directory you use will determine the Blade layout and output path that will be used.
8
+
9
+
> For example, a file stored as `_posts/hello-world.md` will be compiled using the `post.blade.php` layout and saved as `_site/posts/hello-world.html`.
10
+
11
+
## Compiling is initiated with the HydeCLI
12
+
When running the build command, Hyde will take your source files and intelligently compiles them into the output directory. During this build navigation menus and sidebars will be generated automatically.
3
13
4
-
> For example, a file stored as `_posts/hello-world.md` will be compiled into the `post.blade.php` layout and saved as `_site/posts/hello-world.html`.
0 commit comments