How cloudevents/cloudevents-web works
Project type and purpose
• This is a static documentation/blog website (“cloudevents-web”) built with Hugo (a Go-based Static Site Generator) and styled with SASS.
• Its sole purpose is to transform Markdown content, YAML data, and templates into a static HTML/CSS/JS site, then deploy it via Netlify.
File structure
• Top-level config:
• config.toml – Hugo site configuration
• netlify.toml – Netlify build & deploy settings
• package.json & Makefile – local tooling (npm scripts, Hugo commands)
• Content & data:
• content/ – Markdown files for blog and pages
• data/ – YAML files (integrations, parameters, etc.) per locale
• archetypes/ – default front-matter templates
• Templates & layouts:
• layouts/ – Hugo templates (baseof.html, list, single) and partials (navbar, footer, blog widgets, home sections)
• Assets & static files:
• assets/ – SASS source (assets/sass/style.sass) compiled by Hugo’s Pipes or npm
• static/ – static images, logos, and other unprocessed files
• Versioning & modules:
• .gitmodules – submodules (e.g., shared components)
• .gitignore, .editorconfig, LICENSE – ancillary files
README
• Confirms Hugo + npm + Netlify workflow (“hugo serve”, Netlify badge)
• No backend or runtime service; purely a build → deploy → CDN → browser flow