TECHNICAL WALKTHROUGH · LENOEZECHIEL.COM
Inside the Drupal Build
This page documents one real project: the portfolio you are currently viewing. It explains how Drupal is used to organise multidisciplinary content, manage English and French, connect related work, present several media formats and maintain a coherent experience as the website grows.
Project identity
Content currently published
- case studies
- 7
- graphic-design projects
- 24
- video productions
- 11
- selected photographs
- 19
- public documents
- 20
Translations are not counted as separate projects.
Why Drupal
The portfolio contains long-form case studies, graphic-design projects, photographs, videos, professional experience, recognition, certificates and downloadable documents. Treating each item as an isolated page would have made updates slow and inconsistent. Drupal was chosen to give this material a clear structure: the same information can support a card, a detail page, a filter, a search result or a link to related work. The CMS is therefore not only the tool that displays the website; it supports the portfolio’s editorial organisation.
Content architecture
The website organises information into coherent groups rather than fully independent pages. The main visible content families are: case studies; graphic-design projects; photography selections; motion and video productions; experience, education and recognition; certificates and professional documents; profile and contact information.
Bilingual publishing
Each important item should have linked English and French versions. Language coverage includes not only paragraphs, but also menus, labels, filters, buttons, interface messages, SEO titles, meta descriptions, alternative text and documents where both versions exist. Quality control must prevent English fragments from remaining on French pages and ensure that language switches lead to equivalent content.
Taxonomies, search and filters
Disciplines, sectors and other metadata connect content and provide several entry points into the portfolio. The Work page combines text search, filters and sorting to help a visitor move from a dense library to a relevant selection. The “Drupal” taxonomy is used only for this self-initiated portfolio. The public-diplomacy case study uses “Web content” rather than “Drupal/Web”.
Reusable components
Cards, project headers, figures, galleries, document lists, calls to action and links between case studies are built as consistent reusable components. This reduces unintended variation and makes it possible to improve a shared experience in one place.
Media and documents
The website treats each media item as contextualised content: title, description, related project, language, date or role where relevant. Images use appropriate formats and dimensions, videos do not autoplay, and documents use understandable labels rather than raw filenames.
Accessibility
Accessibility is verified in the product rather than only claimed in the copy. Priority checks cover heading structure, explicit links and buttons, connected field labels, keyboard navigation, visible focus, colour contrast, useful alternative text, reading order, no video autoplay and behaviour at high zoom. No specific WCAG conformance claim is made without a dedicated audit.
Privacy and measurement
The code audit found no analytics tool, advertising pixel or font loaded from a third-party service. A privacy-enhanced YouTube embed is clearly identified in the relevant case study; it may establish an external connection when the player loads. Any future analytics solution must be documented before activation.
Performance and maintenance
The website is designed to remain readable and efficient across screen sizes. Verified configuration enables CSS/JavaScript aggregation and compression; templates use WebP images where available and lazy loading for non-priority media. Maintenance covers Drupal security updates, database and file backups, link checking, translation review and monitoring of oversized media.
What this project demonstrates
This project demonstrates hands-on Drupal experience applied to a real need: structuring varied content, designing bilingual journeys, organising search and filters, presenting media, maintaining a coherent visual identity and managing the portfolio over time. It is not presented as evidence of multiple Drupal projects, a client Drupal engagement or a specialisation developed over several years.
Repository and configuration audit
Verified technical details
Foundation
Drupal 11.4.4
Theme
Custom ezechiel_portfolio theme
Content
Structured types for case studies, experience, education, recognition and media resources
Bilingual system
Drupal Language and Content Translation modules with linked translations
Search
Custom search across published Drupal entities
Filters
Custom logic for discipline, sector, keyword and sorting
Media
Media Library with portfolio image and local video types
SEO
Metadata, Open Graph, JSON-LD, canonical URLs and hreflang generated by the custom theme and module