Welcome to AmadeusWeb Spring :: Technology for an Internet of Missions

I am Imran, and I train teams to build robust web ecosystems for themselves.

AmadeusWeb Spring is a practical way to organise a mission, its people, its knowledge and its activities on the web. It is built around files, folders, clear editorial responsibility and gradual improvement. The aim is not to make technology the centre of the work, but to give the work a dependable place to grow.

This deep dive explains the ideas behind the platform, how to begin using it and why a simpler web can give organisations more independence.

Why the Current Internet is Over-complicated and Bloated

Much of the current internet assumes that every site needs a database, accounts, dashboards, automated messages, engagement algorithms and layers of third-party services. Those systems can be useful, but they also introduce cost, maintenance, security concerns and dependence on vendors.

AmadeusWeb Spring takes a quieter approach. Content is stored as files and backed up to Git. A simple FTP deployment publishes the reviewed work to an Apache server. Pages can be Markdown, HTML or PHP, while sheets, decks, forms, media and AI conversations can remain part of the same visible content ecosystem.

The result is a website that is easier to inspect, review and move forward. It favours durable content and intentional relationships over constant notification and algorithmic engagement.

Terminologies / Glossary That We Use

• AmadeusWeb Spring: The PHP and Apache based framework that brings the file-based website together.
• Federated website: A group of related sections, sites or initiatives that can be organised independently while belonging to a larger network.
• Section: A top-level organisational area that may shape the menu without appearing in the URL.
• Node: A main area of a site, usually represented by a folder and a menu level.
• Sub node: A deeper area within a node.
• Page: A piece of content such as a Markdown, HTML or PHP file.
• File-based CMS: A content system in which files and folders are the source of truth instead of database records.
• Content metadata: Information such as title, date and SEO details defined alongside the page content.
• Articles sheet: A sheet that can feed a landing page while each article retains its own metadata and content.
• cdn: A variable that maps shared assets to a special site folder or a selected folder on the CDN subdomain.
• WithAI: A transparent area where conversations with AI can be published as part of the public record.
• Offline first: Developing and reviewing content on a local machine before checking it into Git and deploying it.

Getting Started

Begin with the mission rather than the technology. Describe the audiences, activities and knowledge the site must support over roughly three years. This gives the website a useful outline without pretending that every page must be written on the first day.

The normal workflow is:

1. Install and use VS Code to edit the site files.
2. Arrange sections, nodes, sub nodes and pages to reflect the work.
3. Add Markdown, HTML, PHP, sheets, decks, forms and media where they serve the content.
4. Review the site locally and let a lead check the work offline.
5. Use TortoiseGit or another Git client to record and back up changes.
6. Deploy the reviewed files to the Apache server by FTP.

Training covers the tools, the folder conventions, basic Git practice, project management with tools such as Google Docs and the Spring conventions that connect the pieces.

Audiences and Applications

The platform suits missions that need a durable public knowledge base rather than a constantly changing application. It can support organisations, communities, businesses, educators, families, initiatives, people, projects and networks of related sites.

Typical content includes service information, articles, rich pages, document repositories, photo collections, embedded YouTube or Spotify media, presentations made with Reveal.js or Slides, structured email engagement forms and published AI conversations. HTML is preferred for responsive content; PDFs remain useful for legacy material and document repositories.

Each audience can be given an appropriate path through the same folder hierarchy. Node-level dropdowns and deeper contextual menus help visitors understand where they are and find related material.

10 Non Technical Reasons

1. Your mission remains visible instead of being buried in a platform dashboard.
2. Teams can review work together before anything is published.
3. A clear folder structure makes the organisation easier to understand.
4. Content can be developed gradually over a realistic three-year outline.
5. The website can grow with the work rather than forcing a finished launch.
6. Public content is easier to trust when its structure and history are transparent.
7. Responsive HTML serves people on different devices more effectively than a document-only approach.
8. Related initiatives can share a common ecosystem without losing their own identity.
9. Visitors are invited to communicate directly instead of being trapped in automated funnels.
10. The technology supports an internet of missions rather than an economy of attention.

10 Technical Reasons

1. Files and folders are the primary content source, avoiding database administration for ordinary publishing.
2. Git provides history, backup and a visible record of changes.
3. Local development allows content to be reviewed before deployment.
4. Apache and PHP provide a straightforward hosting environment.
5. FTP deployment keeps the publishing step simple and predictable.
6. Markdown, HTML and PHP allow different levels of authoring and presentation.
7. TSV or PHP can separate structured content from page markup when rich pages need it.
8. Article sheets can populate landing pages while metadata stays with each article file.
9. Folder-derived navigation mirrors the content hierarchy without a separate menu database.
10. cdn allows shared or specialised assets to be kept outside bloated site folders.

Our Support In Your Digital Sovreignty

Digital sovereignty begins with knowing where your content is, how it is organised and how it can be recovered. AmadeusWeb Spring supports that independence by keeping the editable source in ordinary files, backing it up to Git and encouraging public sites to maintain public repositories.

Our support includes training in VS Code, TortoiseGit, the Spring framework, content planning and project management. Development happens offline first, so a lead can review work on a machine before it is checked in and deployed. Hosting is managed by Imran and is provided with an annual hosting fee alongside the platform fee.

There is no requirement for a proprietary authoring dashboard to be the only place where your knowledge exists. The site remains understandable as a collection of content and relationships that your team can inspect and continue to build.

Why Simplified Spiritual Tech Matters

Technology should help people attend to meaningful work. A simpler system reduces the energy spent maintaining accounts, troubleshooting integrations and feeding engagement mechanisms. It leaves more attention for relationships, service, learning and the mission itself.

This is not a claim that every technical feature is harmful or that every project should be identical. It is an invitation to choose tools deliberately. A file, a clear folder, a local review and a direct publication path can often do more for long-term clarity than a large stack of invisible services.

AI has a modest role here: it can be a conversationalist and content partner. It does not need to become a bot, a gatekeeper or another system that owns the relationship with the audience. When appropriate, conversations can be published transparently in a WithAI area.

The DAWN Platform at Large

DAWN is the wider vision in which AmadeusWeb Spring operates: a federated web of missions, people, communities, organisations and areas of work. Each site can have its own content and identity while benefiting from shared conventions, shared assets and a common way of navigating from broad sections to detailed pages.

The platform can bring together Markdown, HTML, PHP, sheets, decks, email templates, rich pages, photos, PDFs, embedded media and AI chat exports. Its menus are derived from the folders and files, its article landing pages can be fed from structured sheets, and its assets can be mapped through cdn when they belong in a shared location.

AmadeusWeb Spring represents seven years of development and Imran's twenty-five years of experience building frameworks. Its purpose is ultimately straightforward: help teams plan their content, build it iteratively, publish it transparently and retain ownership of the digital place where their mission lives.

What is your mission, and which skills would help you advance it most eagerly?