What this page clarifies
Toola is not presented as a generic website builder or a static picture. It is a decision-support environment for complex research-infrastructure energy systems. The public website should explain the method, data flows, ontology and exploitation pathway, while the live app remains hosted separately.
Ontology and module map
Graph based on the current Toola architecture discussion: frontend modules, client-side calculations, static asset data, location/climate API, Lambda/DynamoDB access gate, external datasets and semantic concepts such as OEO, PROV-O, DCAT and QUDT.
Conclusions incorporated into this website
Public landing page
fulka.eu should act as the understandable public entry point: what Toola is, what problem it solves, and where the live app is available.
Separate application hosting
The Toola application remains separately hosted and linked from the website. The public website does not need to host the computational core itself.
Usability beyond GitHub
GitHub is useful for code and archiving, but not friendly enough as the main environment for general public scientists. The website should provide the explanatory layer.
Traceability and exploitation
The page highlights data provenance, methodology, example outputs, documentation, and the role of GitHub/Zenodo style archiving after the project.
Website analytics added
Privacy-friendly Plausible-ready analytics are now embedded across the site. The setup tracks page views once the domain is configured in Plausible and additionally captures clicks on email, phone, LinkedIn, PDF downloads, service details and the live Toola app link.