In order for people outside of the development team or community to use your software, care must be given to allow them to write and publish content with the least amount of friction or obstruction as possible. A well crafted interface that allows people to do this isn’t easy. I have started to use Strapi as a serverless backend API interface recently and believe it’s going to be a very useful solution for a lot of projects.
This is the reproduction of an article I wrote for Net Magazine and was published in Issue 308 (August 2018).
‘Form Follows Function’ goes the saying, but with HTML forms, it’s the other way round. At least in terms of what happens when you fill out a form, and then click the button to ‘send’: a function processes the form. What happens during this process? Why is it necessary? What are some of the options for serverless form handling?
Proposing a solution that isn’t a good fit for a project can be dangerious. It can be implemented without real thought, which can cause major frustration or even abandonment of a project. Instead I’m trying to think more about the question, instead of jumping to conclusions.
At a recent WordPress conference in London I gave this talk. It was a terrifying and yet validating experience!
One of the great strengths in static site generator Gatsbyjs is the node API but it can present a few issues in certain circumstances when content is stored as escaped HTML, such as in WordPress posts and pages. Here’s how we recently dealt with this issue when using react-helmet.
Recently someone reached out to ask if they could use my theme that I use on deliciousreverie.co.uk on their site. So I’ve decided to release this theme to the public, albeit with a few changes.
In November last year I switched from using Windows at my place of work to using Pop!_OS by System76, an Ubuntu derivative designed for developers, researchers and scientists. What motivated me to make the switch? What benefits, and disadvantages, has it brought me?
Whilst simultaneously trying to decide what to build in Laravel and considering an old system we had recently inherited, I realised that I liked looking at the spaghetti code, and was comparatively scared of the shiny, new, empty Laravel installation I had just set up. Here’s how I dealt with my first few tasks and began strategising how we could protect our clients’ investment going forward.