User:Prd: Difference between revisions
More actions
No edit summary |
|||
| Line 35: | Line 35: | ||
Favoriting panels (manifest-based) is now functional! (Relations Journal could use some work.) | Favoriting panels (manifest-based) is now functional! (Relations Journal could use some work.) | ||
=1/26= | |||
[https://www.youtube.com/watch?v=GAVJ3FJra7o delete fucking everything!] | |||
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. | |||
---- | |||
;Other recent activities | |||
---- | |||
Let me paint a general picture for you - | Let me paint a general picture for you - | ||
#'''February''' - Methodical update, enhancement & rework (if necessary) of the existing features. | #'''February''' - Methodical update, enhancement & rework (if necessary) of the existing features. | ||
| Line 41: | Line 48: | ||
#'''May''' - The map is ready for Cloudflare deployment (full proxy & caching) - further design considerations go into the testing realm. | #'''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 | :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.) | :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''' | :'''Extensions Mix''' | ||
::''Caravan'' | ::''Caravan'' | ||
| Line 51: | Line 57: | ||
:::Delivers specific content from a wiki page to the map for embedded display (within info & content panels). | :::Delivers specific content from a wiki page to the map for embedded display (within info & content panels). | ||
::''Mappy'' (Paused) | ::''Mappy'' (Paused) | ||
---- | |||
;Exploring... | ;Exploring... | ||
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.
map.kenshi.wiki - Interactive Map
kenshidb.wiki - KenshiDB, Asset Repository
jobboard.kenshi.wiki - Job Runner Dashboard
1/6
Account creation closed. (Temporarily, wiki refresh is on-schedule for April.)
1/19
1/20
1/24
1/25
Favoriting panels (manifest-based) is now functional! (Relations Journal could use some work.)
1/26
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).
- Mappy (Paused)
- Caravan
- Exploring...
& migration to Typescript. (Vite via JS, then backworking).








