diff --git a/feature-announcements/chennai-foss-2026/index.html b/feature-announcements/chennai-foss-2026/index.html new file mode 100644 index 0000000..b23af43 --- /dev/null +++ b/feature-announcements/chennai-foss-2026/index.html @@ -0,0 +1,635 @@ + + + + + + DevOps-OS — Chennai FOSS 2026 + + + +
+
+
+
+ +
+
+
Chennai FOSS 2026 · Apr 18
+
+

Simplifying Platform Engineering with DevOps-OS

+

A process-first talk on building improved developer experience workflows with open source building blocks.

+
+ Saravanan Gnanaguru + Founder · CloudEngine Labs + gsaravanen.dev +
+
+
+ cloudenginelabs.io + DevOps-OS open source project +
+
+ +
+
20 minute flow
+
+

What we will cover

+
+

01 · Mindset

Why DevOps starts with process, not tooling.

+

02 · DevOps-OS

Why this project exists and what problem it simplifies.

+

03 · Templates

How repeatable tech stack automation becomes reusable building blocks.

+

04 · Platform view

How templates evolve into platform engineering and IDP adoption.

+
+
+
+ Short talk · lightweight slides · practical framing + Ends with a live demo cue +
+
+ +
+
Process-first understanding
+
+

DevOps is a workflow system before it is a toolchain

+
    +
  • Start with how code moves from idea to production.
    • +
  • Then define approvals, quality gates, deployment flow, and feedback loops.
    • +
  • Only after that should tools and YAML enter the conversation.
    • +
+

When process is clear, automation becomes practical, repeatable, and easier to adopt.

+
+
+ Design the path first + Then automate the path +
+
+ +
+
Why DevOps-OS
+
+

Process > tools

+
+
+

What teams usually do

+

Pick CI/CD, Kubernetes, GitOps, and SRE tools first — then struggle to connect them into one usable workflow.

+
+
+

What DevOps-OS encourages

+

Define the delivery process first — then scaffold the right starting configuration around it.

+
+
+

The project is not just about generating files. It is about making the first layer of platform workflow design simpler.

+
+
+ Less blank-page setup + More workflow clarity +
+
+ +
+
Map process with tools
+
+

Connect each stage to the right building block

+
+
1

Plan

Delivery intent, ownership, release expectations.

+
2

Build & test

GitHub Actions, GitLab CI, Jenkins scaffolds.

+
3

Ship

Kubernetes, deployment config, GitOps handoff.

+
4

Operate

Prometheus, Grafana, SLO, alerting foundations.

+
5

Improve

Template updates, reuse, onboarding, standardisation.

+
+
+
+ Process gives context + Tools implement the context +
+
+ +
+
Templatisation
+
+

Turn stack-specific automation into reusable templates

+
+

Opinionated defaults

Encode a practical starting point for Python, Go, JavaScript, Java, or mixed stacks.

+

Consistency at scale

Teams stop rebuilding the same CI, GitOps, and SRE setup from scratch.

+

Faster onboarding

Developers consume a known pattern instead of reinventing delivery setup.

+
+

Templates are not shortcuts. They are packaged implementation experience.

+
+
+ Repeatable + Adaptable +
+
+ +
+
Platform engineering
+
+

What is platform engineering?

+
    +
  • Creating shared internal capabilities that reduce delivery friction for product teams.
    • +
  • Providing paved paths instead of one-off docs, tribal knowledge, or ticket-driven setup.
    • +
  • Balancing standardisation, self-service, governance, and developer experience.
    • +
+
+
+ Not just infrastructure + Usable internal platforms +
+
+ +
+
IDP
+
+

What is an Internal Developer Platform?

+
+
+

Experience layer

+

An IDP is how developers discover, request, and consume platform capabilities through a usable interface.

+
+
+

DevOps-OS angle

+

Templates become the portable building blocks behind that experience layer — ready to plug into self-service workflows.

+
+
+

Platform engineering builds the capability. IDP makes the capability consumable.

+
+
+ Capability + interface + Self-service with guardrails +
+
+ +
+
Demo framing
+
+

Live demo: from template creation to platform consumption

+
+

Show creation

Create templates for CI/CD, deployment, or stack automation using DevOps-OS.

+

Show consumption

Explain how the same templates can power platform engineering workflows and future IDP experiences.

+
+
    +
  • Keep focus on the workflow story, not every command.
    • +
  • Use the demo to show reuse, consistency, and developer experience.
    • +
