diff --git a/Zurich-hackathon.md b/Zurich-hackathon.md
index 4643b6d..4f60624 100644
--- a/Zurich-hackathon.md
+++ b/Zurich-hackathon.md
@@ -2,40 +2,44 @@
# 🚧 Exploring the future of design platforms for AEC
-
* **GitAEC** was bootstrapped at the [AEC Hackathon Zurich](https://opensource.construction/events/aec-hackathon-zurich/) in 2024 as [gitaec.com](https://gitaec.com).
## A Forge for AEC
* GitAEC is a design **[forge](https://en.wikipedia.org/wiki/Forge_(software))** for AEC (Architecture, Engineering, Construction).
-* For more details on the project's origin, and the purpose of a forge for AEC, read this LinkedIn article.
+* For more details on the project's origin, and the purpose of a forge for AEC, read this LinkedIn article :
* [A New Kind Of Forge in AEC](https://www.linkedin.com/pulse/new-kind-forge-aec-milovann-yanatchkov-fmyce)
-## Source
+## A Commit History
-* **Source code** on **[gitaec.org](https://gitaec.org)** ([repo](https://gitaec.org/rvba/forgejo))
-* [Better build instructions](https://pad.codeatlas.cc/s/42oGIVy5N#) to come
-* See [Open discussions](https://pad.codeatlas.cc/FehKN63SSSOctFESmnoi5A#)
-* See also **[Fordj](https://fordj.org/)**
+* One of the great feature of **Git** is the `commit` [history](https://about.gitlab.com/blog/2018/06/07/keeping-git-commit-history-clean/), which keeps tracks of every file changes.
+* When working with text-based [native IFC](https://github.com/brunopostle/ifcmerge/blob/main/docs/whitepaper.rst) files, it's possible to view each stage of the modeling process.
+* Here's an example :
+ * [Added model ifc](https://gitaec.org/brunopostle/creative-freedom/src/commit/b28fbd13d182fb78d4cc79dad1b390c92e1750af/model.ifc)
+ * [Added terrain, retaining walls, stairs and deck columns](https://gitaec.org/brunopostle/creative-freedom/src/commit/c367f58c307db840494b58b991115f13b3687679/model.ifc)
+
+* See more [Commit history](https://gitaec.org/brunopostle/creative-freedom/commits/branch/main) and [Revision graph](https://gitaec.org/brunopostle/creative-freedom/graph)
+* Made with [IfcMerge](https://github.com/brunopostle/ifcmerge)
-## Samples
+## Automation
-* IFC viewer sample : [duplex](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/ifc/duplex.ifc)
-* (The viewer is ~5Mb, you may need to reload the page to see the result properly the first time)
* Automation [sample](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/python/extract.py) in Python
* Automation action [sample](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/.forgejo/workflows/update.yaml) and [logs](https://gitaec.com/rvba/hackathon-zurich/actions)
* Automation sample [output](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/output/duplex.ifc.csv)
-Example of a commit history by [Bruno Postle](https://github.com/brunopostle) :
+## Run
+
+ * The simplest way to run GitAEC is to use the [Docker image](https://gitaec.org/rvba/-/packages/container/gitaec/latest).
+ * Learn how-to run and deploy a [container](https://en.wikipedia.org/wiki/Containerization_(computing)) from [docker.com](https://www.docker.com/)
+
+## Source
+
+* **Source code** of GitAEC is available on the `gitaec` branch of the **[main repo](https://gitaec.org/rvba/forgejo/src/branch/gitaec)**.
+* Head to **Forgejo** [documentation](https://forgejo.org/docs/next/contributor/from-source/) for details on how-to build the platform from source.
-* [Added model ifc](https://gitaec.org/brunopostle/creative-freedom/src/commit/b28fbd13d182fb78d4cc79dad1b390c92e1750af/model.ifc)
-* [Added terrain, retaining walls, stairs and deck columns](https://gitaec.org/brunopostle/creative-freedom/src/commit/c367f58c307db840494b58b991115f13b3687679/model.ifc)
-See more [Commit history](https://gitaec.org/brunopostle/creative-freedom/commits/branch/main) and [Revision graph](https://gitaec.org/brunopostle/creative-freedom/graph)
-
-Made with [IfcMerge](https://github.com/brunopostle/ifcmerge)
# AEC Hackathon Zurich