At a university you may be working on the frontend of our knowledge. Your work might be used for academic publication (scientific journals), you might be working with humans requiring special care on data storage (next to human ethics approval), or working on a system that requires knowledge security (e.g. powerplant, nuclear plants etc). Hence, before you make a public website and start your project on a (random) version control system, sit with your supervisor to talk about:
which version control system is being used (GitLab, GitHub, OneDrive, ..)
where to store the data, for how long, who owns the data once you are finished
who has access to the data and source files
if there are any restrictions on data publication (e.g. confidentiality related to publishing work in a scientific journal, or knowledge security, or human ethics)
if, when, and where to make the webversion available
whether active advertisement is allowed (or even encouraged) once the project is finished
whether your work can be included in our gallery
Note that even without publishing a website online, the workflow can be used locally and has many merits (e.g. the interactive version can be shared using an USB, markdown is much easier to edit than LaTeX or Typst).