Report Bug · Request Feature

Table of Contents

1. about
2. architecture
3. publishing-model
4. repository-structure
5. content-workflow
6. integration-with-the-main-blog
7. faq

---

about

This repository contains the public content of the PullSec blog.

It includes writeups, technical notes, project pages, and public-facing markdown content used by the main Hugo site.
The blog engine, theme integration, layouts, and deployment workflows are managed separately in a private repository.

This separation keeps the architecture clean:

• content stays public
• the site engine stays private
• the deployment pipeline remains isolated

architecture

Important

This repository is intentionally content-only and is consumed by the main blog as a Git submodule.

flowchart LR
    A[Local Content Editing<br/>Markdown + media]
    B[Public Repository<br/>hugo-content]
    C[Private Blog Engine<br/>hugo-fixit]
    D[GitHub Actions]
    E[Hugo Production Build]
    F[Public Website<br/>pullsec.io]

    A -->|git push| B
    B -->|git submodule| C
    C -->|trigger workflow| D
    D -->|build site| E
    E -->|deploy| F

Loading

workflow summary

Stage	Component	Role	Description
Authoring	Local Workspace	Content creation	Write and update markdown content
Source	hugo-content	Public content store	Version control for published content
Integration	hugo-fixit	Site engine	Pulls content via Git submodule
CI/CD	GitHub Actions	Build automation	Generates and deploys the final static site
Deployment	GitHub Pages	Hosting	Serves the final website

publishing-model

Note

This repository is public by design. Only the content is exposed.
The blog engine, configuration, layouts, and deployment logic are kept private.

Repository	Visibility	Purpose
hugo-content	Public	Writeups, posts, pages, and public media
hugo-fixit	Private	Hugo engine, config, layouts, workflows
hugo-community	Public	Giscus / GitHub Discussions backend

repository-structure

about/          About page content
collections/    Collection taxonomy pages
categories/     Category taxonomy pages
friends/        Friends / blogroll page content
posts/          General blog articles
projects/       Project pages
tags/           Tag taxonomy pages
writeups/       Security writeups and walkthroughs

Note

• Content is organized using Hugo-compatible markdown structure.
• Writeups should use page bundles whenever images or local assets are needed.
• Taxonomy folders are kept here so content remains fully separated from the engine.

content-workflow

clone repository

git clone https://github.com/pullsec/hugo-content.git
cd hugo-content

update content

git add .
git commit -m "feat: add new writeup"
git push

update the main blog repository

After pushing content changes, the private blog repository must update its submodule pointer:

cd ../hugo-fixit
git submodule update --remote --merge content
git add content
git commit -m "chore: update content submodule"
git push

integration-with-the-main-blog

This repository is intended to be mounted inside the main blog repository as:

content/

add as submodule

From the main private blog repository:

git submodule add https://github.com/pullsec/hugo-content.git content

If already configured:

git submodule update --init --recursive

local-preview

This repository does not build the site by itself.

To preview content properly, use it through the main Hugo project (hugo-fixit) where the engine, theme, and layout logic are available.

Example from the main blog repository:

podman run --rm -it \
  --userns=keep-id \
  -p 1313:1313 \
  -v "$PWD":/src:Z \
  -w /src \
  ghcr.io/gohugoio/hugo:v0.158.0 \
  server --bind 0.0.0.0 --baseURL http://localhost:1313

faq

why separate content from the main site?

To maintain a clean separation between:

• editorial content
• site engine and configuration
• deployment and automation logic

why keep this repository public?

Because the content itself is intended to be published and shared openly.

why keep the engine private?

To avoid exposing internal site configuration, layout customizations, and deployment implementation.

can this repository be used standalone?

Not as a full website.
It is a content source designed to be consumed by the main Hugo project. test ruleset pipeline