Transparency
Changelog
What changed, when, and what is still open.
A public log of site changes. The point is not decoration: any technical visitor can see the site is maintained, and that corrections are published rather than hidden.
November 2026 — Full audit fixes (v3.3.0)
- “Related projects” links: they were built from a wrong relative path and led to a 404 on all 34 project pages. The path is fixed, and every project now has an English description instead of the Arabic one showing on English pages.
- Headline numbers: the real values are now in the HTML itself, so no zeros appear with “reduce motion” or without JavaScript.
- Canonical host: every canonical and hreflang tag, the sitemap, the feeds and security.txt now point to the host that actually serves this version.
- 404 page: root-absolute URLs, so it keeps its styling on any path, plus an English paragraph.
- Header: sticky again while scrolling, and on a single row.
- Design: the missing
--cardand--linetokens are defined, the type scale is down to nine steps with a 13px minimum, and the focus ring has enough contrast in the light theme. - Search and form: the search dialog has a close button, traps focus and returns it; the contact form shows each error next to its field and moves focus there.
- Security: no inline scripts, so
'unsafe-inline'is gone fromscript-src. The e-mail address is no longer written in the form tag. - CV: the PDF and Word files were regenerated with current figures, metadata and clickable links, and printing the Arabic page is fixed.
- Navigation and taxonomy: one header on every page (sticky, with a phone menu, search and language switch) and one project taxonomy on the home page and the register. On phones, long card lists start shortened with a “show all” button.
- Documented late: the v3.2 additions (site search, reading progress, related projects) were not logged here when they shipped. The floating language button from that batch was removed because it duplicated the header language link.
October 2026 — Text contrast, responsiveness & SEO (v3.1.1)
- Contrast: every text colour was rebuilt on semantic tokens (
--fg-strong/body/muted/faint,--on-dark-*) and all failing pairs in both light and dark themes were fixed — from 490 unique failures in the first audit to zero in an automated pass over 84 pages × 3 viewports × 2 themes, measured against WCAG AA (4.5:1 body text, 3:1 large text and UI). - Root cause: pale greys (slate-300/400) were used as text on white surfaces, and dark-theme rules were written as
html[data-theme="dark"] .subpage xwhile thesubpageclass sits on the<html>element itself — so they never applied. Both patterns are fixed. - Form fields: field backgrounds and borders are now tokens (
--field-bg/--field-border) with explicit text colours, so no input is unreadable. - Responsive: grids use
minmax(min(Npx,100%),1fr)so nothing overflows at 320px, tables scroll horizontally on mobile, buttons wrap instead of clipping, tap targets are ≥24px, and spacing is tuned down to 320px — no horizontal scrolling on any page. - SEO: reciprocal
hreflangcorrected (English pages pointed at the Arabic URLs in all three tags), 42 heading-order skips removed (h2→h4, h1→h3),og:image:alt,og:locale:alternate, descriptions andWebPageschema added where missing,imageadded to article schema, title/description lengths normalised, andsitemap.xmlregenerated (80 URLs) with correct hreflang mappings. - Standalone pages:
cv.htmlanden/cv.htmldo not loadmain.css; undefined tokens, a missing brace that trapped every following rule inside one media query, and browser-default link colours were all fixed there.
October 2026 — full review (v3.1.0)
- Fixed: Python template code visible on 16 pages was removed, and English page titles were moved fully into English.
- Created: the Sodfa Chat pages in Arabic and English — closing the last broken internal link on the site.
- Security: a real PGP key (Ed25519) was issued and its fingerprint published in
security.txtand on the key page, after the published file had been a placeholder. - Performance & privacy: every external call was removed — the fonts (Cairo and Inter) are self-hosted, and the site now makes no third-party request.
- Branding: five genuinely distinct OG cards (previously five identical copies) in Arabic and English.
- Content: 17 project pages rewritten with uniform sections (Problem, Technical Challenges & Design Decisions, Testing Methodology, Outcome & Impact) plus SVG architecture diagrams for five systems.
- New pages: Terms of Use, How I Work with FAQ (and FAQPage schema), PGP key, Evidence, Results, Services & packages, Acknowledgements, Lab notes (5 articles), Changelog.
- Numbers: numeric claims on the home page and CV were aligned with the actual inventory (17 projects, 4 published repositories, practice since 2018, 7 live tools).
- E-mail: the obfuscation strategy was unified: every address shown in body text is obfuscated via
data-email-*, with the real address appearing only insecurity.txtwhere it must. - Technical SEO: every page carries canonical, hreflang (ar/en/x-default), robots, manifest, Open Graph, Twitter Card and JSON-LD, with a 58-URL sitemap including language alternates.
- Declared corrections: references to non-existent pages were removed from
robots.txt, the missingprofile-800.jpgreference was fixed, and a stray CSS parenthesis that cancelled a visual transition was repaired. - Reputation:
humans.txtadded, MIT licences published for the four repositories, and a researcher acknowledgements page created. - Experience: a dismissible privacy notice, a PWA update banner, a unified back-to-top control on every page, project filters with a live result count, internal search, a reading progress bar and related-project suggestions.
July 2026 — foundation (v3.0.0)
- Visual identity rebuilt: colour and type system, dark mode, high contrast.
- Service worker rewritten: shell precache, distinct strategies for HTML and assets, and no activation of a new build before the user agrees.
- Dual CVs: a print-ready visual version and a clean ATS version.
Not done yet — declared
- Production security headers: the
.htaccessfile is ready in the repository (CSP, HSTS, Permissions-Policy…) but needs to be deployed and verified on the server. - Hosting migration: the current free host injects a JavaScript challenge and limits performance. Migration to a provider supporting HTTP/3, compression and security headers is recommended.
- DNS records: the required records file (SPF, DMARC, AAAA) is ready and waits to be added in the domain panel.
- Hosting your own tools: the seven tools run on a third-party provider; moving them to your own subdomain increases continuity and control.