HYM

security x life

Security & Life Log

04 // BLOG // POSITIONING

Why this site covers security, travel and training

Why this personal site is not only a cybersecurity portfolio, and why it also keeps travel and training records.

Article

The article body is loaded from the local content/blog directory at build time.

May 19, 2026Positioning2 min readSecurity, engineering and life methods

Technical content alone is incomplete

Security and engineering are the main line of this site. But if a personal website only contains projects, skills and posts, it can easily become a more polished resume.

The goal here is closer to a long-term record system: a place that shows technical direction while also keeping traces of travel, training and daily rhythm.

Life sections are not off-topic

Travel and training do not directly belong to cybersecurity, but they express the same underlying habits: recording, reviewing and managing oneself over time.

  • Travel notes show observation and expression.
  • Training records show consistency, planning and boundaries.
  • Technical writing shows analysis, implementation and delivery.

Together, they give a fuller picture than a single-purpose portfolio.

Boundaries matter

Life records should not become overexposure. The fitness page shows current status and plan, not a full private log. The travel page records cities and impressions, not every photo.

Clear boundaries make the content maintainable.

The right version for now

The current version connects security content, blog posts, travel notes, training status, terminal interaction and a lightweight CMS. What will determine its quality next is steady real content, not making every page crowded at once.

Views and likes

Views

Loading

Likes

Loading

Article info

Content path

content/blog/en/security-life-site-positioning.md

Category

Positioning

Reading time

2 min read

Tags

securitylife loglong-term practice
Keep reading

May 20, 2026

What a personal site still needs after the features work

A review of what matters when this site moves from a working feature base toward public-ready content.

May 18, 2026

Terminal aesthetics without sacrificing readability

A practical note on keeping a strong terminal identity without making the site harder to scan or evaluate.

May 17, 2026

Why the blog and CMS stay content-as-code

Why Markdown files plus a lightweight publishing surface are a better early trade-off than building a full database-backed CMS.

May 16, 2026

Treat easter eggs as a system, not scattered tricks

A planning note on building easter eggs as a coherent registry with explicit triggers, rewards and persistence.