<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Awattsdev on Medium]]></title>
        <description><![CDATA[Stories by Awattsdev on Medium]]></description>
        <link>https://medium.com/@awattsdev?source=rss-e188f589e2c4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JRMiObelLy0-rhwN</url>
            <title>Stories by Awattsdev on Medium</title>
            <link>https://medium.com/@awattsdev?source=rss-e188f589e2c4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:11:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@awattsdev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Is my website really bilingual? (At least in the eyes of Google)]]></title>
            <link>https://medium.com/@awattsdev/is-my-website-really-bilingual-at-least-in-the-eyes-of-google-58eb227462e4?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/58eb227462e4</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[multilingual-websites]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[multilanguage]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Mon, 26 Oct 2026 12:14:04 GMT</pubDate>
            <atom:updated>2026-10-26T12:14:04.790Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_pVxomYeQ26I3IomVIOpdg.png" /></figure><p>If you run a business in France and your website has a little flag switch in the corner, this one is for you.</p><p>I see it all the time on sites belonging to English-speaking business owners here in Nouvelle-Aquitaine who want to reach the French market. You click the flag button or dropdown, choose the language you want, the page flips into French, and job done. But are your French customers really covered?</p><p>Here’s a test that takes ten seconds. Open your website, look at the address bar at the top, then click the French flag (or whatever other language the site offers). Did the address change? Something like yourbusiness.fr/en becoming yourbusiness.fr/fr? If it did, great, you can probably stop reading. If the address stayed exactly the same, then as far as Google is concerned, your French website doesn’t exist. Which means you won’t display in search results for that language, no matter how good your SEO is.</p><p>Let me explain why. When Google looks at your site, it reads pages, and every page has its own address. A French customer searching for a plumber or a gîte in your area is shown French pages, each with its own address that Google has read and stored. A translate button doesn’t create any of those. It waits until a visitor has already landed on your English page, and then swaps the words on their screen. Google never sees that French version, so it never shows it to anyone searching in French. <a href="https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites">Google’s own guidance for multilingual sites</a> says exactly this: give each language its own address, rather than relying on cookies or browser settings to switch the language.</p><p>So the customers you most want to reach, the French people searching in French, are the ones who will never find you. The button only helps someone who has already found your site in English, and that’s the person who needed it least.</p><p>Depending on how your site is built, there’s a second problem: the translation itself. Often these buttons use machine translation, and nobody checks it. In fact, in many cases you can’t change it even if it’s wrong! It mangles idioms, picks the wrong word for your trade, and switches between tu and vous like it can’t make up its mind. A French reader spots it in the first sentence, and the message they take away is that this business isn’t really for them. Google isn’t keen on it either. Unchecked machine translation is the kind of content it treats as low quality.</p><p>Now, I’m not here to tell you to throw your website away. These problems can be fixed.</p><p>Here’s a little tip for anyone running a <a href="https://www.awattsdev.eu/en/blog/should-i-get-a-wordpress-website">WordPress site</a>. There are well known translation plugins, Polylang, TranslatePress, WPML and Weglot among them, and set up correctly they give every page its own French address and tell Google which version is which. Some of them do this even on their free versions. The catch is that some of the most popular flag plugins only do the on-screen swap unless you pay for an upgrade. They’re quick to install, they look the part, and I suspect a lot of site owners have no idea that’s all they do. If you paid someone to build your site, it’s worth asking them which one you’ve got, or just try the flag test.</p><p>So what does a properly bilingual site look like? Two or more versions of every page, each with its own address, one in English and one in French, plus any other languages you use. Each page tells Google what language it’s in and where its twin lives. The French text is written or checked by someone who speaks French, so it sounds like it was written for a French reader, because it was. And both versions appear in the list of pages your site gives to Google, so it knows to look at them.</p><p>At awattsdev, I handle both of these potential problems. For the projects I work on, each language version is a real page that Google has read. On top of this, they aren’t machine translations. My sites store the actual translations for each language (in a special file type called JSON), so when you flip the flag, the site shows the text that you’ve provided.</p><p>So go and try the flag test on your own site. If the address doesn’t change, ask whoever built it what they used for the French, and whether a French customer searching in French can find you. If half your customers are French, half your website should be too.</p><p><em>Andrew Watts, web developer based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/fr/blog/is-my-website-really-bilingual"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58eb227462e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Est-ce que je devrais vibe-coder mon site web ?]]></title>
            <link>https://medium.com/@awattsdev/est-ce-que-je-devrais-vibe-coder-mon-site-web-b30b2bd05670?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b30b2bd05670</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 13:42:03 GMT</pubDate>
            <atom:updated>2026-10-10T13:42:03.564Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11FSpYp_7s7Bi3m5jHffRg.png" /></figure><p>L’IA, tout le monde s’y met ! “ Demande juste à ChatGPT de le faire “ :) Alors, pour répondre à la question : en gros, oui. Mais il y a plusieurs points à prendre en compte.</p><p>Bon, plus sérieusement. D’abord, je vais vous poser deux questions.</p><p>Première question : avez-vous une connaissance de base du fonctionnement d’internet ?</p><p>Deuxième question : est-ce que vous prévoyez de collecter ou de manipuler les données de vos clients ?</p><p>Si vous répondez non à la première et oui à la deuxième, alors de mon côté, c’est un gros red flag.</p><p>Un mot sur moi. Je suis développeur. J’écris du code pour créer des applications et des logiciels web, et j’utilise l’IA au quotidien. Mes premiers pas dans le monde de l’IA ont consisté à connecter un agent aux repos de mes projets (les dossiers où vit mon code), pour qu’il puisse apprendre ma façon de travailler. J’ai créé des Skills pour l’agent, un peu comme un mode d’emploi, mais pour les agents. Les agents ont un format qu’ils préfèrent, le Markdown, et j’ai plusieurs fichiers dans ce format pour donner du contexte à mon agent. L’agent m’aide à créer mes projets plus vite, c’est tout.</p><p>Maintenant, un petit témoignage. Les agents IA font des erreurs.</p><p>Un exemple. Sur un projet client, j’ai demandé à l’agent de retirer une fonctionnalité. Il a supprimé tout le code, alors que je voulais juste la désactiver. Sur une autre application qui gère des factures, l’agent voulait “ corriger “ les données de vrais clients. Techniquement, ça avait du sens. En réalité, ces données servent aux déclarations fiscales de ces entreprises. Je l’ai arrêté parce que je comprenais ce qu’il y avait en jeu. Quelqu’un qui ne comprend pas le code aurait juste dit oui.</p><p>Les agents ont aussi tendance à compliquer les choses plus que nécessaire. Ils suivent vos instructions, mais il leur manque la nuance pour comprendre ce que vous vouliez vraiment dire.</p><p>Surtout, à mon avis, il faut bien comprendre le sujet sur lequel on demande à l’agent de travailler.</p><p>Un simple site vitrine ? OK, un agent s’en sort très bien. Mais si votre site recueille les données de vos utilisateurs… il y a un gros risque si vous n’êtes pas capable de comprendre ou de vérifier ce que l’agent a écrit.</p><p>Et il y a la loi. Dès que votre site collecte des données personnelles, même un simple formulaire de contact, le RGPD s’applique. C’est vous qui êtes responsable de ces données, pas l’agent. Si vous ne savez pas où elles sont stockées, qui peut y accéder, ou comment elles sont protégées, vous ne pouvez pas répondre à ces questions le jour où quelqu’un vous les pose.</p><p>Donc, voilà mon avis honnête. Revenez à mes deux questions du début. Si vous voulez un site vitrine pour présenter votre activité, allez-y, vibe-codez, c’est une très bonne façon d’apprendre. Mais si votre site doit gérer des données clients, des paiements ou des comptes utilisateurs, faites-vous accompagner par quelqu’un qui comprend ce que l’agent écrit. L’IA est un outil formidable. Ce n’est pas un développeur.</p><p><em>Andrew Watts, développeur web basé en Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/fr/blog/should-i-vibe-code-my-website"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b30b2bd05670" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should I get a WordPress website?]]></title>
            <link>https://medium.com/@awattsdev/should-i-get-a-wordpress-website-bf7a1d1543e5?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf7a1d1543e5</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 16:35:16 GMT</pubDate>
            <atom:updated>2026-10-01T16:35:16.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iJUzVeSLpLFDm0Tdp5VF5g.png" /></figure><p>OK, I’m going to ruffle a few feathers with this one.</p><p>First, let me lay out a few truths. I’m not a WordPress developer. I write software that is used to create websites and web applications, what’s known in the industry as a full stack developer. So I’m not here to sell you WordPress, but I’m not here to trash it either.</p><p>You may be interested to know that around 40% of all websites on the internet run on WordPress. That’s quite staggering considering the other options out there, and there is good reason for it. It’s free to get started, it’s been around since 2003, and almost every web agency and hosting company knows how to work with it.</p><p>So what is WordPress? Think of it as an engine. Technically, it’s built on a wonderful scripting language called PHP, with a database underneath that holds all your text and images. On top of that you choose a theme, which is how your site looks, and plugins, which bolt on extra features like a contact form or a booking calendar. Complicated? Yes it is. It’s a long way from the simple pages the web was built on, and it’s not how web development fundamentals are taught either.</p><p>It’s also worth knowing that a lot of people who call themselves WordPress developers are really designers. That’s not a criticism. Good design matters, and they can make a site look lovely by picking a theme and arranging it in a page builder. But putting a site together isn’t the same as understanding what’s going on underneath it, and the difference tends to show when something breaks or when you want to move. I wrote more about <a href="https://www.awattsdev.eu/en/blog/designer-vs-developer">the difference between a designer and a developer here</a>.</p><p>The internet is a very different beast from what it was 20 years ago. Back then it was mostly a source of information, and WordPress leant into this well, as it started out as a blogging platform to inform people. Nowadays the internet is a responsive and interactive place. Not only does it inform us, we can enter data into it and receive results based on that data. What I mean by that is we can now shop, bank, game and use social media all from behind our devices. WordPress was never designed for the latter, but nonetheless, with several workarounds (you may be familiar with the term WordPress plugins), you can achieve some results.</p><p>Free gets you in the door, but here’s the catch: the work lands on you. A lot of people sign up for free WordPress, pick a template, fill in half of it, leave the stock photos in and never touch it again. On the free plan you also get an address like yourbusiness.wordpress.com and WordPress’s own adverts on your site. It ends up looking like exactly what it is. And your customers judge your business by your website, so a tired DIY site can do you more harm than no site at all.</p><p>Then there’s the upkeep. WordPress itself, your theme and every plugin you’ve added all release updates, and they all need applying. Skip them and you leave security holes open. Most WordPress security problems come from plugins rather than WordPress itself, and every plugin is someone else’s code running on your site. Apply the updates and every so often one clashes with another and something on your site breaks. Someone has to keep on top of it, and if that someone is you, that’s time you’re not spending on your business.</p><p>Here’s the question nobody asks when they set up a WordPress site: what happens if I want to leave?</p><p>Say a few years down the line WordPress isn’t working for you. It’s slow, the updates keep breaking things, or you’ve simply outgrown it. But you like how your site looks and you want to keep it. This is where it gets awkward. WordPress will let you export your words, but your design is built to work inside WordPress and nowhere else. It can’t be picked up and moved. It has to be rebuilt from scratch.</p><p>If your site was made with a page builder like Elementor or Divi, it gets messier still, because your text is tangled up with the builder’s own code. Switch the builder off and your pages fill up with gibberish. The extras stay behind too: your contact form, your booking calendar, the descriptions you wrote for Google. All of those live inside plugins. And if your page addresses change during the move and nobody sets up redirects, Google keeps sending people to pages that no longer exist, and the rankings you’ve built up start to slip.</p><p>For what it’s worth, Wix and Squarespace are even worse on this front. There you can’t take your design with you at all.</p><p>So should you get a WordPress website? There are cases where it’s the right choice. If your business is built around publishing lots of content, articles, news, recipes, a blog that several people write for, WordPress is still very good at that. And if you already have someone who looks after your WordPress site properly, keeping it updated, backed up and secure, there’s no reason to rip it out.</p><p>But if you’re a small business that needs a professional site that looks good on a phone, loads quickly, tells people what you do and lets them get in touch, WordPress is often more machinery than you need.</p><p>And if you’ve got bigger plans, it can end up being the wrong machinery. Say down the line you want to sell online, take bookings, or let customers log in, fill in forms and save their details. On WordPress each of those is another plugin, from another developer, bolted onto a system that started life as a blog, and they all have to get along with each other. It can be done, and plenty of shops run on WooCommerce, but every new feature adds to the pile you have to keep updated. Once customer details are involved, keeping that pile secure is your responsibility too. Built properly from the start, a site can grow with your business, with each new feature designed to fit with the rest rather than bolted on.</p><p>That’s my honest take. Whatever you go with, ask whoever is building your site three things. What is it built on? Who is going to look after it? And can I take it with me if I leave? The answer to that last one tells you more than anything else.</p><p><em>Andrew Watts, web developer based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/should-i-get-a-wordpress-website"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf7a1d1543e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SumUp and e-reporting: who reports your till takings in 2027?]]></title>
            <link>https://medium.com/@awattsdev/sumup-and-e-reporting-who-reports-your-till-takings-in-2027-134c4d1c9df7?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/134c4d1c9df7</guid>
            <category><![CDATA[e-reporting]]></category>
            <category><![CDATA[b2c]]></category>
            <category><![CDATA[point-of-sale]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 12:48:29 GMT</pubDate>
            <atom:updated>2026-09-28T12:48:29.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dnZxP53HZCrpeQtP3cf18g.png" /></figure><p>Back in June I was running one of my IT support sessions at my local cafe and got chatting to the owners, who I know well. I’m building einvoicer, an e-invoicing platform for small French businesses, and they use SumUp as their card provider, so I asked the obvious question: what is SumUp doing about the e-invoicing reform? They didn’t know, and neither did I, but we both assumed a payment provider that size would have something in place. So I started digging there and then. SumUp isn’t handling it themselves. They’re partnering with an approved platform, Indy. That struck me as a little strange, but on the face of it the problem is solved, even if it isn’t a very flexible solution for their customers.</p><p>Since then I’ve spent a few months digging into what that actually means for the people using those little card readers, because there’s a gap here that I don’t think many merchants know about yet. Especially if, like a lot of us running businesses out here, French is your second language and most of what’s written about the reform is in French.</p><p>First, the short version of the reform. Since 1 September 2026, every business in France has to be able to receive electronic invoices through an approved platform, a plateforme agréée (PA). From 1 September 2027, small businesses and micro-entreprises also have to start sending their invoices electronically, and at the same time a second obligation kicks in that gets far less attention: e-reporting.</p><p>E-invoicing covers sales between businesses. E-reporting covers everything else, and the big one for a lot of small traders is sales to the public. If you run a cafe, a market stall or a small shop, most of your sales don’t have an invoice at all. Someone taps their card, gets a receipt, and walks off with a coffee. From September 2027 the tax office wants to know about those sales too, sent through a PA as structured data, with your takings broken down by VAT rate, on a regular schedule that depends on your VAT regime.</p><p>So where does SumUp sit in all this? As of September 2026, SumUp is not a PA and hasn’t announced plans to become one. Its invoicing tool, SumUp Factures, produces ordinary PDF invoices rather than the structured Factur-X format the reform requires, and SumUp doesn’t send your sales data to the tax office. You can keep using the card reader, nothing changes there, but the reporting has to happen somewhere else.</p><p>As mentioned above, the somewhere else SumUp points people towards is mainly Indy, and to be fair to Indy, it’s a solid option. It’s a registered PA, and e-reporting is included in its free plan. For invoices you create in Indy, the reporting happens automatically.</p><p>The bit that caught my attention is what happens to the card sales that never had an invoice. As far as I could find, Indy doesn’t connect directly to SumUp. Their shopkeeper pages talk about entering your daily till totals, your tickets Z, by hand, alongside a bank feed. The direct integrations Indy lists are Stripe, Shopify, Amazon and PayPal. SumUp isn’t one of them.</p><p>That matters more than it sounds. A bank feed shows you the lump sum SumUp pays into your account, minus fees. It doesn’t show you how much of that was sold at 5.5%, 10% or 20% VAT, which is exactly the breakdown e-reporting needs. So you’re either typing your till totals in every day, or someone is working it out later from paperwork. For a busy cafe owner, that’s one more job at the end of a long day, every day, forever.</p><p>The frustrating part is that the data already exists. SumUp has a proper API, and provided you’ve set VAT rates on your products in the SumUp app, every sale that goes through it carries the VAT breakdown by rate. It’s sitting there. It just isn’t being sent anywhere.</p><p>That’s the piece I’m building into einvoicer. The idea is simple: you connect your SumUp account once, einvoicer pulls your transactions in automatically, groups them by VAT rate, and submits the e-reporting to the tax office through our approved platform partner. No daily totals to type in, no separate app to remember.</p><p>I’m not writing this to tell anyone Indy is wrong for them. If you already issue most of your sales as invoices, it may be all you need. But if you take a lot of card payments for small everyday sales, and SumUp has sent you off to set up another platform, it’s worth asking a simple question before you commit: how are my till takings going to get reported? If the answer is “I type them in”, there’s a better way coming.</p><p>A year sounds like plenty of time, but September 2027 will come around quickly, and the businesses that sort this out early are the ones that won’t be scrambling in August. If you’re a SumUp user and want to be one of the first to try the automatic connection, get in touch. I’m happy to answer questions either way.</p><p><em>Andrew Watts, builder of einvoicer, based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/sumup-e-reporting-2027"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=134c4d1c9df7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bug That Only Shows Up on Touch-Screen Laptops]]></title>
            <link>https://medium.com/@awattsdev/the-bug-that-only-shows-up-on-touch-screen-laptops-85c7a87fa316?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c7a87fa316</guid>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Thu, 23 Jul 2026 08:30:12 GMT</pubDate>
            <atom:updated>2026-07-23T08:30:12.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F08KAYELH0uge3v7_HpnkQ.png" /></figure><p>I launched a site a few days ago for a client who runs an animal communication and holistic wellbeing practice. Fully bilingual, English and French, built from scratch, tested on my phone, tested on a tablet, tested on my desktop with a mouse. Everything worked. Then she messaged me. The menu wouldn’t open. Not on her phone, she said. Just on her laptop.</p><p>That sentence alone should have told me something was odd, because a laptop should be the easiest device to get right. It’s not a phone with a tiny screen, it’s not a tablet you’re guessing about, it’s just a browser with a mouse or trackpad like the one I build everything on. So my first thought was that she meant her phone after all, or that she’d cleared cache wrong, or something equally boring. I asked her to send a screen recording.</p><p>She had a touch screen laptop. One of those Windows convertibles you can tap directly on the display, but she was also using the trackpad most of the time like anyone would. And that’s where it went wrong.</p><p>The dropdown menus on the site only opened on hover, a fairly normal choice for a desktop nav. To decide whether to show a hover menu or a tap-friendly one, I’d used a CSS media query that checks the type of pointer a device has, pointer: fine for a mouse or trackpad, pointer: coarse for a finger on a touchscreen. It’s the standard way to tell the two apart without guessing from screen width, which breaks constantly on tablets and now, apparently, laptops too.</p><p>The problem is a touch screen laptop reports pointer: fine, because it has a trackpad, even though the person using it might be tapping the screen directly half the time. The browser has no way of knowing which input she actually used in that moment. So my hover menu correctly identified her device as having a precise pointer and never considered that she might tap the screen with a finger instead of clicking with the trackpad.</p><p>The fix was simple once I understood it. Stop relying on hover to open the menu at all. Make it open on click or tap instead, and let hover be a bonus for mouse users rather than the only way in. It took about twenty minutes to change once I knew what was actually happening, which is usually how these things go. The hard part isn’t the fix, it’s realising that a device you’d never think to test on exists and behaves differently to what the spec assumes.</p><p>If you’re building anything with a hover menu, it’s worth asking yourself the same question I should have asked earlier. Are you assuming mouse or touch based on the device type, or are you actually handling both regardless of what the browser tells you it thinks it has? Touch screen laptops aren’t rare. I just hadn’t built for one before.</p><p><em>Andrew Watts, web developer based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/touch-screen-laptop-nav-bug"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c7a87fa316" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Factur-X explained: what it is, how it works, and what building it taught me]]></title>
            <link>https://medium.com/@awattsdev/factur-x-explained-what-it-is-how-it-works-and-what-building-it-taught-me-7b5f401f0072?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b5f401f0072</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[einvoice]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Wed, 24 Jun 2026 16:34:49 GMT</pubDate>
            <atom:updated>2026-06-24T16:34:49.447Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5EI88RxY9jrh2azR3sUUQ.jpeg" /></figure><p>France is mandating structured electronic invoicing for all businesses from September 2026. If you’re building anything that touches invoicing for French or European clients, you’re going to need to know about Factur-X. Here’s what it actually is, because there’s a lot of confusion around it.</p><p>Factur-X is a hybrid invoice format. On the surface it looks like a normal PDF, something you can open, read and print like any other document. But embedded inside the PDF file is a structured XML document containing all the same invoice data in machine-readable form. The format is built on PDF/A-3, which is an ISO standard for archival PDFs, and the XML follows the Cross Industry Invoice (CII) schema.</p><p>The PDF part is for humans. The XML part is for machines. Both live in the same file, which is what makes it a hybrid.</p><p>This is actually a clever solution to a real problem. An invoice needs to be sent once and handled differently depending on who receives it. A small supplier with no automation can open the PDF and read it. A large organisation with accounting software can extract the XML and process it directly. You don’t need two separate files or two separate workflows, one file does both jobs.</p><p>Factur-X comes in several profiles, each one requiring a different amount of data in the XML. The MINIMUM profile requires almost nothing, just identifiers and totals. The EN16931 profile follows the European standard and requires a full breakdown of line items, VAT rates, payment terms, buyer and seller details and more. Which profile you need depends on who you’re invoicing and what their systems expect.</p><p>This is where it gets complicated in practice. The XML schema sounds straightforward until you start implementing it. The field names are not obvious, the nesting structure takes some getting used to, and there are validation rules that aren’t clearly documented in one place. I spent a lot of time on things like the correct structure for a VAT breakdown, which fields are required at which profile level, and why a file that looked correct to me kept failing validation.</p><p>The PDF generation side has its own challenges. You need to produce a valid PDF/A-3, which is stricter than a regular PDF. Fonts need to be embedded, certain features are not allowed, and the file metadata needs to follow specific conventions. If you get any of that wrong, the output won’t pass validation even if the XML inside it is perfect.</p><p>If you want to validate a Factur-X file yourself, the FNFE validator (FNFE-MPE is the French association behind the standard) is the most reliable tool I found. The official specification documents are freely available too, though they assume some familiarity with XML and the UN/CEFACT CII schema.</p><p>I built Factur-X generation into Einvoicer as part of getting it ready for the September 2026 compliance deadline. The Factur-X part sits alongside Peppol BIS 3.0 output and integration with the Super PDP network, which handles the actual submission infrastructure for France. That’s a separate topic, but worth knowing that Factur-X is the document format and Peppol is the delivery network. They’re related but not the same thing.</p><p>If you’re building invoicing software for the French market, Factur-X is not optional from September 2026. For business-to-government invoicing it’s already required. For B2B it rolls out by company size, with larger businesses going first.</p><p>The good news is that the hybrid approach means you don’t need to throw away your existing PDF generation. If you’re already producing invoices as PDFs, you’re partway there. The main work is generating valid CII XML, embedding it correctly into a PDF/A-3 container, and validating the output. Once that pipeline is in place, the format itself is not as intimidating as the documentation makes it look.</p><p>Happy to answer questions if you’re working on something similar.</p><p><em>Andrew Watts, full stack developer based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/facturx-explained"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b5f401f0072" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A View on E-invoicing]]></title>
            <link>https://medium.com/@awattsdev/a-view-on-e-invoicing-01eb194808d1?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/01eb194808d1</guid>
            <category><![CDATA[electronic-invoicing]]></category>
            <category><![CDATA[e-invoicing]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 19:27:16 GMT</pubDate>
            <atom:updated>2026-06-16T19:27:16.929Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_4kEmBWqdon1NKWqp81Pw.png" /></figure><p>E-invoicing. I imagine you’re all sick of hearing about it. I don’t blame you. The French government have made a complete mess of this one. Electronic invoicing, another administrative tool to keep tabs on us all.</p><p>Originally they were going to build their own government platform to manage it. I’ve lived in France for ten years now, and for anyone who’s been here long enough, using French government websites (impots.gouv, ANTS, and the rest) is a bit like playing Russian roulette as to whether they’ll actually work. To their credit, they looked at their own track record and realised they had absolutely no chance of building a working system for four million French businesses to submit every invoice through their already creaking IT infrastructure. So they shelved it and opened the door to private companies who could become accredited platforms, known as PDPs.</p><p>It was March this year that I first looked into it properly. I’m a software developer, I spend most of my time writing code. Not wanting to pay a monthly fee to a private platform, the first thing I Googled was whether any of the accredited providers offered an API. What that means in plain English: a way for developers to plug into the platform’s core logic and build their own tools on top of it, rather than using a ready-made app that you pay for. The answer was one. One out of 112 registered providers. They’re called SuperPDP, and I’ve been working with their software ever since.</p><p>Initially I just wanted something simple for myself. I run a free IT support session twice a month at a local English-run cafe in a town called Civray, 86400. If you’re ever in the area, I’d highly recommend a visit. It’s called Crafty Cafe, run by a lovely couple, Jen and Simon. E-invoicing came up a lot in those sessions. So one day I made a quick video of the little tool I’d built, posted it on Facebook, and asked who’d be interested in something like this.</p><p>The response was pretty amazing, especially for me. I usually get two likes if I’m lucky. I mean, who cares about a bloke posting on social media about writing code? But I realised there were a lot of confused people out there, and that’s how einvoicer.fr was born. I expanded the platform so anyone can use it, and this week it started accepting its first users.</p><p>Sorry for the plug, but where better to plug your own product than your own blog on your own website.</p><p>If anyone is still confused by all of this, please don’t hesitate to get in touch. I should be able to point you in the right direction.</p><p><em>Andrew Watts, web developer based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/a-view-on-e-invoicing"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01eb194808d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your AI Social Media Posts Sound Like AI (And What to Do About It)]]></title>
            <link>https://medium.com/@awattsdev/why-your-ai-social-media-posts-sound-like-ai-and-what-to-do-about-it-a1c1d7c86155?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1c1d7c86155</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 08:27:00 GMT</pubDate>
            <atom:updated>2026-06-03T08:27:00.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eua14Tj56hIAEMXMcExfZg.jpeg" /></figure><p>Here’s a post you’ll recognise. Business name in capitals, flanked by sparkle emojis. A short intro about being reliable and friendly. Then nine services listed one by one, each with its own cute emoji: a broom for cleaning, a house for property handovers, a key for key handovers. It closes with “I’m happy to help. Send me a message for more information or availability.”</p><p>You’ve seen this post before. You’ve probably seen it dozens of times from dozens of different businesses. That’s the problem.</p><p>Obviously you can’t miss the emojis, but one of the other biggest giveaways? It’s the em-dash (-). Right there in the second line, something like “Based near Poitiers, covering up to 1 hour surrounding areas.” Except it reads “Based near Poitiers — covering up to 1 hour surrounding areas.” That long dash between two clauses is something almost no one writes naturally in a social media post. AI uses it constantly because it’s common in the polished written English the model was trained on. It’s practically a signature at this point. If you spot an em-dash in a Facebook post from a local business, there’s a very good chance a human didn’t write it.</p><p>The other tells are less precise but they stack up. The systematic one-emoji-per-service formatting reads like a template because it is one. The AI assigned a relevant icon to each line because that’s what posts like this tend to do. “Help take the stress away” sounds warm but could apply to literally any service in any industry. “I’m happy to help” is how AI closes things when it has nothing specific to say. “Whether you need help getting your property guest-ready, preparing to move, or simply keeping on top of things” is a sentence construction AI reaches for constantly, three parallel clauses held together with “whether.”</p><p>None of this is a problem with AI, it’s 2026 and I’m not here to judge. But sounding like everyone else? I doubt anyone wants that. It comes down to a problem with the prompt.</p><p>When you open ChatGPT or Claude and type “write a social media post for my cleaning business,” the tool has nothing to go on. It doesn’t know how you speak, what you find funny, what makes your service different from every other cleaner in the area, or what you’d never say in a million years. So it produces the average, the statistical centre of every cleaning business post it has ever seen. Generic phrasing, template structure, emojis as bullet points, a closing line that could belong to anyone.</p><p>The fix is not to stop using AI for content. The fix is to give it enough to work from before you ask it to write anything. That means your own voice written down in plain language. Not your job title, your actual voice. How you normally talk to customers. The things you’d never say. Examples of messages you’ve written that felt right. Specific details about your situation, your location, your clients, the kind of work you actually do. When the AI has that context it stops averaging and starts writing toward something specific. A great way to provide more context is to pass the agent copies of your own previously written emails.</p><p>It also means being deliberate in the prompt itself. “Write a social media post for my cleaning business” is close to the worst prompt you can give. Something like “write a post for a one-person cleaning service based near Poitiers, mainly doing gite handovers and end-of-stay cleans, who wants to come across as practical and straightforward rather than corporate and cheerful” gives the model enough to deviate from the template. It still won’t sound exactly like you. But it will sound less like everyone else.</p><p>And tell it what not to do. If you wouldn’t use nine different emojis in a note to a neighbour, say so. If you’d never use “I’m happy to help” as a sign-off, say so. If you hate em-dashes, say so. The model defaults to these things because they’re common in the genre. You have to specifically ask it not to.</p><p>There’s a broader point here about how most people use these tools. They treat them as text generators: describe a topic, get a post. The results tend to be fine in a forgettable sort of way. The people getting better output are treating the AI more like a collaborator with a short memory that needs briefing every single time. Give it your voice, give it the context, tell it what you don’t want, then edit what comes out toward something that sounds like you actually wrote it.</p><p>The all-caps headline, the emoji list, the generic CTA, the em-dash. None of these things on their own are a disaster. But together they signal to anyone paying attention that no actual person sat down and thought about this post. In a local market where most businesses are generating the same AI-average content, the bar for standing out is actually quite low. You don’t need to be a great writer. You just need to sound like a person.</p><p><em>Andrew Watts, web developer based in Nouvelle-Aquitaine, France.</em></p><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/ai-content-sounds-human"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1c1d7c86155" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do I Need a Web Designer or a Developer?]]></title>
            <link>https://medium.com/@awattsdev/do-i-need-a-web-designer-or-a-developer-c2da78951342?source=rss-e188f589e2c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2da78951342</guid>
            <category><![CDATA[website]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[small-business]]></category>
            <dc:creator><![CDATA[Awattsdev]]></dc:creator>
            <pubDate>Wed, 27 May 2026 12:46:02 GMT</pubDate>
            <atom:updated>2026-05-27T12:46:02.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*93VoUdBBHUXmboOUlDg6ug.jpeg" /></figure><p>It’s a fair question, and the honest answer is: it depends on what you actually need your website to <em>do</em>.</p><p>The terms get used interchangeably, but they’re not the same thing.</p><h3>Designer vs Developer: what’s the actual difference?</h3><p>A designer thinks about how something looks. Colours, layout, fonts, where the eye goes when you land on a page. And to be fair, tools like WordPress, Wix, and Squarespace have closed the gap considerably. A designer with a good eye can now drag and drop their way to a decent-looking site without writing a line of code.</p><p>That’s not nothing. For some businesses it’s genuinely fine.</p><p>But there are trade-offs. You’re renting space on someone else’s platform. Monthly fees that tend to creep up. Templates that only bend so far before everything starts looking the same. And the moment you need something slightly outside what the platform offers: a custom booking flow, a multilingual setup, anything that talks to another service, you hit a wall pretty quickly.</p><p>A developer makes it real. Takes a design and writes the code that turns it into something that works in a browser, loads fast on a phone, and doesn’t fall over when someone fills in a form.</p><h3>How the web has changed</h3><p>The reason this gets confusing is that the web itself has changed enormously. Twenty years ago a “website” was basically a digital flyer. A few pages of text and images, a phone number, maybe a map. You could get away with something that just looked decent because that was almost all it needed to do.</p><p>That’s not where we are now.</p><p>Modern websites handle contact forms, booking requests, product catalogues, member logins, payments, multilingual content, and data that updates in real time. The gap between a “website” and a “web application” is basically gone for most businesses. Your visitors expect things to work, not just look nice.</p><h3>So what do most small businesses actually need?</h3><p>For most of what you need: a professional site that looks clean, loads properly on mobile, has a working contact form and shows up on Google, you need a developer who has a decent eye for design. Not a graphic designer who dabbles in code.</p><p>That’s because the problems you’ll actually run into aren’t visual ones. They’re things like: the form doesn’t send emails. The site looks fine on a laptop but broken on a phone. Google can’t read it properly. It’s slow. The French translation doesn’t work. These are development problems, not design problems.</p><p>Where a dedicated designer makes sense is if you have very specific brand requirements. A business with an existing identity that needs to be translated to the web precisely. In that case, a designer produces the visual spec and a developer builds it. Two separate people doing two separate jobs.</p><p>For most local businesses I work with, that level of separation isn’t necessary and honestly just adds cost and complexity. What they need is someone who can handle the whole thing, design included, and make sure it actually works when it goes live.</p><p><em>Andrew Watts, web developer based in Nouvelle-Aquitaine, France.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uz7ANGhp858LwL2eo-h0Aw.png" /></figure><p><em>Originally published at </em><a href="https://www.awattsdev.eu/en/blog/designer-vs-developer"><em>https://www.awattsdev.eu</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2da78951342" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>