It “lives” in a Git repository, is statically generated (well, at present really just statically created), and online at https://dirageosystems.ch since December 2021.
In 2023 we contracted dreamis.ch to redesign the website. It now uses Bootstrap (no longer W3CSS) and the custom CSS is generated and minified from scss/custom.scss (keep these files in sync, either with a scss processor or manually).
In 2025 we made a big-ish update, and moved from a single page to multiple pages. The website is still static, still uses bootstrap and now added jekyll (GitHub Pages Default) static site generator
Please keep this simple and static.
Presently hosted at GitHub Pages, straight from the GitHub repository. Things to consider:
- GitHub Pages only works for a public repository
- GitHub Pages publishes the docs/ directory on the main branch
- need empty file docs/.nojekyll to disable Jekyll
- turned on “Enforce HTTPS”: HTTP requests get a 301 (permanent redirect) to HTTPS; good
- configured the custom subdomain
www.dirageosystems.chand the custom apex domaindirageosystems.ch; a DNS CNAME record pointswww.dirageosystems.chtodirageosystems.github.ioand several DNS A records pointdirageosystems.github.ioto the GitHub servers - read the GitHub Pages docs about custom domains
The page is automatically built upon a push to github. If you want to have local previews, create a jekyll docker container by using the included docker-compose.yml. Go to the root of this repository and run:
docker-compose up
The site will be available under locallhost:4000 approximatley 4sek after saving your edits in your editor..
-
Git: Clone the repository (once only)
-
Edit the web site.
-
Test locally: open
locallhost:4000, navigate to your changes, test behavior. You may use the browser's Debugger tools (F12) to simulate small screens and look into the console for errors and warnings. -
Git: review and commit your changes. Use a short but descriptive commit message.
-
Git: push your commit(s) to GitHub; it will automatically publish the changes within a few minutes.
-
Test the published web site: navigate to https://www.dirageosystems.ch and review your changes with your Desktop browser and your mobile browser.
In der Schweiz gibt es seit 2012 eine Impressumspflicht (revidiertes Gesetz über den unlauteren Wettbewerb UWG). In Deutschland gibt es das als Anbieterkennzeichnung schon länger. Es geht darum, dass der Urheber der Seiten zweifelsfrei identifiziert und kontaktiert werden kann. Also: Firmenname (wie im Handelsregister eingetragen), funktionierende Mail und Postadresse, optional Telefonnummer und Firmennummer. Dies entweder auf jeder Seite oder auf jeder Seite einen Link zu einer Impressum-Seite.
Achtung: für eine Geschäftstätigkeit in Deutschland/EU sind weiter erforderlich:
- Name und Vorname einer vertretungsberechtigten Person
- Telefonnummer
- Umsatzsteuer- oder Wirtschaftssteuer-Identifikationsnummer (wenn vorhanden)
- Handels-, Vereins-, Partnerschafts- oder Genossenschaftsregister mit Registernummer (falls vorhanden)
Quelle: https://www.cyon.ch/blog/Impressum-Websites/
Weiter ist eine Datenschutz-Erklärung zwingend. Sobald die Seite von EU-Bürgern verwendet wird, werden diese sich auf die DSGVO berufen, wir müssen also auch hinsichtlich DSGVO eine vollständige und korrekte Datenschutz-Erklärung erstellen und auf jeder Seite (im Footer) verlinken. Bei Hosting auf GitHub Pages (oder wo auch immer) ist sicher mindestens auf deren Datenschutzerklärung zu verweisen.
Siehe:
- https://www.cyon.ch/blog/anleitung-datenschutzerklaerung
- https://www.datenschutzstelle.li/index.php/?cID=316
- https://docs.github.com/en/github/site-policy/github-privacy-statement
- https://docs.github.com/en/github/site-policy/global-privacy-practices
We do not collect any user data at the moment at all (but GitHub might).
We don't even use cookies.
The language selection happens via a lang flag which is updated in all links through a js file.
Should we decide for site usage statistics, we could use good old StatCounter (I'm using this for the IEG site) or Google Analytics as in the snipped below. But beware that we have to update our privacy policy accordingly!
<!-- Google Analytics: change UA-XXXXX-Y to be your site's ID. -->
<script>
window.ga = function () { ga.q.push(arguments) }; ga.q = []; ga.l = +new Date;
ga('create', 'UA-XXXXX-Y', 'auto'); ga('set', 'anonymizeIp', true);
ga('set', 'transport', 'beacon'); ga('send', 'pageview')
</script>
<script src="https://www.google-analytics.com/analytics.js" async></script>- Google Search Console may report a duplicate that is has
no canonical link; this asks for a
<link rel="canonoical" ...>element; see also Wikipedia article
- robots.txt – config site crawling, see https://www.robotstxt.org
- browserconfig.xml – settings for IE11 and Edge browsers, see https://msdn.microsoft.com/en-us/library/ie/dn455106.aspx
- site.webmanifest – the Web App Manifest, see below
- 404.html – should be returned on HTTP/404 errors (works with GitHub Pages)
- CNAME – required by GitHub Pages
The web app manifest belongs to the realm of progressive web
apps (PWAs) and allows a web site to be installed on a mobile
device's home screen (without an app store). It is a JSON file
referenced from HTML with <link rel="manifest" href="FILE">.
Mozilla
has the details.
The og:foo meta tags are for the Open Graph Protocol,
a Facebook thingy that helps control what Facebook (and
others) display when their users share this page.
Details on https://ogp.me/
-
https://html5boilerplate.com and
https://github.com/h5bp/html5-boilerplate
consulted for a kick start and modern web compliance -
https://www.w3schools.com/w3css/default.asp
The CSS framework used. It is disputed, but simple to use, lightweight, and just works. -
https://looka.com
a useful online logo generator; could download an entire brand kit, but that is no longer free -
https://pages.github.com/
free website hosting straight from a GitHub repo.