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

Content is never lost since ours is a file based cms backed up to git. We handle markdown, html, php, sheets, decks, email engage forms, rich pages, ai chat exports and the menu is derived by simply reading folders and files.

So a website is really a 3 year outline of what sorts of content is needed, to support which areas and activities and then built iteratively.

The core goal of the training is to show how simply a federated website can be organised, basic tortoisegit usage, vs code and the nuances of the proprietary framework which stitches everything together.

Media is photos, pdfs and embedded youtube and spotify. Pdfs are only to support legacy content or document repositories. We prefer html as its responsive.

Themes use canvastemplate.com by default and rich pages can be built with clear separation of content from html either by php, tsv or html.

Training includes use of tools and project management practices including google docs.

Content is developed offline first so a lead can review work on a machine before it is checked in and deployed to the server.

Top level has sections which do not appear in the url, then node then sub node then page. The menu has a node level series of dropdowns and deep contectual menus that mirror the folder hierarchy.

Since content is transparent as public sites are required to have their git repositories public as well, we even encourage conversations "WithAI" to be published as is.

A https://joyfulearth.org/assets/cdn/ variable can map to a special site folder or be loaded from a specific subfolder of our cdn subdomain. This is done to prevent site folders or federated sections from getting bloated.

AmadeusWeb Spring is a mature 7 year old codebase, the culmination of my 25 years as a coder and builder of frameworks.

Goodbye SQL, goodbye login and security nightmares as deploy is a simple ftp upload. Goodbye bloat and the days when an algorithm controls the engagement.

Landing pages can be fed by an articles sheet while the actual metadata is loaded from the article file directly. This means seo info, title, date etc is definable along with the page direct.

No system emails, just structured email templates that the visitor has opened as a draft that they have to email in. So no captchas either.

Decks use revealjs of slides.com.

The builder is simple and elegant and uses php, hosted on apache. Hosting is managed exclusively by me and comes with an annual fee, payable alongside the platform fee.

I recommend vs code for editing site content. I also see this new way of developing as truly in the spirit of building an internet of missions.

I dont see AI as anything more than a conversationalist or content partner so dont ask me why there isnt a bot or a cli.

What is your mission? And what skills to aid in that are you most eager to learn?