In my Self Promotion of InkedWith post, I mentioned that I had some plans to bring in some new battles with technology. This article is a simple battle I found for removing glare with GIMP in images. I had taken some pictures to be used for printing as well as posting to social media. The problem is that they included some glare. An example of one of these images is below....
Finally, my blog is searchable! I have added enough content that scrolling endlessly through categories wasn’t enough anymore. What Directions I Used As you might recall from my Successfully Deploying a Static WordPress Site post, I moved over to using Simply Static Pro to make my WordPress static. I finally got around to actually looking at the Set up search instructions and everything is live! How Did I Enable Search The directions above tell you to enable fuse and put `` into your page....
While this post is mainly focused on self promotion of InkedWith, my new Shopify store, I figured it was a good way to open up a new wave of technology challenges! With the shameless plug out of the way, allow me to cover the back history of this a little bit. Back History I have always been interested in trying to start some kind of side business. I have never really been able to find what to do....
If you’ve followed my previous posts, you’ll see that I’ve spent some time attempting to build my blog on WordPress and then finally make it static. This had resulted in lots of custom code and even more failed attempts to get things to publish correctly. I’ve finally been successful in building out my site with a combination of some of my failed attempts: Adding Nginx in Front of WordPress Building a Kubernetes Container That Synchs with Private Git Repo Building a Static WordPress The third article above is the most failed attempt to date at making the WordPress site static because it resulted in just as many successes as it did failures....
I recently needed to setup Content Security Policy (CSP) on a website and I couldn’t think of where to get started. The first question that came to mind was what all content do I allow and how do I test everything without having to look through all of the code on the site. This is where the Content-Security-Policy-Report-Only header can come into play. The short version is that this allows you to create a policy in report only mode and you can collect the results at the endpoint specified via the report-uri directive....