Latest revision as of 01:45, 24 August 2025

What's a prd?

Holder of the skeleton key.

Upgraded to level 20

The Decider

Rebirther

Professional in dozens of languages, master of the cloud, arbiter of HTTPS requests - utterly clueless.

Figure it out mentality.

From signal to server, understand everything!

Socials

Discord - prd1847

Prdandsuch on Reddit

KenshiDBdotWiki@gmail.com

Realpolitik, World Revisions

Mega Archive

8-23

😇 Over the next week the last necessary connections regarding the map-wiki relationship will be established. Thereafter the interface & its interactivity become to the primary focus in that realm. Throughout the month of September a concerted purge of all unnecessary aspects of the wiki & its imported systems will take place. Extensions will whittle down to the necessary inclusions, Gadgets, Widgets, Templates & Modules all passing through a kind of case for usability & merits thereof. Finally, the wiki's frontend will be forced forward in terms of content parity to that of the Fandom wiki - synchronizing their available information and combining with the advancements made (ex... the interactive map system, modding portal(s) & tooling sections). In a brief summary to instill confidence - no hurdle exists which prevents for the full scale development of the wiki other than reaching effort-based milestones. The coveted features live in an assembled state. The task, if given an analogue, is assembling a vehicle having all the required parts ready for fastening & welding together. Any doubts at the viability of this dissipated some months ago.

All hail the march of progress
Whichever way you like
You're gonna carry that weight
Do it with a smile

Cool Image Tools

@@ Line 1: / Line 1: @@
-Git:
+<big>{{Center|What's a prd?}}</big>
-<br>
+<small>{{Center|Holder of the skeleton key.}}</small>
-===== Studybuddy =====
+;Upgraded to level <big>'''20'''</big>
-*HTTP
+[https://www.youtube.com/watch?v=qf-_bRjZ38U The Decider]
-*HTML
-*CSS
+[https://www.youtube.com/watch?v=E4w4pzj9wE8 Rebirther]
-:*LESS
-:*Mustache
+[https://www.youtube.com/watch?v=rXPpkzdS-q4 Professional in dozens of languages, master of the cloud, arbiter of HTTPS requests - utterly clueless.]
-*JS
+----
-:*Node - See: https://nuxt.com/docs/api/nuxt-config#nitro
+Figure it out mentality.
-:*Vue - See: https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue
+*https://en.wikipedia.org/wiki/We_choose_to_go_to_the_Moon
-:*'''Nuxt''' - Test environment being built.
+*https://en.wikipedia.org/wiki/File:President_Kennedy%27s_Speech_at_Rice_University.ogv#file
-::*Leaflet - Foundation of the map but as per the coordinate transformation the library is mostly a guideline, not a rule.
+From signal to server, understand '''everything'''!
-::*jQuery - Too prevalent not to be familiar with.
+----
-*PHP- (We hate Laravel)
+:Socials
-:*Parsoid
+::Discord - prd1847
-*Nginx - See maintenance & downtime plans.
+::Prdandsuch on [https://www.reddit.com/user/prdandsuch/ Reddit]
-:*SSL
+::KenshiDBdotWiki@gmail.com
-*Kubernetes
+----
-:*Blue/Green
+[[Project:Realpolitik|Realpolitik, World Revisions]]
-*MySQL
+----
-:*MariaDB
+[https://mega.nz/folder/2DRFAYzJ#sF1O8a2VhRwM3J0ddaNYug Mega Archive]
-*Cargo
+----
-*MW-core
+;8-23
-*Unix
+{{emoji|1F607}}
-*Bash
+Over the next week the last necessary connections regarding the map-wiki relationship will be established. Thereafter the interface & its interactivity become to the primary focus in that realm. Throughout the month of September a concerted purge of all unnecessary aspects of the wiki & its imported systems will take place. Extensions will whittle down to the necessary inclusions, Gadgets, Widgets, Templates & Modules all passing through a kind of case for usability & merits thereof. Finally, the wiki's frontend will be forced forward in terms of content parity to that of the Fandom wiki - synchronizing their available information and combining with the advancements made (ex... the interactive map system, modding portal(s) & tooling sections). In a brief summary to instill confidence - no hurdle exists which prevents for the full scale development of the wiki other than reaching effort-based milestones. The coveted features live in an assembled state. The task, if given an analogue, is assembling a vehicle having all the required parts ready for fastening & welding together. Any doubts at the viability of this dissipated some months ago.
-<br>
+----
-:*Q: Why a high level framework? Why not Laravel?
+;[https://www.youtube.com/watch?v=C58C8U_3WPM All hail the march of progress]
-::*Good questions, here's the answers:
+;[https://www.youtube.com/watch?v=ewvRS3NwIlQ Whichever way you like]
-:::*# A similar line of thinking as to "Why MediaWiki 1.43?". It serves the use-case and provides me access to a mountain-top view. I'm more than willing to traverse that mountain and don't want to ignore any aspect of the stack high or low. Also, I want to write in ''pure'' PHP so there's as little abstraction as possible when browsing the ocean of the MW-core and its extensions. Knowing when Laravel was utilized is good to know - it's not any more necessary than Nuxt to actually use. That said. I'm not overtly opposed to Laravel's use. I've been staring at PHP for weeks and catch snippets of JS as I go along. This is to forcefully expose myself to a JS heavy environment and '''adapt'''.
+;[https://www.youtube.com/watch?v=S6cXNH6AVg0 You're gonna carry that weight]
-:::*# Because I'm not actually restricting myself to the high level. As much as I want to see heavily bundled frameworks I'm spending just as much time perusing documentation on TLS, TCP/IP, HTTPS, DNS, SSL, nginx, etc. My intent doesn't stop at the wiki or the map. The path to total sysadmin is almost invariably going to be slow and filled with struggle. Wrestling with Nuxt and MediaWiki is just as important as taming nginx and cloud services. Everything matters.
+;[https://www.youtube.com/watch?v=0Nz8YrCC9X8 Do it with a smile]
-<br>
+----
-*Also...
+=Cool Image Tools=
-::*No. I will not be using Django (Python) or Rails (Ruby). Considering the ubiquitous presence of PHP on MediaWiki and the lack of integrating tooling for the aforementioned I'm left with too much added work to try and get those spun up. Time is better spent developing skills which can directly translate to the wiki. Besides, a javascript heavy approach to the map gives me ample exposure to the other big player on the wiki (especially for gadgets).  This is not about making '''the greatest map to ever exist built in the most ideal way'''. Rather, it needs to meet various functional uses and refine around those. Obviously the existing map is a rudimentary mock-up and embodies only one test of one feature (coordinate conversion).
+*https://www.imgonline.com.ua/eng/cut-photo-into-pieces.php
-::*The topic of Leaflet has already somewhat been settled. The library is effortless to work with and boils down to optimization strategies. Load times have been as low as ~200ms for the global map wrapper via the Nuxt module.
+*https://squoosh.app/editor
-::*Vue's lovely interface options are the big task at hand since they're the primary driver of the interactivity. Since in reality the map itself is a static element with rigid elements requiring no manipulation beyond load routines.
+----
-::*So you might ask - what of the mod loading capabilities? Simple answer: they won't be in the first iteration of the map. Before adding custom data I'd like to be sure all other forms of basic interactivity work fine.
-:::*Nuxt is being used to produce the first iteration of the map. It might be used in the second or even third. By then I may change course to compare options, strip down the model further or embrace Nuxt fully. Who can say?
+[[Category:Pages with broken file links]]