It sounds like you’ve successfully transformed your .docarchive for static hosting using the swift-docc tool, but you’re encountering issues when hosting the output files. Here are a few suggestions to help resolve the problem: 1. Base URL Configuration: Ensure the base URL for your documentation matches the deployment path. For example, if hosting on GitHub Pages at username.github.io/project, use the --hosting-base-path option during the swift-docc command: swift run docc process-archive transform-for-static-hosting <path/to/docarchive> --output-path <destination_path> --hosting-base-path /project This adjusts links and assets for deployment under a subdirectory. 2. Path and Asset Issues: Double-check that all files, including CSS, JS, and other assets, are correctly uploaded and accessible. Use browser developer tools to identify any 404 errors or resource loading issues. 3. Hosting Platform Configurations: Some platforms require special configurations for routing or serving index.html. Make sure your hosting environment is properly set up for static files. 4. Test Locally: Before deploying, use a local static server (e.g., python -m http.server) to confirm everything works as expected. Alternatively, consider using a dedicated static hosting service like StaticHost to simplify the deployment process. It’s designed to host static sites with minimal configuration, making it an excellent option for hosting documentation or similar content.