Internal Development🔖

Design Reference (master file is the Adobe XD file): https://scene.zeplin.io/project/61bf224529c45d15624e7f28

Prototype🔖

Using React, Bootstrap, Dnd-Kit, Chart.js, Jest-Dom

First, solely by Phil (early 2022): https://staging.mensch.link

Second, by Phil and Team Saboja (delivered 06.10.2022): https://app.mensch.link

Question Editor at https://fragenarango.mensch.link/

DB: https://arango.ftt.gmbh:8529

All Code gathered at https://code.ftt.gmbh/ftt

Overview from Zulip🔖

Assets and graphics🔖

List, constantly being updated by the UX team, headed by Dominik Fusek and UX/UI team Kenya: https://docs.google.com/spreadsheets/d/1Pdw_GjXjtl0W2XVgz9Vyjeo2pz11JKH8fC-MFZpooIg/edit?usp=sharing

Here we have to clarify the collaboration process.

Current Dramaturgy🔖

https://chat.ftt.gmbh/user_uploads/2/b1/4EGR_d6DxoMYsVE0zUT71bjk/220407_MenschLink_Dramaturgie.pdf

Link to the MenschLink presentation:🔖

https://drive.google.com/file/d/1c24hm-Y8KKWO96BG-i1NHY4SEB_t8ejn

Here is the Zeplin channel with access data:🔖

https://app.zeplin.io/project/61bf224529c45d15624e7f28/dashboard

ftt@ftt.gmbh fEBSTWx%@^XR8P4

We will then use low poly for now, because that is speedy in design and wide adoption is available.

Mental Model (work in progress)🔖

https://docs.google.com/spreadsheets/d/1Tj3tnGxE6Ql9RcG11nPmCUQ0CHdYiqU0khkBjr7lJPo/edit?usp=sharing

Competences: A incredible catalog from the german government and a international organization🔖

ISCO 08 - Competence/job profiles & co https://chat.ftt.gmbh/#narrow/stream/11-MenschLink/topic/Kollaboration.20Fragestellungen/near/693

Milestones: https://view.monday.com/1988418997-2a57e40c5e4aaaf365127e4398d6be3d?r=use1

Graphics🔖

Assets by Jannik: https://drive.google.com/drive/folders/16CNEhVAUe8Sy-Is3dTBQ7wm8KX_3FKhE?usp=sharing

Ultimate Low Poly Pack for Blender🔖

https://drive.google.com/drive/folders/1PciLcr8viuXg9-__zg_jogMAUzauSjJG

We also have a Unity version. Ask if needed.

Flat icons transport as transition phase🔖

https://chat.ftt.gmbh/user_uploads/2/6a/z23cVjph58Yg1HN4V5RnfX62/iStock-512452221.eps

Graphics for climate zones (Jannik)🔖

ID7: location.climate Q7: Which climate do you prefer? A1: cold zone A2: temperate A3: Mediterranean A4: subtropical A5: tropical

See: https://chat.ftt.gmbh/#narrow/stream/11-MenschLink/topic/Kollaboration.20Fragestellungen/near/2439

Graphics for terrain types🔖

High mountains Low mountain range Hill country Moderate hilly country Lowland Sea

See: https://chat.ftt.gmbh/#narrow/stream/17-web.2Bdesign/topic/landing.20pages/near/2470

Old Editable Taxonomy (unavailable): https://taxo.mensch.link

Technological Considerations🔖

Frontend Components🔖

Drag and drop:

• https://bevacqua.github.io/dragula/

Slider:

• https://refreshless.com/nouislider/
• https://mui.com/material-ui/react-slider/

Frontend Frameworks🔖

We should look into optimizing our current stack, as I have also heard reports of the webapp loading slowly, especially when there are internet connectivity issues. Bootstrap has quite a few issues, including bad performance/high traffic usage, so I wonder why you chose it when there are many alternatives - Tailwind seems to be highly-praised as a direct Bootstrap alternative. As for React, a friend recommended to use https://preactjs.com and as mentioned above, nextjs, or at least react-signals for better component communication. I also just learned about an appraised concept called CSS-in-JS, and right away found a framework which also supports React: https://stitches.dev

Scalability🔖

We have to start considering which tech stack to use once we want to scale properly. Erlang/Elixir (use the latter) are built specifically for scaling. I remember starting a project in Elixir+Phoenix a while back and AFAIR it was pleasant. Haskell (A friend worked at the popular Web Framework IHP there), Go and Rust are also good options to consider, as well as Kotlin due to its flexibility (JVM/JS/Native) which could allow us to write a native Android app together with the web app.

As for the frontend, we should investigate WebAssembly, especially when performance becomes an issue, it has reached production-readiness years ago. Rust might be able to handle both backend and frontend and is known for its performance: https://www.caci.co.uk/insights/opinions/rust-websassembly-is-it-ready/

Programming Languages Genealogy🔖

Wikipedia has a good overview to find out which languages stem from where, which we could turn into a diagram https://www.wikiwand.com/en/Generational_list_of_programming_languages#/C_based

Somebody already made a chart about that, unfortunately a bit dated though: https://github.com/stereobooster/programming-languages-genealogical-tree

But he has also collected some links about it.