|
|
| (7 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| == Map ==
| | [[Main Page|Return to the main page]] |
| *'''2/27''' - Setting up Nuxt environment.
| | |
| :*Expected as:
| | [[Project:Index|Return to the project index]] |
| ::*SSG <- rather, ssr:false
| |
| ::*SPA
| |
| ::*Leaflet (Module)
| |
| :*Initial thoughts are the tooling is great but CLI interactions are the real highlight.
| |
| :*Nuxt's on-install DX offers quite a lot of flexibility without creating a monolith upon initial setup.
| |
| :*Unlikely to need anything from SSR and its qualities. Leaflet is best handled client-side.
| |
| ::*However, the plan for modlist tokens means there will need to be authentication (silent) to communicate with user created configurations.
| |
| ::*Nitro's exact role is projected to be limited or on-use, if used. Need to dig here -> ''see the protected API calls and background mini-sync.''
| |
| *'''2/28''' - Vue? Nuxt?
| |
| :*What is actually true is "ssr:false", at least as far as Leaflet is concerned.
| |
| ::*Since it operates (exclusively) in the client realm the biggest questions are:
| |
| :::*Prerendered with simplified routes? vs --
| |
| :::*Selective prerendering.
| |
| :::*Landing animation? Haven't done hydration tests.
| |
| :::*Auth token from MW? Nitro, hello?
| |
| :*Leaflet just wants to work. No issues (yet).
| |
| :*Haven't gotten around to caching strategies, mostly focused on click interactions and the map frame at the moment.
| |
| ::Late night: Spent some time monitoring Nitro operation. Insightful!
| |
| ::It is '''very''' clear Nuxt is in active development and sometimes uses experimental features (going as far as recommending them).
| |
| :::This...is not ideal. Even so, the framework is fun and I'm still rather busy exploring JS itself.
| |
| :::Less about "mastering Nuxt" and taming the tiger. I just needed a comfortable JS-like environment to see what the ceiling looked like. It's alright.
| |
| <br>
| |
| *:Q: Why a high level framework? Why not Laravel?
| |
| :*Good questions, here's the answers:
| |
| ::*# 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. | |
| ::*# Because I'm not 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.
| |