+
+
+ Presenter cue slide + No deep walkthrough on screen +
+
+ +
+
Wrap-up
+
+

Key takeaways

+
+

1

Process-first thinking makes DevOps automation more useful.

+

2

Templates help teams standardise without slowing developers down.

+

3

Platform engineering is about delivering reusable internal capabilities.

+

4

DevOps-OS can act as an open source building block behind that journey.

+
+

Thank you — Chennai FOSS 2026.

+
+
+ github.com/cloudengine-labs/devops_os + Use ← →, space, or click buttons +
+
+ +
Slide 1 / 10
+
+ + +
+
+
+ + + + diff --git a/hugo-docs/content/_index.md b/hugo-docs/content/_index.md index ca179c9..8facd0b 100644 --- a/hugo-docs/content/_index.md +++ b/hugo-docs/content/_index.md @@ -91,3 +91,4 @@ python -m cli.devopsos scaffold sre --name my-app --team platform | [Dev Container]({{< relref "/docs/dev-container" >}}) | Configure the dev container | | [AI Integration]({{< relref "/docs/ai-integration" >}}) | MCP server & AI skills | | [CLI Reference]({{< relref "/docs/reference" >}}) | Full CLI options and output paths | +| [Chennai FOSS 2026 Presentation]({{< relref "/docs/talks/chennai-foss-2026" >}}) | GitHub Pages-friendly conference deck with embedded playback | diff --git a/hugo-docs/content/docs/_index.md b/hugo-docs/content/docs/_index.md index 63640e6..d388284 100644 --- a/hugo-docs/content/docs/_index.md +++ b/hugo-docs/content/docs/_index.md @@ -26,3 +26,4 @@ Welcome to the DevOps-OS documentation. Use the sidebar to navigate between sect | [Dev Container]({{< relref "/docs/dev-container" >}}) | Multi-language dev environment setup | | [AI Integration]({{< relref "/docs/ai-integration" >}}) | MCP server for Claude / ChatGPT | | [CLI Reference]({{< relref "/docs/reference" >}}) | Complete command options and output paths | +| [Talks & Presentations]({{< relref "/docs/talks" >}}) | GitHub Pages access to conference-ready DevOps-OS decks | diff --git a/hugo-docs/content/docs/talks/_index.md b/hugo-docs/content/docs/talks/_index.md new file mode 100644 index 0000000..4c76dd0 --- /dev/null +++ b/hugo-docs/content/docs/talks/_index.md @@ -0,0 +1,13 @@ +--- +title: "Talks & Presentations" +weight: 80 +bookCollapseSection: true +--- + +# Talks & Presentations + +Conference-friendly DevOps-OS presentation material published on GitHub Pages. + +| Presentation | Description | +|--------------|-------------| +| [Chennai FOSS 2026]({{< relref "/docs/talks/chennai-foss-2026" >}}) | Process-first DevOps-OS talk deck with direct browser playback | diff --git a/hugo-docs/content/docs/talks/chennai-foss-2026.md b/hugo-docs/content/docs/talks/chennai-foss-2026.md new file mode 100644 index 0000000..67a2527 --- /dev/null +++ b/hugo-docs/content/docs/talks/chennai-foss-2026.md @@ -0,0 +1,22 @@ +--- +title: "Chennai FOSS 2026" +weight: 10 +--- + +# Chennai FOSS 2026 Presentation + +Open the deck directly or use the embedded view below during the session. + +- [Open presentation in a new tab](../../../feature-announcements/chennai-foss-2026/) +- [Open the Talks section]({{< relref "/docs/talks" >}}) + +
+ Presenter note: Use the direct presentation link above for full-screen delivery. The embedded view is intended for quick access from GitHub Pages. +
+ + diff --git a/hugo-docs/static/feature-announcements/chennai-foss-2026/index.html b/hugo-docs/static/feature-announcements/chennai-foss-2026/index.html new file mode 100644 index 0000000..b23af43 --- /dev/null +++ b/hugo-docs/static/feature-announcements/chennai-foss-2026/index.html @@ -0,0 +1,635 @@ + + + + + + DevOps-OS — Chennai FOSS 2026 + + + +
+
+
+
+ +
+
+
Chennai FOSS 2026 · Apr 18
+
+

Simplifying Platform Engineering with DevOps-OS

+

A process-first talk on building improved developer experience workflows with open source building blocks.

