The-DevOps-Daily / The-DevOps-Daily/devops-daily
Add inline images, diagrams, and screenshots to articles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 392
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 121
Description
GEO Audit Finding — Medium Priority
Category: Content E-E-A-T (Experience)
Problem
Every article analyzed has exactly one hero SVG image and zero inline visuals. Technical tutorials lack terminal screenshots, architecture diagrams, dashboard screenshots, or step-by-step visual walkthroughs. This signals lack of real-world experience (screenshots = evidence of actually doing the work).
What to Do
Add to key articles:
- Terminal screenshots showing real command outputs
- Architecture diagrams (can use Mermaid or similar)
- Dashboard/UI screenshots where relevant
- Before/after visual comparisons
- Step-by-step visual walkthroughs
Expected Impact
Improves Experience signals and content quality metrics. Visual content is also increasingly referenced by multimodal AI models.
From GEO Audit Report 2026-03-20 — Overall Score: 53/100
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No article files or tests are named. Start by locating the key articles and their existing hero SVGs, then select relevant tutorials and determine which terminal outputs, diagrams, dashboards, comparisons, and walkthroughs are needed; done means the selected articles contain appropriate inline visuals rather than only a hero image.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100