student@hack3rs:~$ cat content-maintenance-process.md
How hack3rs.ca Content Is Maintained and Updated
The site uses an evergreen-first maintenance approach: update core learning pages and tool guides when workflows, terminology, or practical guidance improves, while keeping blog posts date-aware and historical.
prerequisites
- $Interest in white-hat network security learning.
1. Evergreen Core Pages vs Date-Based Posts
Learning modules, threat pages, FAQs, and tool guides are written to stay useful over time. They get updated when explanatory clarity, workflows, references, or defensive guidance can be improved — not on a fixed calendar.
Blog posts are dated and often tied to a specific operational period or seasonal pattern. They stay published for historical context but may be linked to newer evergreen pages when the topic has grown.
That split keeps the site useful for both active learners and people researching how a topic evolved.
2. What Triggers an Update
Updates happen when there are content gaps, better internal linking opportunities, recurring confusion in a section, meaningful changes to a tool workflow worth teaching, or simply a clearer way to explain something.
Navigation improvements are also a trigger — when a new learning module or threat page is added, related pages are updated to link to it so readers do not have to guess what to read next.
Updates prioritize clarity and practical value. Rewrites for their own sake do not happen.
3. How to Read Content Dates
For evergreen pages, focus on the concepts, workflows, and evidence patterns — the fundamentals do not rotate quickly. For blog posts, use the publication date to understand the seasonal or operational framing.
When planning production changes, always verify commands, versions, and vendor-specific behavior against current official documentation and your environment. Site content is a learning guide, not a runbook.
If a page seems outdated or you notice a factual error, the contact details in security.txt are the right place to flag it.
maintenance-process-checklist
- $Evergreen pages are updated for clarity, workflow improvements, and better linking.
- $Blog posts preserve their original context and date.
- $Internal links are reviewed when related pages are added.
- $Readers should validate environment-specific commands against current official docs.
- $Official documentation is the final authority on product and version specifics.