Last year I started working on SlothCMS, it’s still in progress but it’s completely different project than when it started.
Lessons from biting more than I can chew

Last year I started working on SlothCMS, it’s still in progress but it’s completely different project than when it started.
A year ago when I started with SlothCMS I had some plans. I failed all of them. In this post I’d like to talk where and why I did failed.
It’s been a while, four and a half years in fact, since I wrote anything about my tools. So this post is long overdue.
Not all disabilities are treated equally and you can’t create 100% accessible space. Those two rules are absolute. What you can do is to create things which can be easily made accessible. CSS Tricks is tricky but it can be made accessible for a subset of people living with anxiety.
My first version of CSS was 2 and the latest CSS version is 3 which was kind of released in early 2010’s. And since then we are to some degree stuck with it even though CSS from 2018 is a lot more capable than CSS from 2012.
No documentation or self-documenting code are as bad as documentation for documentation’s sake. So what to use on a project which will be developed in bursts from time to time?
I am starting to experiment with Python 3 and setting up the environment is my pain point. So here’s my cheat sheet.
This is apparently an annual post about not being good enough in your own eyes.
While working on SlothCMS I encountered a problem, how to pass a security token between front-end and back-end. In this post I want to explore several possibilities.
Continue reading “Passing security token between back-end and front-end”