Text version of the portfolio of Rémi Moreau, a BTS SIO SISR student (French two-year degree in IT infrastructure and networks). Open in RémiOS, the interactive version → · Version française

RémiOS portfolio — online presence

Type
Personal project
Date
September 2026 – October 2026
Status
online, evolving
Technologies
JavaScript, HTML, CSS, Vite, Markdown, GitHub Pages, GitHub Actions, DNS, GoatCounter, GitHub Copilot, Google Apps Script, Docker, Nginx, Claude Code
Skills
B1.3 Develop the organisation’s online presence; B1.4 Work in project mode; B1.5 Make an IT service available to users; B1.6 Organise one’s professional development

Context

The E5 exam of the BTS SIO requires a portfolio presenting my projects and the skills of the framework. Rather than a ready-made template, I wanted a website that reflects the SISR option: RémiOS imitates a Linux system booting (GRUB screen, systemd log), then shows a whiptail-style menu, with a hidden terminal.

It is also my online presence as a candidate: the jury, recruiters and my LinkedIn contacts reach it through my own domain name, remim.me.

Objectives

Implementation

The website. It is static and built with Vite. A plugin I wrote converts the Markdown project pages into HTML at build time, and checks each one (mandatory fields, existing skills, images present): a badly filled page blocks publication. The browser only receives HTML, CSS and a little JavaScript, with no external library and no font loaded from a third party.

Two languages, two themes. The website exists in French and in English (remim.me/en), from the same Markdown files: each translated page has its English version next to the French one, and a text not yet translated is still shown in French, flagged as such. The English content is only downloaded by visitors of the English version. A dark mode follows the system setting, or the visitor's choice, stored in their browser.

Hosting and domain name.

Security and the GDPR. A strict content security policy (CSP) prevents any external script from running. The website sets no cookies, and its legal notice describes the publisher, the host and the processing of data (contact form, audience measurement).

Search engine optimisation. A carefully written title and description, schema.org structured data (a "person" record with my position, my school, my GitHub and LinkedIn links), a sitemap (sitemap.xml), a robots.txt that keeps my CV away from search engines (it contains my phone number), a preview image for LinkedIn shares, and an icon in the formats Google asks for.

Audience measurement. GoatCounter, a cookie-free open-source tool, counts each page viewed. To keep the "no external script" rule, I wrote the page-view sending myself instead of loading the official script. Nothing is counted for bots, nor for browsers that ask not to be tracked.

The technology watch. Every Monday, a GitHub Actions job reads the RSS feeds of 33 sources. GitHub Copilot then picks, for each of my three topics (cybersecurity in industrial SMEs, virtualisation, e-invoicing), the most useful articles, summarises them and tags them. The news appears in the "Technology watch" section, one tab per topic.

The watch by e-mail. New news items also reach me by e-mail, numbered. I reply with my opinion on the ones that caught my attention ("1, 3: what I take away…"); the AI turns it into a synthesis, without adding anything, and sends it back for me to proofread. I reply "ok" and it is published, or I ask for a correction. The website has no server: a small Google Apps Script in my Gmail account relays the e-mails to GitHub Actions, which runs the AI and saves the synthesis. Nothing is published without my approval, and only my own messages are read.

The dashboard (dashboard.remim.me). A second static website, in its own repository, to run the portfolio without opening a code editor:

Portfolio architecture diagram: visitors open remim.me over HTTPS; the domain name, managed at Namecheap, leads to GitHub Pages, which serves the portfolio and the dashboard.remim.me dashboard. Each page viewed is counted by GoatCounter. I write in VS Code or from the dashboard, which saves to the repository through the GitHub API. Each push triggers GitHub Actions, which tests then publishes the site. Every Monday, the watch reads 33 RSS feeds and has GitHub Copilot summarise the articles.
Portfolio architecture: publication, automated watch and dashboard (diagram in French)

Built with Claude Code. My role: defining the need, making the choices and testing.

Source code (MIT licence): the website and the dashboard.

Screenshots

RémiOS main menu: a grey whiptail-style box on a blue background, with the logo, my details and the numbered sections
Main menu, after the Linux-style boot
Technology watch section: three topic tabs, and in the Cybersecurity topic, the "Latest news" and "My syntheses" tabs, then the summarised news items with their tags
Technology watch: one tab per topic, news summarised every Monday
Quick view for the jury: a plain page on a white background, with the table of contents
Quick jury view: plain, printable, no animation
Hidden terminal: the ls and cat commands show the site's files, including the folder of each watch topic
Hidden terminal: the site browsed like a file system
Dashboard overview: state of the three watch topics with the age of the latest synthesis, state of publication and collection shown like a boot log, shortcuts, and a box with the site's visits
The dashboard.remim.me dashboard: the overview
Dashboard Syntheses view: topic bar, list of published syntheses, editor, and the topic's news items to tick to cite them as sources
Dashboard: writing a synthesis and citing its sources

Results and testing

The website has been online since September 2026, and its traffic has been measured since 9 October 2026.

Difficulties encountered

No server on GitHub Pages. The dashboard had to write to the repository and call an AI, without exposing any secret. Solution: the GitHub API called from the browser, with a personal token with minimal permissions, and the AI run by GitHub Actions, where its secret stays.

GitHub Pages' cache. Right after an update, a browser could show the new page with the old stylesheet. I added a version number to each file, and a test checks that none is forgotten.

Measuring the audience without weakening security. GoatCounter's official script would have required allowing an external script. So I rewrote the page-view sending, and a test checks that no visit is counted during the tests themselves.

The icon missing in Google. The site only had an SVG icon, whereas Google asks for a square image of 48 px or a multiple of 48: I added a favicon.ico and a 192 px image.

Concurrent writes. The dashboard and the Monday collection write to the same repository. Each write checks the file's version, so as never to overwrite a change made elsewhere, and the Monday job updates itself before pushing its own.

Possible improvements

Skills applied