Site's technical specifications
URL parameters
| Parameter | Value(s) | Default value | Description | Control exemple | Portée/context | Status |
|---|---|---|---|---|---|---|
| lang |
|
en | Sets current page's and future navigation's language. If content is not available in selected language, the site will adapt, usually displaying content in available language, but also keeping selected language when navigating. |
 |
Whole site. | |
| style |
|
minimalistic-white | Sets current page's and future navigation's style. |  |
Whole site. |
|
| key | (Context-dependent) | (Context-dependent) | Selects an item. | (Context-dependent) | Pages that can display an item list/selection or a single it. | Mostly implements where applying. |
| page (...) | [Integer numbers] | 1 | Pagination... | Pages that can display an item list/selection. | Pagination ot implemented yet (2023-12-16).) |
Purpose
This site was started around 2010 with no pretension other than being a casual, personal, "web 1.x"-level communication/sharing center, providing some degree of independence from platforms platforms that may isolate contents and users based on "network effect" dependence. It can be seen as a derivative from the 1990s "personal websites", based on more recent tools.
Some constant attestion points are:
- To keep things future proof and relatively easy to maintain;
- To avoid solutions that would require compromises with user data/privacy;
- To keep presentation sober and simple on most pages.
This web site is NOT a professional portfolio/showcase. Most of the projects I worked on implied teams and belonged to the companies I was working for. Others were home-made projects that were not necessarily made to public.
Technology
This web site is based on a PHP/Apache hosting, which was the most common and the cheapest option at creation time. (My main programming language is C#.)
This web site mainly relies on casual home-made backend+frontend framework (PHP/SQL+HTML/CSS/JavaScript), started around 2010 or 2011.
Credits
Many pages have a "Credits" link in their footer. This links to a page with credits to the authors of resources I used. Each credit page can be about a section or a page. I usually do not remove credits even if I do not use some resource anymore, hence there may be credits for resources that don't appear anywhere on the site anymore.
Site map
Site map has a page on it's own: https://thomasconte.net/sitemap/?style=minimalistic-white
No local cookies + Low third party scripts contents
This web site on its own does not use cookies and I usually avoid embedded third party scripts. Even in case you see a logo and a link to some other web sites (i.e.: links to Facebook with logo), they are made of local static HTML tags and do not include any hidden third-party scripts. (Most websites that you visit "daily" or mobile applications will simply not tell what they use and often use hundreds of them.)
At the time I'm updating this paragraph though (2023-01-29), there are a few exceptions:
- Pages with video galleries:
- include YouTube's embedded players (usually after a click), which may involve YouTube's cookie(s).
- Donation pages:
- include a PayPal pixel (which I don't think can be removed without breaking the form) and a form which redirect to PayPal's backend, which may involve PayPal cookie(s).
Thumbnails on menu-type pages vs pages/sections contents
Not all pages/sections in the site have the same "quantity" or "nature" of content. Hence, sometimes the thumnails used on menu-type pages can raise somewhat more expections that the corresponding pages/sections should. I am aware of this. This is because I try to make the menu-type pages look nice, and I don't want to downgrade their looks. I don't see this as a major issue on a low-traffic website, so at the time of writing (2022-03-29) I don't want to change this.