Deployment

Deploy your site or application that uses EthioWDS by building your project and publishing the output to your hosting environment. The design system is static assets (styles and optional scripts), so it works with common hosting and deployment setups.

Before you deploy

  • EthioWDS is installed and its stylesheet is included (see Installation).
  • Your project builds successfully and looks correct locally at different screen sizes.
  • You’ve run any tests or checks you use (see Testing).

Build your project

Run your project’s build command so it produces the files you will deploy (e.g. HTML, CSS, and scripts). The build process should bundle or copy the EthioWDS stylesheet and any assets you use. Ensure the paths to the design system files are correct in the built output so they load in production.

Static vs dynamic sites

Static sites — If your site is built as static HTML, CSS, and scripts, upload the build output to your host (e.g. via FTP, Git, or a hosting dashboard). Many hosts support static sites and optional redirects or headers for SPA-style routing.

Dynamic or server-rendered sites — If your project uses a server or framework, deploy using that project’s recommended process (e.g. build step, then run the server or deploy to a platform). The design system remains static assets referenced by your templates or layout.

Check after deployment

  • Open the live site and confirm styles load (no missing or broken CSS).
  • Test key pages and components on desktop and mobile.
  • Verify links, forms, and navigation work on the live URL.

See also

Installation — How to add EthioWDS to your project. Testing — What to test before and after deployment.