Crates.io | lssg-lib |
lib.rs | lssg-lib |
version | 0.1.0 |
source | src |
created_at | 2023-11-28 00:37:46.110397 |
updated_at | 2023-11-28 00:37:46.110397 |
description | Lyr's Static Site Generator Library |
homepage | |
repository | https://github.com/Lyr-7D1h/lssg |
max_upload_size | |
id | 1051450 |
size | 117,471 |
The idea is to generate static html, css, js files based on custom markdown format.
This uses a custom markdown parser which will not necessarly follow official specifications. I'm making it to the point that it is usable for me, PR's are welcome! See LMarkdown
down for more information.
Install binary
git clone git@github.com:Lyr-7D1h/lssg.git
cd lssg
cargo install --path .
Generate static files
lssg {PATH_TO_INDEX_MARKDOWN_FILE} {PATH_TO_OUTPUT_FOLDER}
This is how you would generate lyrx from its content
cd examples/lyrx
lssg ./content/home.md ./build
You can also use links to markdown to generate content
lssg https://raw.githubusercontent.com/Lyr-7D1h/lssg/wip/examples/lyrx/home.md ./build
[!NOTE] Any links from the input markdown file to other markdown files have to be contained within the parent folder of your input markdown file
LMarkdown tries to follow Commonmark markdown specifications although deviating wherever it makes sense to make page renderning easier.
Structure of a lmarkdown file:
<!--
{MODULE_CONFIG}
-->
{MARKDOWN}
eg.
<!--
[default]
title="This is the html title"
[blog]
-->
<!--
The first comment on a page is seen as module configuration and is parsed as toml
it has the following format:
[{module_identifier}]
{options}
-->
# Just some header in file
<!-- All HTML comments are ignore in output -->
<!-- The following will generate `http://{root}/test` url based on the markdown file -->
[Check out my other page](./test.md)
<!-- So this in html will turn into `<a href="./test">Check out my other page</a>` -->
In short this is what happens when executing LSSG
Given index markdown file path
|
Sitetree: Recursively find links to resources in parsed pages and stylesheets (stylesheets, fonts, icons, other pages)
|
Sitetree: Add these resources as nodes into Sitetree
|
Go through all nodes in tree
if resources
Copy resource
if page => use modular HtmlRenderer to turn lmarkdown tokens into html, and write to file
HtmlRenderer: Create Domtree
|
HtmlRenderer: Delecate modification of Domtree to modules based on LMarkdown Tokens
|
BlogModule: Render Token if applicable
|
DefaultModule: Fallback rendering of Token, it should render every kind of Token
- references to root don't work