More actions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
<br> | <br> | ||
===== Studybuddy ===== | ===== Studybuddy ===== | ||
*HTTP | |||
*HTML | *HTML | ||
*CSS | *CSS | ||
| Line 7: | Line 8: | ||
:*Mustache | :*Mustache | ||
*JS | *JS | ||
:*Node | :*Node - Relevant and flexible. Hard not to base around this. | ||
:* | :*Vue - Practical answer to clean interface. | ||
:*Vue | :*Nuxt - Somewhat naturally coupled with Vue & Node. Understandable and more approachable than Next & React. | ||
:*jQuery | :*Express - Decent option for managing server-side while the rest are dealing with the client-side. Depends on tests. | ||
:*Leaflet | ::*jQuery - Too prevalent not to be familiar with. | ||
*PHP | ::*Leaflet - Foundation of the map but as per the coordinate transformation the library is mostly a guideline, not a rule. | ||
*PHP- (We hate Laravel) | |||
:*Parsoid | :*Parsoid | ||
*Nginx | *Nginx - See maintenance & downtime plans. | ||
:*SSL | :*SSL | ||
*Kubernetes | *Kubernetes | ||
:*Blue/Green | :*Blue/Green | ||
*MySQL | *MySQL | ||
:*MariaDB | :*MariaDB | ||
| Line 24: | Line 26: | ||
*Unix | *Unix | ||
*Bash | *Bash | ||
<br> | |||
**No. I will not be using Django (Python) or Rails (Ruby). When considering for ubiquitous presence of PHP on MediaWiki and the lack of integrating tooling I'm left with too much added work to try and get those spun up. A javascript heavy approach to the map gives me ample exposure to the other big player on the wiki. 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). | |||
Revision as of 19:43, 27 February 2025
Git:
Studybuddy
- HTTP
- HTML
- CSS
- LESS
- Mustache
- JS
- Node - Relevant and flexible. Hard not to base around this.
- Vue - Practical answer to clean interface.
- Nuxt - Somewhat naturally coupled with Vue & Node. Understandable and more approachable than Next & React.
- Express - Decent option for managing server-side while the rest are dealing with the client-side. Depends on tests.
- jQuery - Too prevalent not to be familiar with.
- Leaflet - Foundation of the map but as per the coordinate transformation the library is mostly a guideline, not a rule.
- PHP- (We hate Laravel)
- Parsoid
- Nginx - See maintenance & downtime plans.
- SSL
- Kubernetes
- Blue/Green
- MySQL
- MariaDB
- Cargo
- MW-core
- Unix
- Bash
- No. I will not be using Django (Python) or Rails (Ruby). When considering for ubiquitous presence of PHP on MediaWiki and the lack of integrating tooling I'm left with too much added work to try and get those spun up. A javascript heavy approach to the map gives me ample exposure to the other big player on the wiki. 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).