So I had a look at the site.

You asked me to help with the 2026 forum. I ended up rebuilding the site on a branch instead of writing you a list of suggestions, because a list of suggestions is easy to argue with and a working site isn't.

Nothing here is deployed anywhere near production. It's a branch. The live site is untouched and I couldn't change it if I wanted to.

The thing that actually needed fixing

The site was six hand-written HTML pages with the year typed into all of them. Changing editions meant editing every page and hoping you caught them all.

Now the content lives in data files and the pages are generated from it. Adding 2027 is: copy one file, change one number, rebuild. Everything — nav, footer, meta tags, sitemap — follows automatically. 2025 stays up as an archive rather than being overwritten.

Three things I found by accident

• The stylesheet asked for a font that was never loaded. Every page was rendering in whatever the visitor's system picked. It had presumably always looked slightly different on everyone's machine.
• The event date was pixels, not text. It was painted into an image file, so 2026 would have needed new artwork — and until someone made it, the site would have quietly shown last year's date. It's real text now.
• Every photo in the gallery led to a dead link. The lightbox pointed at files that aren't in the repo. Clicking any photo would have 404'd in production.

I'm not saying this to dunk on whoever built it. It's a good-looking site and these are exactly the things you don't notice from the inside.

The photos

The gallery was serving the untouched camera originals — averaging 5.3 MB each, all 76 of them. Now it serves three generated sizes.

• Gallery page, first load 1.9 MB → 0.79 MB
• Opening one photo 5.3 MB → 122 KB
• Retina thumbnails none → included

Those are measured over the wire, not estimated. The retina version costs about what the old blurry one did, so the sharper images are effectively free.

Greek

English stays at the root, Greek lives at /el/, and every page exists in both with a switcher in the nav. The interface and AMTF's own copy are translated. Speaker bios stay in whatever language they were written in, because translating someone's bio for them is rude.

One catch worth knowing: the site's typeface has no Greek characters at all. Left alone, every Greek word would fall back to a different font on every visitor's machine. There's a second font in there now to cover it.

The Greek is my draft and I'd want a native speaker to go through it before it goes near production. That's me, but I'd still rather two of us read it.

What I deliberately did not do

I didn't invent any 2026 content. The 2026 page exists, it has the right shape, and every section that needs real information says so plainly instead of guessing.

I also didn't build ticketing. If you're planning to use something like more.gr, then this is a redirect and not a project, and building it first would have been a waste of both our time. Worth a five-minute conversation before anyone writes code.