pages

.github/workflows/pages.yml

@@ -0,0 +1,42 @@
+name: Publish page
+
+permissions:
+  actions: none
+  checks: none
+  contents: none
+  deployments: none
+  id-token: none
+  issues: none
+  discussions: none
+  packages: none
+  pages: write
+  pull-requests: none
+  repository-projects: none
+  security-events: none
+  statuses: none
+
+on:
+  push:
+    tags:
+      - v*
+
+env:
+  CARGO_TERM_COLOR: always
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+      - uses: actions/checkout@v3
+
+      - name: install dependencies
+        run: cargo install dioxus-cli
+
+      - name: publish
+        run: dx build --release

.gitignore

@@ -5,3 +5,4 @@ out.txt
 deleteme*
 .env
 dist
+docs

Dioxus.toml

@@ -0,0 +1,42 @@
+[application]
+
+# dioxus project name
+name = "ssd_web"
+
+# default platfrom
+# you can also use `dx serve/build --platform XXX` to use other platform
+# value: web | desktop
+default_platform = "web"
+
+# Web `build` & `serve` dist path
+out_dir = "docs"
+
+# resource (static) file folder
+asset_dir = "public"
+
+[web.app]
+
+# HTML title tag content
+title = "Dioxus | An elegant GUI library for Rust"
+base_path = "ssd"
+
+[web.watcher]
+
+index_on_404 = true
+
+watch_path = ["src", "examples"]
+
+# include `assets` in web platform
+[web.resource]
+
+# CSS style file
+style = []
+
+# Javascript code file
+script = []
+
+[web.resource.dev]
+
+# Javascript code file
+# serve: [dev-server] only
+script = []

README.md

@@ -13,7 +13,7 @@ which was really error prone and annoying to work with. So I wrote a small (clos
 code generator using [D](https://dlang.org/), [SDLang](https://sdlang.org/) and a template engine.
 
 After a few months it was clear, that the template engine made certain things way harder to maintain and reason
-about. Which is why I decided to rewrite the whole thing in C#. Thio time I used a custom parser to allow for more
+about. Which is why I decided to rewrite the whole thing in C#. This time I used a custom parser to allow for more
 streamlined data files and I built the generator in a way, that the actual code generation would be done through
 C# DLLs. This way you could still use a template engine if you want by embedding it into a DLL and using that.
 

src/main.rs

@@ -83,7 +83,7 @@ which was really error prone and annoying to work with. So I wrote a small (clos
 code generator using "#r a {href: "https://dlang.org/", "D" } ", " a { href: "https://sdlang.org/", "SDLang" } " and a template engine." }
 
 p { r#"After a few months it was clear, that the template engine made certain things way harder to maintain and reason
-about. Which is why I decided to rewrite the whole thing in C#. Thio time I used a custom parser to allow for more
+about. Which is why I decided to rewrite the whole thing in C#. This time I used a custom parser to allow for more
 streamlined data files and I built the generator in a way, that the actual code generation would be done through
 C# DLLs. This way you could still use a template engine if you want by embedding it into a DLL and using that."#r }