Azure DevOps · Frontend Capsule
A static site you can ship without a build step.
Plain HTML, CSS, and JavaScript at the repo root. Connect this repository to a Code Capsules Frontend Capsule, leave the build command blank, and go live on every push.
What you get
Everything a Frontend Capsule needs
This sample is intentionally small so you can confirm Azure DevOps source, static hosting, and custom domains without extra setup.
No build pipeline
index.html, styles.css, and
app.js sit at the repository root. Leave Build
Command and Static Content Folder Path empty.
Responsive layout
Semantic markup, CSS custom properties, and a mobile navigation pattern you can reuse or strip back for your own site.
Tiny interactivity
Vanilla JavaScript drives the deploy log, mobile menu, and fade-in sections. No frameworks, bundlers, or package managers.
How it deploys
From Azure Repos to a live URL
-
Connect the repo
Create a Frontend Capsule and grant Code Capsules access to this Azure DevOps repository.
-
Skip the build
Leave the build command and output folder blank. The capsule serves these files as-is.
-
Push to main
Each commit on the tracked branch triggers a new deploy. Open the capsule URL to confirm the site is live.
FAQ
Common questions
How do I preview this locally?
Open index.html in a browser, or serve the folder
with npx serve / python3 -m http.server
so relative assets load cleanly.
Can I add a framework later?
Yes. Replace these files with a React, Vue, or Angular app and set a build command plus output directory on the capsule. This sample stays static on purpose.
Where should assets live?
Keep HTML, CSS, JavaScript, and images in the same directory Code Capsules treats as the static root — here, the repository root.
Ready to deploy your own copy?
This page is a static HTML site meant for a Code Capsules Frontend Capsule. Point the capsule at this Azure DevOps repo and ship it.
Open Code Capsules