amazee.ai WordPress AI demo – main

Author: admin

  • Getting Started with Headless WordPress: An Honest Guide

    Headless WordPress promises the best of both worlds: editors keep the familiar publishing experience, developers get a modern front-end stack. After shipping a dozen headless projects, here is the honest guide I wish someone had handed me at the start.

    When headless makes sense — and when it doesn’t

    Choose headless when you have genuinely multiple consumers of content (web, apps, digital signage), hard performance requirements, or a front-end team that lives in React or Vue. Skip it when you have a content site with a small team: the block editor, previews, menus, and plugins you get for free in traditional WordPress take real engineering effort to rebuild against an API.

    The stack

    • Content API: the REST API ships with core; WPGraphQL is worth the plugin for complex queries
    • Front end: Next.js remains the safest choice for incremental static regeneration
    • Previews: solve this first, not last — editors will judge the whole project by it
    • Webhooks: trigger rebuilds on publish with a small must-use plugin

    The three problems everyone hits

    First, permalinks: WordPress generates absolute URLs pointing at the CMS domain, and you will chase them through content, menus, and sitemaps. Second, previews: the editor expects to render drafts, and your static front end does not know about them — you need a preview route that queries drafts with authentication. Third, images: WordPress media URLs point at your CMS server, so put a CDN or image proxy in front early.

    None of these are hard individually. Together they are the difference between a two-week estimate and a two-month project. Budget accordingly, keep the CMS and front end in separate repositories with separate deploy pipelines, and your future self will thank you.

  • Sustainability Report 2026: 34% Emissions Cut, and Where We Fell Short

    Today we are publishing our 2026 Sustainability Report, covering the full calendar year 2025 across all our data centre regions and offices. The headline: we reduced absolute scope 2 emissions by 34 percent while growing compute capacity by over 60 percent.

    Key figures

    • 100% renewable electricity across all Swiss and EU data centre operations
    • 34% reduction in absolute scope 2 emissions year over year
    • Average PUE of 1.18 across owned facilities, down from 1.26
    • Waste heat from our Zürich facility now warms 400 nearby apartments

    Where we fell short

    Transparency requires reporting misses alongside wins. Our scope 3 supplier emissions remain an estimate rather than a measurement for 40 percent of our vendor base, and our target of full measurement by end of 2025 slipped to mid-2026. Business travel emissions also rose 12 percent as in-person customer work rebounded — we have introduced a per-team travel carbon budget for 2026 to bring this back in line.

    The full 48-page report, including our methodology and third-party assurance statement, is available for download. We welcome scrutiny: sustainability claims in our industry too often evaporate under inspection, and the only remedy is publishing numbers someone else can check.

  • Rösti with Alpine Cheese: The Only Recipe You Need

    Every Swiss family guards its own rösti doctrine. Some swear by raw potatoes, others par-boil the night before. Some add bacon, some consider that heresy. This version — par-boiled, generously buttered, finished with Alpine cheese — is the one I learned in a farmhouse kitchen above Appenzell, and it has never failed me.

    Ingredients (serves 4)

    • 1 kg waxy potatoes (Charlotte or similar), boiled in their skins the day before
    • 60 g butter, plus more for finishing
    • 150 g Appenzeller or Gruyère, coarsely grated
    • 1 small onion, finely sliced (optional but recommended)
    • Sea salt and black pepper

    Method

    Peel the cold boiled potatoes and grate them on the coarse side of a box grater. Work gently — you want distinct strands, not mash. Season with a teaspoon of salt and a few grinds of pepper.

    Melt half the butter in a heavy 24 cm frying pan over medium heat. If using onion, soften it first for three minutes. Add the potatoes and press them gently into an even cake with a spatula. Cook undisturbed for 12 to 15 minutes until the underside is deep golden — resist the urge to peek before the ten-minute mark.

    Now the flip: slide the rösti onto a large plate, invert the pan over it, and turn the whole assembly over in one confident motion. Hesitation is the enemy. Add the remaining butter around the edges, scatter half the cheese over the top, and cook another 10 minutes until the second side matches the first.

    Finish with the rest of the cheese and let it melt under a lid for two minutes. Serve straight from the pan, ideally with fried eggs and a sharp green salad to cut the richness. Leftovers reheat surprisingly well in a dry pan, though in twenty years I have never actually had leftovers.

    A proper rösti should shatter at the edge and yield at the centre — crisp armour over a molten heart.

  • Why Private AI Matters for European Enterprises

    When a European hospital group asked its board to approve a generative AI rollout last year, the project stalled on a single question: where, exactly, does the data go? It is the question every compliance officer in Europe is now asking, and the answer determines whether AI projects ship or die in review.

    The sovereignty gap

    Most popular AI services route prompts through infrastructure governed by foreign jurisdictions. For a marketing team drafting social posts, that may be acceptable. For a hospital summarising patient notes, a bank triaging support tickets, or a government agency processing citizen requests, it frequently is not. GDPR, the EU AI Act, and sector rules like HIPAA and FINMA circulars create overlapping obligations that generic cloud AI terms rarely satisfy.

    Private AI hosting closes this gap by keeping inference inside a defined jurisdiction, on dedicated infrastructure, with contractual guarantees about data retention. The model weights run where your lawyers can point to them on a map.

    What to evaluate

    • Data residency: in which country does inference happen, and is that contractually guaranteed?
    • Retention: are prompts and completions logged, and for how long?
    • Model provenance: can you audit which model version processed your data?
    • Exit strategy: OpenAI-compatible APIs mean you are never locked to one vendor

    Performance is no longer the trade-off

    The old objection to private AI was quality: self-hosted models trailed the frontier by a year or more. That gap has collapsed. Current open-weight and privately-hostable frontier models handle summarisation, extraction, classification, and drafting at a level indistinguishable from public cloud offerings for the vast majority of enterprise workloads. The remaining question is not whether private AI is good enough — it is whether your data governance can afford anything else.

    The practical path for most organisations: start with one high-volume, low-risk workload — support ticket triage is the classic choice — measure quality against your current baseline, and expand from there. Six months later, the compliance review that used to kill projects becomes a formality, because the answer to “where does the data go” is finally simple.

  • 48 Hours in Zürich: A Local’s Weekend Guide

    Zürich has a reputation problem. Ask most travellers and they will tell you it is a city of banks, expensive watches, and not much else. Spend a weekend here, though, and a different city emerges: one of lake swims at sunrise, industrial quarters turned into galleries, and some of the best coffee in central Europe.

    Day One: Old Town and the Lake

    Start early at Grossmünster, the twin-towered church that anchors the old town. The climb up the Karlsturm costs a few francs and rewards you with the best view in the city: the Limmat river below, the Alps on the horizon, and the lake stretching south like a sheet of hammered silver. From there, wander the Niederdorf’s cobbled lanes before the shops open, when the quarter still belongs to delivery bikes and bakers.

    For lunch, skip the tourist cafés along the river and head to a workers’ canteen turned lunch spot in Kreis 4. A plate of Zürcher Geschnetzeltes — veal in cream sauce with crispy rösti — will set you back less than you fear, and more than you hoped. Afternoons belong to the lake. Locals swim from the wooden platforms at Seebad Utoquai from May to September; in winter, the same crowd sits in the sauna boats moored along the shore.

    Day Two: Zürich West

    The city’s former industrial district is where Zürich stops being polite. Under the railway viaduct, arches that once stored coal now house bakeries, wine bars, and a food market. The Löwenbräukunst complex stacks three galleries inside an old brewery, and the Freitag tower — built from stacked shipping containers — sells bags made from recycled truck tarps to a queue of design tourists.

    • Take tram 4 or 13 to Escher-Wyss-Platz and walk from there
    • The Prime Tower’s 35th-floor bar has the best aperitivo view
    • Frau Gerolds Garten is the summer spot for outdoor drinks
    • Im Viadukt market hall closes at 8pm on weekdays

    Zürich is the only city I know where you can attend a gallery opening, swim in drinking-water-clean river, and catch a night train to three different countries — all in the same evening.

    Budget note: Zürich is unapologetically expensive, but the ZürichCARD (27 CHF for 24 hours) covers all public transport and most museum entries. Tap water is excellent everywhere, and the 1,200 public fountains all run with drinking water — bring a bottle and skip the 5-franc café refills.

  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!