We all need passwords and we are all encouraged (or forced) to make them “complex” so that no one will guess them. This is potentially the most significant vulnerability that any individual or organisation has when they are trying to ensure that thier personal details and content is secured from theft and malicious use. The Problem The sheer number of passwords that we need to remember is daunting: User account to sign in to device Wi-fi password to access the internet User account for email provider User account for each individula web-site User account for each app We all gravitate to using a single password as it is easier to remember, but then each time we need to create a password, the rules might be different:

This may seem like a strange title for a blog post, so let me explain. As many of us involved in IT do, I provide tech support for my family, and also provide them with Office 365 which provides email, Office Apps and a range of tools that are probably less familiar. Supporting my family has its challenges, in particular, trying to introduce new ways of working with new tools. This isn’t so different from any organisation that changes their technology and the way that they want their employees to work.

As a good digital citizen, I need to consider legislation such as GDPR (and from Wikipedia) and comply with it. Hugo has page on GDPR but I could not see any details on setting up a consent banner for cookies. Solution To create a cookie consent notice I followe the excellent blog from LittleBigTech. This approach consists of a few simple steps: Create a partial called cookie-consent.html Replace the reference to analytics with this partial In my case I had a patrtial that inclded the gtag from the config, so I updated the code provided to use this approach rather than hard coding the gtag Add a content/privacy.

My blog is up and running and I have more than 10 years of content migrated. As part of the migration, I have reviewed categories and tags to ensure that they are consistent, but also to make it easier to find related content. I can find content based on categories and tags by browsing the pages that list them and the associated pages, but I want to be able to search as well.

Part of my rationale for moving to Hugo was to remove the need to manage comments. Instead, I wanted to have comments in LinkedIn or on Twitter. Very quickly the need to allow people to comment on these mediums came about - credit to Luke Evans (, ) for highlighting the need to comment. Links within posts In the above paragraph, I put in links to my guinea pig, Luke. To do this I wrote a short code for each platforminto which I could pass the appropriate value to allow the path to be created.

In part 1 of this series I covered what it takes to create a post using Hugo. This post covers the structure of the files that make up the site and allow a post to be published on the site. Directories When a new Hugo site is created, a small number of directories are created. These are described in the formal documentation but I have my own descriptions below: archetypes - stores the default files and file bundles used when new content is created config - contains the config files - this one I added so I could split the config settings across different files content - contains all of the user created content data - if used, contains data files layouts - contains the files used to layout the site and provide shortcodes static - files that are not changed and served as is favicons - contains the favicons files images - image files themes - contains a folder for each theme and theme component used on the site Core Directories Several of these directories are essential to understand as they contain the core building blocks of a Hugo site.

I’m happy I have moved everything to Hugo but I learned a lot on the journey and I need to remember what I have done so I can change things in the future and share my experiences. Creating a new post Possibly the most important element to remember: what do I type to create a new post? hugo new posts/2022/2022-01-04-notes-on-hugo -k post-bundle The elements of the statement are as follows

I have been blogging, on and off, for longer than I thought. I have recently not been blogging as much as I used to and have also had feedback that sometimes when people clicked on links to go to my blog, they were redirected to undesirable sites. For a while, I had been planning to move away from the hosting solution I was using as it was expensive and obviously not as secure as I had thought.

With Microsoft 365 many of us are collaborating via guest access to many tenants owned by clients, partners, communities or even family. Some of these will be following best practice and implementing additional security controls such as MFA. So what happens when you get a new phone or new authentication app and need to change all of those tenants to look at a new authenticator app? You may also have been granted access to apps and groups, or be eligible to request access packages as part of Azure Active Directory Entitlement, or be an approver as part of Access Reviews.

Whenever someone leaves an organisation or changes roles, the permissions of their user account should be checked to ensure that No Teams are left without an owner (every Team should really have two owners) Their access to Teams they no longer need access to is revoked. There are many ways to do this but most organisations will consider this when the need arises. I have published a PowerShell module that provides commandlets to carry out some essential actions to support the management of Teams permissions.