http-observatory VS Hugo

Here are a few tools you can use: https://www.zaproxy.org/ (Web app scanner) https://www.ssllabs.com/ssltest/analyze.html?d=importer.bilendo.de (SSL server test) https://github.com/santoru/shcheck (Security Header Check) https://observatory.mozilla.org/ (Content Security Policy validator)

Regular Audits: Use tools like Mozilla Observatory or Security Headers to regularly check your headers.

What's better about this vs. Mozilla Observatory.

https://developer.mozilla.org/en-US/observatory (formerly https://observatory.mozilla.org/)

Or Security Headers?

https://securityheaders.com/

Or VENOM?

https://github.com/oshp/oshp-validator

Applaud the effort, these are things that more devs should be aware of when building websites...

Hey some specific feedback on this tool... On mobile, it has a lot of "view port wobble" and the input fields aren't keyed right, it's just using a straight text input field so you don't get any ".com" buttons as you type. Small UX stuff like that annoy me more than if a page has a privacy policy setup correctly. (=

Detectify once made an offer of making free scans which I took them up on. There are plenty of free Content Security Policy (CSP) and other vulnerability checkers around such as Observatory or Pentest. Shields UP!! will identify which ports you have open.

Website Headers Analyzer (Mozilla)

scan our site with Mozilla Observatory and improve our grade by registering a domain name, enabling HTTPS, adding a certificate and setting security headers

First, for session persistence, go with the default Django session with cookie storage. Set your cookie to HTTP only and ensure your application uses the most common HTTP security headers and controls. Test your application with https://observatory.mozilla.org/ to have an idea of what you're missing.

Mozilla Observatory

A few days back, I wrote a blog post about static site generators, in particular how I decided to migrate my blog from Zola to Hugo. One of my points was to be able to hack my own content before generating the final HTML.

This post is a summary of my recent decision to go back to Hugo after using Zola. I also report on how LLM assistants with Web access can aid in such decisions, not as an authority but as a research assistant.

Hugo is a fast and flexible static site generator built in Go, known for its speed and large theme ecosystem. It supports markdown, taxonomies, multilingual content, and powerful templating with minimal dependencies. Hugo is highly performant and well-suited for building large-scale documentation sites. It’s ideal for teams seeking speed and customization with minimal runtime requirements.

Try Hugo[1]. In depends on a template you choose alone whether Hugo will generate a landing page, a website, a blog, etc.

[1] https://gohugo.io

The content of the guide lives in a single Markdown file, content/_index.md. The website is built using Hugo.

Every PKMS/BASB needs a search functionality. Ever since I've created brainfck to host my own collection of thoughts/ideas/resources (aka Zettelkasten) I wanted to be able to actually search within my collection of org-roam based notes. Meanwhile for all my sites I own (this blog, my CV/portfolio, brainfck and defersec) I use hugo. All of them didn't have proper search capabilities. That's why I was looking for a proper way to include search functionalities without any major effort.

A fast and flexible static site generator built with love by bep, spf13, and friends in Go.

This project demonstrates how to deploy a static website using Hugo and Pulumi on AWS S3. Hugo is a fast static site generator, and Pulumi is an infrastructure-as-code tool that allows you to define cloud resources using TypeScript. The site is deployed to an S3 bucket configured as a static website, with public access enabled for viewing.

It was long my desire to write a blog with stuff that interests me. Lately i was studying Golang and i came across Hugo which is a really nice and fast site generation utility. This was a great opportunity to start my own blog by using Hugo and Github Pages in order to host it. Why?