Static Hosting Support using DocC

It is a little hard to say exactly what might be going wrong given this description, but it is a good sign if you can see that HTML files are emitted in the output path after running that command. There is no "root" page for DocC output at the moment, so it might be possible that you just didn't visit an appropriate URL path (example: /documentation/frameworkname). Although if you are truly seeing blank pages with no content at all, it may be worth checking to see if there are any JavaScript or other related errors being reported by your web browser.

One other potential issue is that maybe the version of Xcode you used to create the archive does not contain a recent version of DocC needed to support static hosting. To address that, you could update to the latest beta version of Xcode which would have this newer functionality and then use that to build your documentation for exporting the archive before running the process-archive command.

Also, you may need to also pass the --hosting-base-path argument if you intend to host the static site on a URL that includes a base path, like some GitHub Pages URLs may require (for example you may need to use something like --hosting-base-path /myrepo for a URL that needs to support something like /myrepo/documentation/frameworkname).

Hopefully some part of this information helps with your specific situation! You may also want to check out some recent related documentation for the DocC Swift Package Manager plugin at https://apple.github.io/swift-docc-plugin/documentation/swiftdoccplugin/publishing-to-github-pages

It's likely the base path is misconfigured. The resources all fail to load from the html file because the process-archive command prefixes the base path you pass it with a forward slash.

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.