Why This Chapter Matters
A modern website is no longer consumed only by people sitting in front of desktop computers.
Today, most visitors access websites through mobile phones, while search engines, AI assistants, voice interfaces and other automated systems continuously analyse website content without ever looking at the page the way a human does.
This has fundamentally changed the role of digital media.
Earlier, a programmer's responsibility was largely to display attractive photographs, graphics and videos. Today, every media file must also become a source of structured knowledge that can be discovered, understood, reused and trusted by both humans and machines.
A photograph is no longer just a picture. It may document an event, identify a product, show a farming practice, preserve historical evidence or explain a technical process. Similarly, a video is not merely something to watch. It may contain demonstrations, interviews, training material or expert opinions that should remain searchable long after the video is published.
The programmer therefore has a much larger responsibility than simply uploading files.
Every media asset should load quickly on mobile devices, consume minimum bandwidth, carry sufficient descriptive information, connect with related content and remain useful for many years.
Good media management is therefore not about creating visually attractive pages. It is about building an organised digital knowledge ecosystem where every photograph, illustration, infographic, audio recording and video contributes meaningfully to the organisation's knowledge base.
This chapter explains the principles every programmer should follow while designing, storing, presenting and maintaining digital media.
________________________________________
Rule 4.1; Treat Every Media File as a Knowledge Asset, Not Decoration
The Rule
Every photograph, graphic, illustration, audio recording and video should contribute useful knowledge instead of merely filling empty space.
Why This Rule Exists
Many organisations invest considerable effort in producing valuable media, but once uploaded, these files remain isolated from the rest of the website.
A photograph may show an important field experiment.
A video may contain an expert explaining a complex subject.
An audio recording may preserve a valuable interview.
Unless these assets are properly organised and described, they become invisible despite being publicly available.
Media should therefore be treated as organisational knowledge that deserves the same importance as written content.
What Most Programmers Do
Media files are often uploaded only because a page appears visually incomplete.
Decorative stock photographs are repeatedly used across multiple pages.
Little attention is given to what information the media actually communicates.
Once uploaded, files remain disconnected from the organisation's larger knowledge system.
Better Practice
Before adding any media file, ask:
• What knowledge does this media convey?
• Does it help explain the subject?
• Can someone understand its purpose without reading the entire page?
• Will it remain useful several years from now?
Every media file should strengthen the page rather than merely decorate it.
Programming Impact
This influences:
• media management systems
• CMS design
• content relationships
• metadata fields
• search functionality
• long-term knowledge preservation
________________________________________
Rule 4.2; Optimise Media for Mobile Devices First
The Rule
Assume that the majority of visitors will access the website through mobile devices using different screen sizes and internet speeds.
Why This Rule Exists
Desktop computers are no longer the primary platform for consuming website content.
Large images that appear beautiful on high-resolution monitors may unnecessarily increase loading time on mobile phones.
Similarly, videos, animations and graphics that consume excessive bandwidth may discourage visitors before the page has fully loaded.
Fast loading is no longer merely a convenience.
It directly influences visitor experience, search visibility and user engagement.
What Most Programmers Do
A single high-resolution image is uploaded and delivered to every visitor regardless of device.
Large files are resized only through CSS while the browser still downloads the complete image.
Multiple heavy images, videos and animations are loaded immediately even when the visitor never scrolls to them.
Better Practice
Generate multiple versions of every important image.
Deliver the most appropriate version according to:
• screen size
• device capability
• display resolution
• connection speed
Use responsive images, modern file formats where appropriate, lazy loading and efficient caching.
Images should remain visually effective without becoming unnecessarily large.
Programming Impact
This affects:
• responsive image generation
• caching strategy
• content delivery
• page speed
• Core Web Vitals
• bandwidth usage
• mobile experience
________________________________________
Rule 4.3; Help Humans and Machines Understand Every Media Asset
The Rule
Every media file should include sufficient descriptive information to explain its meaning.
Why This Rule Exists
Computers do not understand photographs by simply looking at pixels.
They understand filenames, captions, surrounding text, metadata and alternative descriptions.
Similarly, visitors using screen readers depend upon alternative text to understand images.
Without proper descriptions, valuable media becomes difficult to discover, interpret and reuse.
What Most Programmers Do
Images are uploaded using filenames such as:
IMG_4587.jpg
DSC99821.png
Final-New-Latest.jpg
Alternative text is often omitted.
Captions are ignored.
Videos are embedded without summaries.
Audio recordings contain no transcript.
Better Practice
Every important media asset should include appropriate descriptive information.
For photographs:
• meaningful filename
• alternative text
• caption where required
• photographer or source
• date where relevant
For videos:
• title
• description
• thumbnail
• transcript
• summary
• key learning points
For audio recordings:
• speaker
• subject
• duration
• transcript
• recording date
Machines understand context much better than pixels alone.
Programming Impact
This improves:
• accessibility
• search indexing
• AI interpretation
• internal search
• content discovery
• future reuse
________________________________________
Rule 4.4; Connect Every Media Asset to Related Knowledge
The Rule
Media should never exist as isolated files. Every asset should be connected to relevant content throughout the website.
Why This Rule Exists
A single photograph may relate to several articles.
A training video may support multiple case studies.
An interview recording may belong to a project, an expert profile and a knowledge library simultaneously.
When media remains isolated, visitors miss valuable information and organisations repeatedly duplicate the same resources.
What Most Programmers Do
Media is uploaded only for one specific page.
The same file is uploaded again elsewhere under another name.
Relationships between media and content are rarely maintained.
Better Practice
Allow media to connect with:
• articles
• blogs
• reports
• projects
• products
• authors
• locations
• FAQs
• downloads
• related media
One media asset should support multiple knowledge pages without duplication.
Programming Impact
This influences:
• relational databases
• tagging systems
• content linking
• digital asset management
• AI knowledge graphs
• content reuse
________________________________________
Rule 4.5; Deliver Rich Media Without Slowing the Website
The Rule
Provide a rich media experience without sacrificing speed, usability or accessibility.
Why This Rule Exists
Visitors appreciate useful media but dislike waiting for it.
Heavy pages increase abandonment rates, particularly on mobile devices.
Similarly, automatic video playback, unnecessary animations and excessive interactive effects often distract visitors from the actual content.
Good engineering balances quality with performance.
What Most Programmers Do
Every page attempts to impress visitors through:
• large sliders
• background videos
• autoplay media
• excessive animations
• oversized graphics
The website becomes visually attractive but technically inefficient.
Better Practice
Load only what is immediately required.
Delay non-essential media until the visitor requests it or scrolls near it.
Avoid autoplay except where genuinely necessary.
Use meaningful thumbnails.
Allow visitors to decide when rich media should begin.
Programming Impact
This improves:
• loading speed
• visitor experience
• accessibility
• server performance
• mobile usability
• search performance
________________________________________
Rule 4.6; Preserve Media for Future Discovery and Reuse
The Rule
Store media so that it remains searchable, identifiable and reusable for many years.
Why This Rule Exists
Organisations gradually accumulate thousands of media files.
Without proper organisation, valuable photographs, videos and recordings disappear inside folders even though they continue to exist.
Years later, someone may wish to locate:
• every photograph of a particular project
• every interview by a specific expert
• every drone image of a farm
• every product demonstration video
If media has not been organised properly, these valuable assets become practically lost.
What Most Programmers Do
Files are stored in folders according to upload date or temporary project names.
Ownership information is missing.
Versions become confusing.
Multiple copies of the same file exist.
Searching becomes difficult.
Better Practice
Develop a consistent media management system that records:
• descriptive filenames
• ownership
• copyright
• creator
• subject
• keywords
• location
• project
• creation date
• revision history
• licensing information
The objective is not merely to store media.
It is to preserve organisational knowledge.
Programming Impact
This affects:
• Digital Asset Management (DAM)
• media databases
• metadata architecture
• backup strategies
• search systems
• AI indexing
• long-term maintenance
________________________________________
Chapter Summary
Digital media has evolved far beyond decoration.
Every photograph, graphic, audio recording and video now forms part of an organisation's permanent knowledge ecosystem. These assets must therefore be managed with the same discipline applied to written content.
A programmer's responsibility extends well beyond uploading files. They must ensure that media loads efficiently on mobile devices, carries sufficient descriptive information, integrates with related knowledge, performs well across different platforms and remains accessible for future generations of users and intelligent systems.
The organisations that manage their media as structured knowledge assets will not only build faster and more useful websites, but also create digital repositories that continue generating value long after the original content has been published.
In the AI era, every media file should answer a simple question:
Does this asset merely decorate the website, or does it help preserve, communicate and expand the organisation's knowledge?
