website-2 Dynamic Site
website.git · Tickets
A Website Ticket (Triaged):
Ticket · History
- September 14, 2026 Created (title: Dynamic Site)
Changes
@@ -0,0 +1,44 @@+---+title: Dynamic Site+permalink: website/dynamic-site/+ticket: open+---++*A s::[[website-tickets|Website Ticket]] (Open):*++**Ticket** \| s::[[website-dynamic-site-history|History]]++## Symptoms++This site is currently statically generated, which has several downsides:++- The static site generator takes a long time to run due to the number of pages being generated. This has been slowly increasing over time, and is becoming more and more burdensome.+- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches+- The router makes multiple requests where it should only make one+- The SPA logic makes one request for every new link a user ever sees, which may be dozens per page. These should be consolidated into one, or at least fewer, requests. While the javascript app is being rewritten, several things could be improved - *ticket TBD*+- Automating any part of the site is very difficult, as it requires creating a ruby plugin. The Git fronted is implemented this way, and it shows in its lack of growth.+- The site content must obviously be... static, which is quite limiting+- Certain features of the site require javascript, such as the "back" links throughout the site+- Redirects are done in html, which is slow, causes flashing, and may work poorly without js. Redirects should be done via http.++With the ability for static content, some new interesting things could be made:+- As mentioned earlier, a better git frontend, +- Chat room?+- Interactive site-wide games?++Many more things could be automated:+- "Projects" with links to git, tickets, etc.+- Ticket boilerplate+- Modify Dates?+- Permalinks+- Etc.++## Problem?++The site is unable to grow due to being statically generated, which is a relic of its history.++## Implementation++As all pages are promised to be s::[[Permalinks]], the site must be rewritten while keeping full parity.++After the server has been written, it can be swapped out with the old static server. - September 15, 2026 Edited
Changes
@@ -13,9 +13,8 @@ This site is currently statically generated, which has several downsides: - The static site generator takes a long time to run due to the number of pages being generated. This has been slowly increasing over time, and is becoming more and more burdensome.-- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches-- The router makes multiple requests where it should only make one-- The SPA logic makes one request for every new link a user ever sees, which may be dozens per page. These should be consolidated into one, or at least fewer, requests. While the javascript app is being rewritten, several things could be improved - *ticket TBD*+- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches or commit history.+- The SPA logic makes one request for every new link a user ever sees, which may be dozens per page. These should be consolidated into one, or at least fewer, requests. While the javascript app is being rewritten, several things could also be improved - *ticket TBD* - Automating any part of the site is very difficult, as it requires creating a ruby plugin. The Git fronted is implemented this way, and it shows in its lack of growth. - The site content must obviously be... static, which is quite limiting - Certain features of the site require javascript, such as the "back" links throughout the site@@ -30,7 +29,9 @@ - "Projects" with links to git, tickets, etc. - Ticket boilerplate - Modify Dates?+- Links to pages that don't yet exist - Permalinks+- Full-screen image pages that work without JS - Etc. ## Problem?@@ -42,3 +43,9 @@ As all pages are promised to be s::[[Permalinks]], the site must be rewritten while keeping full parity. After the server has been written, it can be swapped out with the old static server.++- [x] Set up an HTTP server+- [ ] Route requests+- [ ] Sandbox the program and run it with systemd or something?+- [ ] Ensure full parity with the old website+- [ ] Point nginx to the HTTP server\ No newline at end of file - September 15, 2026 Edited
Changes
@@ -19,6 +19,7 @@ - The site content must obviously be... static, which is quite limiting - Certain features of the site require javascript, such as the "back" links throughout the site - Redirects are done in html, which is slow, causes flashing, and may work poorly without js. Redirects should be done via http.+- The static site generator blindly builds all website files, which is a security vulnerability With the ability for static content, some new interesting things could be made: - As mentioned earlier, a better git frontend, - September 15, 2026 Edited
Changes
@@ -49,4 +49,4 @@ - [ ] Route requests - [ ] Sandbox the program and run it with systemd or something? - [ ] Ensure full parity with the old website-- [ ] Point nginx to the HTTP server\ No newline at end of file+- [ ] Point nginx to the HTTP server - September 15, 2026 Edited
Changes
@@ -22,7 +22,7 @@ - The static site generator blindly builds all website files, which is a security vulnerability With the ability for static content, some new interesting things could be made:-- As mentioned earlier, a better git frontend, +- As mentioned earlier, a better git frontend, js-less back buttons - Chat room? - Interactive site-wide games? - September 15, 2026 Edited
Changes
@@ -21,10 +21,11 @@ - Redirects are done in html, which is slow, causes flashing, and may work poorly without js. Redirects should be done via http. - The static site generator blindly builds all website files, which is a security vulnerability -With the ability for static content, some new interesting things could be made:+With the ability for dynamic content, some new interesting things could be made: - As mentioned earlier, a better git frontend, js-less back buttons - Chat room? - Interactive site-wide games?+- Bug report/feedback buttons for git repos/ticket pages? Many more things could be automated: - "Projects" with links to git, tickets, etc. - September 16, 2026 Edited
Changes
@@ -46,8 +46,6 @@ After the server has been written, it can be swapped out with the old static server. -- [x] Set up an HTTP server-- [ ] Route requests-- [ ] Sandbox the program and run it with systemd or something?+- [x] Implement s::[[website-clojure-server|clojure-server]]+- [ ] Dynamically generate markdown pages - [ ] Ensure full parity with the old website-- [ ] Point nginx to the HTTP server - September 19, 2026 Edited
Changes
@@ -26,6 +26,7 @@ - Chat room? - Interactive site-wide games? - Bug report/feedback buttons for git repos/ticket pages?+- Sending only the font characters needed on first load to reduce total size and time for the font to load in Many more things could be automated: - "Projects" with links to git, tickets, etc. - October 2, 2026 Edited
Changes
@@ -35,6 +35,7 @@ - Links to pages that don't yet exist - Permalinks - Full-screen image pages that work without JS+- "Reference pages" that can be viewed over history and permanently linked to via their sha - Etc. ## Problem? - October 3, 2026 Edited
Changes
@@ -35,7 +35,7 @@ - Links to pages that don't yet exist - Permalinks - Full-screen image pages that work without JS-- "Reference pages" that can be viewed over history and permanently linked to via their sha+- [[Reference Pages|Reference Pages]] - Etc. ## Problem? - October 5, 2026 Edited
Changes
@@ -29,10 +29,10 @@ - Sending only the font characters needed on first load to reduce total size and time for the font to load in Many more things could be automated:-- "Projects" with links to git, tickets, etc.+- "Projects" with tabs - links to git, tickets, etc. - Ticket boilerplate - Modify Dates?-- Links to pages that don't yet exist+- Links to pages that don't yet exist (big for future stuff) - Permalinks - Full-screen image pages that work without JS - [[Reference Pages|Reference Pages]] - October 20, 2026 Edited
Changes
@@ -40,7 +40,9 @@ ## Problem? -The site is unable to grow due to being statically generated, which is a relic of its history.+Not sure.++- The site is unable to grow due to being statically generated, which is a relic of its history. ## Implementation @@ -51,3 +53,4 @@ - [x] Implement s::[[website-clojure-server|clojure-server]] - [ ] Dynamically generate markdown pages - [ ] Ensure full parity with the old website+ - [ ] Make testing environment, put _everything_ in one dir so you can just test thing yk - October 20, 2026 Change formatting
Changes
@@ -35,7 +35,7 @@ - Links to pages that don't yet exist (big for future stuff) - Permalinks - Full-screen image pages that work without JS-- [[Reference Pages|Reference Pages]]+- [[Reference Pages]] - Etc. ## Problem?@@ -46,7 +46,7 @@ ## Implementation -As all pages are promised to be s::[[Permalinks]], the site must be rewritten while keeping full parity.+As all pages are promised to be s::[[permalinks]], the site must be rewritten while keeping full parity. After the server has been written, it can be swapped out with the old static server. - October 20, 2026 Move to automated tickets (renamed from website-dynamic-site.md, status: none → open, category: none → triaged, type: none → addition)
Changes
@@ -1,12 +1,11 @@ --- title: Dynamic Site-permalink: website/dynamic-site/-ticket: open+status: open+category: triaged+type: addition --- -*A s::[[website-tickets|Website Ticket]] (Open):*--**Ticket** \| s::[[website-dynamic-site-history|History]]+**Ticket** \| s::[[website@dynamic-site@history|History]] ## Symptoms @@ -50,7 +49,7 @@ After the server has been written, it can be swapped out with the old static server. -- [x] Implement s::[[website-clojure-server|clojure-server]]+- [x] Implement s::[[website@clojure-server|clojure-server]] - [ ] Dynamically generate markdown pages - [ ] Ensure full parity with the old website - [ ] Make testing environment, put _everything_ in one dir so you can just test thing yk - October 20, 2026 Space and Old flags
Changes
@@ -5,7 +5,7 @@ type: addition --- -**Ticket** \| s::[[website@dynamic-site@history|History]]+**Ticket** \| [[website@dynamic-site@history|History]] ## Symptoms @@ -45,11 +45,11 @@ ## Implementation -As all pages are promised to be s::[[permalinks]], the site must be rewritten while keeping full parity.+As all pages are promised to be [[permalinks]], the site must be rewritten while keeping full parity. After the server has been written, it can be swapped out with the old static server. -- [x] Implement s::[[website@clojure-server|clojure-server]]+- [x] Implement [[website@clojure-server|clojure-server]] - [ ] Dynamically generate markdown pages - [ ] Ensure full parity with the old website - [ ] Make testing environment, put _everything_ in one dir so you can just test thing yk - October 20, 2026 Automate history pages
Changes
@@ -5,8 +5,6 @@ type: addition --- -**Ticket** \| [[website@dynamic-site@history|History]]- ## Symptoms This site is currently statically generated, which has several downsides: - October 20, 2026 Number website tickets created before the numbering system (renamed from website@dynamic-site.md)
Changes
@@ -3,6 +3,8 @@ status: open category: triaged type: addition+redirect_from:+ - website/dynamic-site/ --- ## Symptoms@@ -47,7 +49,7 @@ After the server has been written, it can be swapped out with the old static server. -- [x] Implement [[website@clojure-server|clojure-server]]+- [x] Implement [[website@5|clojure-server]] - [ ] Dynamically generate markdown pages - [ ] Ensure full parity with the old website - [ ] Make testing environment, put _everything_ in one dir so you can just test thing yk - October 20, 2026 Edited
Changes
@@ -12,7 +12,7 @@ This site is currently statically generated, which has several downsides: - The static site generator takes a long time to run due to the number of pages being generated. This has been slowly increasing over time, and is becoming more and more burdensome.-- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches or commit history.+- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches or commit history. (see [[website@7]]) - The SPA logic makes one request for every new link a user ever sees, which may be dozens per page. These should be consolidated into one, or at least fewer, requests. While the javascript app is being rewritten, several things could also be improved - *ticket TBD* - Automating any part of the site is very difficult, as it requires creating a ruby plugin. The Git fronted is implemented this way, and it shows in its lack of growth. - The site content must obviously be... static, which is quite limiting - October 23, 2026 Remove trailing slashes
Changes
@@ -4,7 +4,7 @@ category: triaged type: addition redirect_from:- - website/dynamic-site/+ - website/dynamic-site --- ## Symptoms - October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from website@2.md, title: Dynamic Site → none)
Changes
@@ -1,5 +1,4 @@ ----title: Dynamic Site status: open category: triaged type: addition@@ -12,7 +11,7 @@ This site is currently statically generated, which has several downsides: - The static site generator takes a long time to run due to the number of pages being generated. This has been slowly increasing over time, and is becoming more and more burdensome.-- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches or commit history. (see [[website@7]])+- Git frontend pages only show the main branch and the latest commit of that branch. You can't see active branches or commit history. (see [[website-7 Dynamic Git Frontend]]) - The SPA logic makes one request for every new link a user ever sees, which may be dozens per page. These should be consolidated into one, or at least fewer, requests. While the javascript app is being rewritten, several things could also be improved - *ticket TBD* - Automating any part of the site is very difficult, as it requires creating a ruby plugin. The Git fronted is implemented this way, and it shows in its lack of growth. - The site content must obviously be... static, which is quite limiting@@ -49,7 +48,7 @@ After the server has been written, it can be swapped out with the old static server. -- [x] Implement [[website@5|clojure-server]]+- [x] Implement [[website-5 Clojure Server]] - [ ] Dynamically generate markdown pages - [ ] Ensure full parity with the old website - [ ] Make testing environment, put _everything_ in one dir so you can just test thing yk - October 24, 2026 Replace ticket status, category and resolution with ticket (status: open → none, category: triaged → none)
Changes
@@ -1,6 +1,5 @@ ----status: open-category: triaged+ticket: triaged type: addition redirect_from: - website/dynamic-site