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...
[[File:RoadSmithv7.png|center|Road editor progress...Consumes polylines and allows editing thereafter.|1416x1416px|border|frameless]]
[[File:PaintingToolsPreview.png|frame|center|Painting & Planning tools for the map.]]
Favoriting panels (manifest-based) is now functional! (Relations Journal could use some work.)
----
----
;Other recent activities
: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).
:B. Help & Tooltips (Tested, modestly implemented, further tweaks & proliferation)
:C. Power Ranks & World History (50%)
:D. Advanced Overlays (In progress.)
:E. Town Layouts, Landmarks, Road Network and Biomes. (Biomes done.)
:F. Equipment Locker (12/2, 50%)
:G. Main Modal Window (4 migrated)
:H. Light/Dark Theming
:I. Right menu additions (states, campaigns).
:K. v2 Data Processing (12/5+)
'''3. Caravan'''
& migration to Typescript. (Vite via JS, then backworking).
:A. Proper Page Declaration & Separation
----
:B. Painting & Placements Import/Export
{{Center|'''SVGs reign supreme!'''}}
:C. Landing Page
----
:D. User Manifest Manager
[[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]]
:E. Final Manifest Additions
----
:F. Thin Proxy Discussion
[[File:MarkerTypes.png|center|PNG icons matched to markers as according to their type classification.|thumb|1200x1200px]]
----
'''4. Manifestor'''
[[File:TownLayouts-v2.png|center|Geometry updates to the Town Layout viewer - making more advanced layouts comprehensible.|thumb|1200x1200px]]
:A. KDB Backend Test
----
:B. MapOrchestration
[[File:SampleTownLayout.png|center|Initial proof of concept for town layout viewer.|thumb|1200x1200px]]
:C. Map's v2 Endpoint
----
:D. Global Action Log
[[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.
[[File:RoadSmithv7.png|center|Road editor progress...Consumes polylines and allows editing thereafter.|thumb|1200x1200px]]
----
'''6. SDK'''
[[File:PaintingToolsPreview.png|frame|center|Painting & Planning tools for the map.]]
: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 03:46, 26 January 2026
I can't stay long, whispered the butterfly, but I'll put a memory in your heart.
Favoriting panels (manifest-based) is now functional! (Relations Journal could use some work.)
Other recent activities
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!
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.
