Town layouts present a curious case of being especially large. Bundling them into the standard dynamic response wouldn't work - thankfully there's a sequenced solution. Having solved for roads (preliminary conversion to SVGs) this handles the other big contributor to the map's initialization (Cloudfare investigation was for static assets). Testing that (layouts additional sequence and beginnings of a viewer) today while determining best approaches for v2 & Mappy.
Due to having all except a few magical pieces of the FCS (magic numbers for the RAW_ACTIONS) and the enforced limitations on the map's content browser... I'll be making a more complete WebFCS page as a dedicated browser for viewing all contents, including those which did not qualify for usage on the map.
Favoriting panels (manifest-based) is now functional! (Relations Journal could use some work.)
;More recent notes
=1/26=
Tested the worker to satisfaction. Nice optimization outcomes & the limited scope means little else need be done here. Gained some extra insight on header management (in Nginx). Busywork regarding town layouts, Caravan and revising the map's initialization for the v2 + CDN pipeline. Here's a few other tangents in the mix...
Exploring the usage of [https://flarum.org/ Flarum] for an external forum. Conceptually funnels all social activity ''outside the knowledge base'' whilst maintaining an integrated companionship. Ideally speaking - this comes in the form of the forums being woven into the skin link-redirect schema, meaning then discussions, comments and wiki accounts engage with Flarum when searching for discussion/to discuss. This, in theory, eliminates a lot of extension busywork, database noise and obligation to use the wiki itself for such social functions. Instead then, a ''proper'' software package is used more in line with the best of what modern forums can offer. The server ecosystem is already completely setup for its usage - the main challenge lives in creating a SSO system.
# Stylizer
----
# Manifestor's API + Map Orchestration
;Other recent activities
----
Let me paint a general picture for you -
#'''February''' - Methodical update, enhancement & rework (if necessary) of the existing features.
#'''March''' - Optimization, bug-testing, stress testing and v2 + PWA update process. (Preliminary work done here - functional rebuild first.)
#'''April''' - Style alignment. 4-theme (possibly more). Visual refinements & reworks. (The wiki can be cleanly reset once ContextSharing & v2 are done being teste. Not contingent, just nice to know.)
#'''May''' - The map is ready for Cloudflare deployment (full proxy & caching) - further design considerations go into the testing realm.
----
:Looked at setting up a server fallback schema -> NYC -> Atlanta -> San Fran
:Not load balancing per se - in cases, if ever, the host data center is rendered unavailable the server ''can'' be migrated elsewhere. (That said, it's not necessary at the moment - it's merely feasible if found so.)
----
:'''Extensions Mix'''
::''Caravan''
:::Adding favorites for panel browsing (on the map).
::''ContextSharing''
:::Delivers specific content from a wiki page to the map for embedded display (within info & content panels).
::''Mappy'' (Paused)
----
;Exploring...
;Earlier notes
[https://lit.dev/ Lit]
In the depths of navigating the Cloudflare ecosystem. Examining what can be done with workers & beyond for edge caching. Did you know serverless functions can be managed almost entirely externally? That took some mental model migration. An early look at setting up the smart switch for optimized request delivery & processing is the focal point right now. The task map for what's to be done with the map is largely settled. Doing it ideally means making that initial API request and page loading nice & quick. The wiki comes back into play as the map is "wired" to connect to the corresponding page targets (see the Stobe landmark). Various upgrades to Caravan and then the creation of the modding portals follows. Yes, a mass deletion campaign of the test templates will occur, because... the Wikipedia templates are often overbuilt for our needs / inappropriate for the Citizen skin, etc...
# Preliminary development of the Mappy {{emoji|1F60A}} extension. (Dedicated extension for consuming JSON and delivering wiki-ready maps for embedding in various formats... This extension will be released publicly, shared freely and built with a user-facing input & control schema.)
[https://component-party.dev/ Components]
# Upstream-Downstream for Map development (adjusting version control conventions because of ongoing creation of styling & minification process).
# Cloudflare Workers, first on the map's upstream, the into the map's manifest pipeline, then applied as appropriate respective to the wiki ecosystem (I'm on the free tier!).
# Map development itself is a known quantity. Progress temporarily pinned for workflow adjustments.
# ''<big>Personal note</big>'', Q1 is extremely busy for me. Most of the three months will be combatting the onslaught of snow and finishing up the projects wholly separate from these activities. The good news is I'm in a ''just as planned'' situation for those (mostly) and am really in a holding pattern until they resolve. Once they do, ramp to cruising altitude and maintain, because there's nothing else in the way any longer.
[[File:RoadSmithv7.png|center|Road editor progress...Consumes polylines and allows editing thereafter.|1416x1416px|border|frameless]]
& migration to Typescript. (Vite via JS, then backworking).
----
{{Center|'''SVGs reign supreme!'''}}
----
[[File:OpenPanels.png|center|A look at the on-map panels and main menu after Favoriting functionality was enabled.|thumb|1200x1200px]]
----
[[File:MainMenuOverhaul.png|center|Earliest (working) version of the combined right & left menus, composing the main menu, the "default" format for the desktop presentation of the map.|thumb|1200x1200px]]
----
[[File:MarkerTypes.png|center|PNG icons matched to markers as according to their type classification.|thumb|1200x1200px]]
----
[[File:TownLayouts-v2.png|center|Geometry updates to the Town Layout viewer - making more advanced layouts comprehensible.|thumb|1200x1200px]]
----
[[File:SampleTownLayout.png|center|Initial proof of concept for town layout viewer.|thumb|1200x1200px]]
----
[[File:ModifiedRoads.png|center|Extraction and visualization of a modified road network before cleanup. Native (green), custom (yellow) and modified (purple).|thumb|1200x1200px]]
:A. See after completion of map segment. Task Map B.
'''6. SDK'''
:A. Pinned due to ongoing workflow change. Task Map B.
----
'''Continuing Education'''
:''Bash''
::https://www.youtube.com/watch?v=Sx9zG7wa4FA
:''nginx''
::https://nginx.org/en/docs/beginners_guide.html
:''Varnish''
::https://vinyl-cache.org/docs/6.0/
:''SVGs''
::https://www.svgrepo.com/tools/
:''JSON''
::https://www.json.org/json-en.html
::''Personal note'', almost the entire site and external tooling operate based upon generation and exchange of JSON. It is, much like SVGs, utterly critical to how this site and the rest of the ecosystem operates.
::[https://devclass.com/2025/05/29/microsoft-designates-blazor-as-its-main-future-investment-in-web-ui-for-net/ Why I've chosen Blazor for 2026 and beyond]
:Code Style
:::An aside. I am an advocate for minification and making source maps available. This comes loaded with an '''extremely opinionated''' code style that is wholly divergent from industry standard (AirBnB style) formats. Spatial specificity (interchangeable with line specificity and explicit spatial containment), is a kind of mixed format derived from JSON's presentation, reapplied across other web native languages (primarily HTML, CSS & Javascript). There are goofy reasons for its existence, which I'm happy to share!
:::# I do a significant amount of debugging in my browser. The interface appears to the right side of my screen. Tall, vertically focused, dense code is readable insofar as that it requires no horizontal scrolling. Logic can be dense so long as it's communicated.
:::# I'm privy to split views and multiple windows, causing wide lines across multiple screens to require adjustment and constant panning to view.
:::# Whitespace does exactly nothing '''for me'''. In fact, it's rather unhelpful! Minimizing whitespace and offsetting/replacing with new line breaks removes what feels like a rollercoaster across screen space.
:::# I have poor eyesight. Larger text helps - this inherently causes horizontal space to become a luxury when accounting for the aforementioned situations. Equalized line starts are really "no different" when brackets are provided new lines by default, meaning there's no hidden bracket ever lingering off-screen to the right.
:::# When a block is functional and finished its format is '''irrelevant''' respective to what will occur in the minification process. Likewise, source maps can unwind any applied style and reformatted to a more "traditional" presentation for public viewing.
:::# My preferences are not intended to be embraced by anyone - they're '''my''' preferences. Nevertheless, because I do intend to make the format "known" (in terms of having a public reference and a knowledge base to point to), so that it can be refined, iterated upon, have a thorough ruleset and be comprehended by myself and others... a doc site will be made to show and explain! Importantly, I'll be building in a transmutation tool for converting to and from the format (for my own purposes, though anyone would be welcome to use it).
[[Category:Pages using center with no arguments]]
[[Category:Pages using center with unknown parameters| Prd]]
Latest revision as of 18:53, 26 January 2026
I can't stay long, whispered the butterfly, but I'll put a memory in your heart.
Exploring the usage of Flarum for an external forum. Conceptually funnels all social activity outside the knowledge base whilst maintaining an integrated companionship. Ideally speaking - this comes in the form of the forums being woven into the skin link-redirect schema, meaning then discussions, comments and wiki accounts engage with Flarum when searching for discussion/to discuss. This, in theory, eliminates a lot of extension busywork, database noise and obligation to use the wiki itself for such social functions. Instead then, a proper software package is used more in line with the best of what modern forums can offer. The server ecosystem is already completely setup for its usage - the main challenge lives in creating a SSO system.
Other recent activities
Let me paint a general picture for you -
February - Methodical update, enhancement & rework (if necessary) of the existing features.
March - Optimization, bug-testing, stress testing and v2 + PWA update process. (Preliminary work done here - functional rebuild first.)
April - Style alignment. 4-theme (possibly more). Visual refinements & reworks. (The wiki can be cleanly reset once ContextSharing & v2 are done being teste. Not contingent, just nice to know.)
May - The map is ready for Cloudflare deployment (full proxy & caching) - further design considerations go into the testing realm.
Looked at setting up a server fallback schema -> NYC -> Atlanta -> San Fran
Not load balancing per se - in cases, if ever, the host data center is rendered unavailable the server can be migrated elsewhere. (That said, it's not necessary at the moment - it's merely feasible if found so.)
Extensions Mix
Caravan
Adding favorites for panel browsing (on the map).
ContextSharing
Delivers specific content from a wiki page to the map for embedded display (within info & content panels).
& migration to Typescript. (Vite via JS, then backworking).
SVGs reign supreme!
A look at the on-map panels and main menu after Favoriting functionality was enabled.Earliest (working) version of the combined right & left menus, composing the main menu, the "default" format for the desktop presentation of the map.PNG icons matched to markers as according to their type classification.Geometry updates to the Town Layout viewer - making more advanced layouts comprehensible.Initial proof of concept for town layout viewer.Extraction and visualization of a modified road network before cleanup. Native (green), custom (yellow) and modified (purple).Colorful roads, borders, resources & weather layers.Road editor progress...Consumes polylines and allows editing thereafter.Painting & Planning tools for the map.
