Indeed, The mapping is missing.
Create the Mappings and then publish and test, it should work:
Add-TtmMapping -ID Mapping1 -CmEnvironmentId Tridioncm_localhost -PublicationID tcm:0-5-1 -WebApplicationId Website1_RootWebApp -RelativeUrl /
Note:
CmEnvironmentId, PublicationId, and WebApplicationId should be your environment-specific values
For PublicationId - Note down your example website publication Id.
For CmEnvironmentId - run this Powershell cmd Get-TtmCmEnvironment and note down the Id.
For WebApplicationId - first, run this Powershell cmd Get-TtmWebsite identify the base URL and cd environment and note down the Id, and then run the Get-TtmWebApplication -WebsiteId Website1, note down the Id, once you know all the parameters values of the Add-TtmMapping then proceed to create the mapping and publish and test.
The example website configuration should look like this for your reference, but the values and Ids are differs based on customer-specific values.
PS C:\Users\vagrant> Get-TtmCmEnvironment
CoreServiceRootUrl : net.tcp://localhost:2660
WebsiteRootUrl : http://localhost:80
CoreServiceCredentials : "AuthenticationType":"Windows", "UserName":"VAGRANT-2016\MTSUser", "Password":"********"
Id : Tridioncm_localhost
ExtensionProperties : {}
PS C:\Users\vagrant> Get-TtmWebsite
BaseUrls : {http://localhost:8852}
CdEnvironmentId : CdEnvironment1
EnvironmentPurpose : Staging
CdEnvironment :
ScopedRepositoryKeys : {DxaSiteType, DxaExampleSite}
Id : Website1
ExtensionProperties : {}
PS C:\Users\vagrant> Get-TtmWebApplication
ContextUrl : /
WebsiteId : Website1
EnvironmentPurpose : Staging
CdEnvironment :
ScopedRepositoryKeys : {DxaSiteType, DxaExampleSite}
Id : Website1_RootWebApp
ExtensionProperties : {}
PS C:\Users\vagrant> Get-TtmMapping
CmEnvironmentId : Tridioncm_localhost
PublicationId : tcm:0-5-1
EnvironmentPurpose : Staging
WebApplicationId : Website1_RootWebApp
RelativeUrl : /
PrimaryMappedUrl : http://localhost:8852/
IsOffline : False
CdEnvironment :
Id : Mapping1
ExtensionProperties : {}
I hope it helps.