+
+ Saravanan Gnanaguru + Founder · CloudEngine Labs + gsaravanen.dev +
+
+
+ cloudenginelabs.io + DevOps-OS open source project +
+
+ +
+
20 minute flow
+
+

What we will cover

+
+

01 · Mindset

Why DevOps starts with process, not tooling.

+

02 · DevOps-OS

Why this project exists and what problem it simplifies.

+

03 · Templates

How repeatable tech stack automation becomes reusable building blocks.

+

04 · Platform view

How templates evolve into platform engineering and IDP adoption.

+
+
+
+ Short talk · lightweight slides · practical framing + Ends with a live demo cue +
+
+ +
+
Process-first understanding
+
+

DevOps is a workflow system before it is a toolchain

+
    +
  • Start with how code moves from idea to production.
    • +
  • Then define approvals, quality gates, deployment flow, and feedback loops.
    • +
  • Only after that should tools and YAML enter the conversation.
    • +
+

When process is clear, automation becomes practical, repeatable, and easier to adopt.

+
+
+ Design the path first + Then automate the path +
+
+ +
+
Why DevOps-OS
+
+

Process > tools

+
+
+

What teams usually do

+

Pick CI/CD, Kubernetes, GitOps, and SRE tools first — then struggle to connect them into one usable workflow.

+
+
+

What DevOps-OS encourages

+

Define the delivery process first — then scaffold the right starting configuration around it.

+
+
+

The project is not just about generating files. It is about making the first layer of platform workflow design simpler.

+
+
+ Less blank-page setup + More workflow clarity +
+
+ +
+
Map process with tools
+
+

Connect each stage to the right building block

+
+
1

Plan

Delivery intent, ownership, release expectations.

+
2

Build & test

GitHub Actions, GitLab CI, Jenkins scaffolds.

+
3

Ship

Kubernetes, deployment config, GitOps handoff.

+
4

Operate

Prometheus, Grafana, SLO, alerting foundations.

+
5

Improve

Template updates, reuse, onboarding, standardisation.

+
+
+
+ Process gives context + Tools implement the context +
+
+ +
+
Templatisation
+
+

Turn stack-specific automation into reusable templates

+
+

Opinionated defaults

Encode a practical starting point for Python, Go, JavaScript, Java, or mixed stacks.

+

Consistency at scale

Teams stop rebuilding the same CI, GitOps, and SRE setup from scratch.

+

Faster onboarding

Developers consume a known pattern instead of reinventing delivery setup.

+
+

Templates are not shortcuts. They are packaged implementation experience.

+
+
+ Repeatable + Adaptable +
+
+ +
+
Platform engineering
+
+

What is platform engineering?

+
    +
  • Creating shared internal capabilities that reduce delivery friction for product teams.
    • +
  • Providing paved paths instead of one-off docs, tribal knowledge, or ticket-driven setup.
    • +
  • Balancing standardisation, self-service, governance, and developer experience.
    • +
+
+
+ Not just infrastructure + Usable internal platforms +
+
+ +
+
IDP
+
+

What is an Internal Developer Platform?

+
+
+

Experience layer

+

An IDP is how developers discover, request, and consume platform capabilities through a usable interface.

+
+
+

DevOps-OS angle

+

Templates become the portable building blocks behind that experience layer — ready to plug into self-service workflows.

+
+
+

Platform engineering builds the capability. IDP makes the capability consumable.

+
+
+ Capability + interface + Self-service with guardrails +
+
+ +
+
Demo framing
+
+

Live demo: from template creation to platform consumption

+
+

Show creation

Create templates for CI/CD, deployment, or stack automation using DevOps-OS.

+

Show consumption

Explain how the same templates can power platform engineering workflows and future IDP experiences.

+
+
    +
  • Keep focus on the workflow story, not every command.
    • +
  • Use the demo to show reuse, consistency, and developer experience.
    • +
+
+
+ Presenter cue slide + No deep walkthrough on screen +
+
+ +
+
Wrap-up
+
+

Key takeaways

+
+

1

Process-first thinking makes DevOps automation more useful.

+

2

Templates help teams standardise without slowing developers down.

+

3

Platform engineering is about delivering reusable internal capabilities.

+

4

DevOps-OS can act as an open source building block behind that journey.

+
+

Thank you — Chennai FOSS 2026.

+
+
+ github.com/cloudengine-labs/devops_os + Use ← →, space, or click buttons +
+
+ +
Slide 1 / 10
+
+ + +
+
+
+ + + +