Organisation website
A substantial content structure with menus, categories and languages.
← All technologies
Joomla · BIG FISH
Web development with Joomla
We build organisational websites and editorial sections with structured content, languages and access boundaries. Design follows the content rather than the limits of a ready-made template.
BIG FISH / JOOMLA
01Article and fields
02Action permissions
03Viewing access
04Site template
Design × technology × your workflow
PRODUCT CAPABILITIES
Technology becomes
a working product.
Editorial workflow
Separate preparation, review and publishing responsibilities.
Member content
Audience-specific content with testable access rules.
INTERACTIVE EXAMPLE
Try the workflow.
See the outcome.
An author prepares an article and an editor publishes it for an intended audience. Switch roles and access levels to inspect visibility.
Educational example with fictional data. Actions stay in your browser. This models the workflow; it is not a connected CMS, server or database.
Joomla
JoomlaWorkflow result
The example is ready to explore.
WORKFLOW ARCHITECTURE
Every step has
a responsibility.
01
Article and fields
02
Action permissions
03
Viewing access
04
Site template
| Layer | Outcome |
|---|---|
| Interface | Input, limits, loading and errors are clear. Keyboard operation is available. |
| Data | Values have an owner, format and freshness rules. |
| Release | Critical journeys, backups and recovery have been checked. |
BIG FISH · Joomla
Many sections. One navigation system.
Joomla website development requires clear routes through substantial content. We design menus, categories and links between pages so visitors can find the right section whether they arrive from the homepage, search or a direct link.
For multilingual Joomla portals, we check long headings, language switching and restricted content states. The editing workspace and public website support different roles without mixing their responsibilities.
PRACTICAL GUIDE
Building a product
with Joomla.
Architecture, constraints and testable workflows. The exact configuration follows the project requirements.
Joomla / 01
Articles and categories
Organise news, expert content and services through a deliberate content model. Categories support editorial work without becoming a duplicate URL system. Define introductions, images, authors and topic attributes for cards. Check how each article appears in a listing, search results and its own detail page.
Acceptance check
Card and article use one introduction.
Joomla / 02
Menus and routing
A menu item determines how an article or category is presented. Content can acquire several paths, so define its primary address and navigation rules in advance. Check canonical links and redirects when restructuring menus. Mobile navigation must remain usable with long labels and multiple nesting levels.
Acceptance check
A direct URL opens the intended article.
Joomla / 03
Fields and overrides
Custom fields separate article facts from body text. Render them through controlled template overrides while leaving core and extension code intact. Handle missing values, absent images and long descriptions. Check override compatibility after updates: retaining a file does not guarantee it remains correct for a newer component version.
Acceptance check
A component update is tested with its override.
Draft → Review → Published
Action permission ≠ Viewing access
Author → prepare
Editor → review and publishJoomla / 04
Actions and visibility
Permission to edit an article differs from permission to view it publicly. User groups participate in action permissions; access levels determine the viewing audience. Check inheritance and explicit denials. This page uses a simplified example; production rules must cover the complete hierarchy of groups, categories and components.
Acceptance check
Guests cannot read member content.
Joomla / 05
Editorial workflow
Content moves through understandable preparation, review and publication states. The exact steps and transitions depend on requirements and the selected configuration. Verify scheduled publication against server and editorial time zones. Unpublishing must remove content from listings and clear relevant caches, not merely change an icon in the manager.
Acceptance check
Authors cannot publish without permission.
Joomla / 06
Multilingual content
Associate translated articles with their corresponding menu items. A translation need not be published alongside its source. When unavailable, the language switcher should offer a clear route rather than silently showing a different article. Verify document language, metadata, routing, forms and retention of the selected language after an enquiry.
Acceptance check
A missing translation is not replaced by an unrelated article.
Joomla / 07
Extensions and operations
Check each extension’s Joomla/PHP compatibility, maintenance and required data access. Retest forms, search and media handling in staging after updates. Cache only suitable public responses. Content intended for a restricted group must not enter a shared cache or an unrestricted search index.
Acceptance check
Restricted articles stay out of shared caches.
Joomla / 08
Verification and training
Acceptance covers each role, publishing, restricted content, translations and mobile navigation. Test restoring backups together with media files. Editors receive instructions for fields, menus and audiences. Administrators receive an extension inventory and update procedure so ongoing operations do not depend on a single developer’s memory.
Acceptance check
Each role has a separate acceptance scenario.
FAQ
Before we start
Is this a ready-made product?
No. The example illustrates a proposed workflow for Joomla. We design the production system around your requirements, data and integrations.
Can we retain our current systems?
We first review their interfaces, data ownership and constraints. The result may be an integration, a phased migration or a focused replacement of one component.
What do we receive at handover?
The agreed deliverables include design assets, source code, environment requirements and operational instructions. Scope, ownership and support are recorded in the contract.
Let’s design your product
Tell us about your workflow, audience and existing systems. We will define the interface, technical boundaries and delivery stages.