Blog

Guides, tutorials and honest write-ups from DRS Web on coding, SEO, AI and open source — the things we work out while building for clients, written down while they are still fresh. Filter by topic or by programming language to narrow this down to whatever is relevant to you, or just read from the top.

Frequently asked questions

What does DRS Web write about here?

Four things, mostly: web development, SEO, practical AI and open source. The posts range from step-by-step tutorials you can follow at a keyboard to opinionated write-ups of decisions we had to make. You can narrow the list by topic or by programming language using the filters on this page, or browse everything from the blog index.

Who writes these articles?

The DRS Web team, based in the North West of England. We build WordPress websites, mobile apps, UX and UI design and IT infrastructure for clients, and we also build free websites for community projects, CICs and small charities in the North West supporting neurodiverse people. What gets written here comes out of that work.

Can I use the code from these posts in my own projects?

Yes. Code in these articles is there to be used — copy it, adapt it, ship it. Test it in your own context first, because examples are trimmed for clarity and usually leave out the error handling and edge cases a production version needs. Where a post builds on someone else’s library or project, that project’s own licence applies to it.

How often is new content published?

New posts go up as the work produces something worth writing down, rather than on a fixed schedule. The blog index is ordered newest first, so the top of the list is always the most recent thing published. Filtering by topic or language keeps that ordering, so you can see what is current within a subject too.

I have spotted a mistake in an article — how do I tell you?

Please get in touch through the contact page. Technical writing goes stale, tools change their defaults, and we would far rather correct an article than leave it quietly misleading someone. A correction is most useful with the post title and the exact command, snippet or step that did not work, so we can reproduce it before changing anything.