sitecore / xm-cloud-introduction Goto Github PK

The SUGCON EU site (https://sugcon-eu.vercel.app/) uses a very long piece of text for the H1 tag. For SEO purposes, H1 tags should be very descriptive of the content such that people searching for a page will hit that particular page based on the H1 content.

The current content is likely H2 type of content, and a proper H1 which is more reflective of the site should be used.

NOTE: This may mean changing the code or templates as well to support outputting the 'description' content in a styled way without using the Title field, which should be output for things like browser title and the H1.

We need to read the output of the dotnet sitecore cloud deployment create command to see whether the response was successful.

This will stop the intermittent false positives we've been seeing.

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2735638572

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2701651778

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

I was able to select a future date for contributions. Not sure if that is allowed or not.

Currently we're using a custom Development.ps1 script to handle reload of the rendering host when code changes in debug mode.

This should be removed in favour of the OOTB Hot Reload functionality now provided by MS, details:
https://devblogs.microsoft.com/dotnet/introducing-net-hot-reload/

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2702354478

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

I would recommend that the Description field be much wider and the Link field be shortened with some friendly display text.

It looks like there is a button here without any text? I looked at the content item but couldn't see any unpopulated fields?

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2702229164

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

Document as blog or videos
Check if we showcase another technology stack (check with Andy about preferences)

When using a mobile device (or even a small screen) header component is not visible making it not possible to log in.

Anyway to wrap the wording?

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2702354480

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

Currently we're just running a .NET Core 3.1 application using the .NET6 runtime. We should upgrade the rendering host to leverage the new functionality released with .NET 6

Some examples:
https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60-samples?view=aspnetcore-6.0
https://docs.microsoft.com/en-us/aspnet/core/migration/31-to-60?view=aspnetcore-6.0&tabs=visual-studio

Need community contributions guide here in the project

We need to define how we are going to take contributions from the community in this repository.

Once defined a Contributions guidelines needs to be added to this repository, stating what has been defined.

Currently the MVP Site robots.txt is set to deny all crawlers while we're in development.

When live this needs to be reverted to allow crawlers to access the site.

Currently all editing is in admin mode. There are no new versions created and no workflow on the changes, so there is also no history of changes made to content.

People who login should have a user level, not admin, and be able to go through standard workflow for versions to be created.

Something we have setup for the Developer Portal is to have the branches automatically deleted when we merge to main, and then the option to restore if we want (in an error case, such as what recently happened with the Favicon branch)

Can we add that configuration into this repo as well to make it less likely someone forgets to remove their PR branch?

Update the GitHub Actions to implement reusable workflows, removing duplication currently used in the workflow definitions.

I can access the /selections page ok, but when I click 'My current applicationthen the/selections/apply` page gives me an error and doesn't display the form

We need to move the existing Serialisation items from the MVP repository into this one. This will enable us to migrate the content into XM Cloud, to enable testing of functionality based on those items.

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2701955145

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

The Experience Editor doesn't work for the MVP site when running in Full Local Development mode.

Enable field editor for that component. Note that this has to be done in a way that is compatible with Pages, not just Experience Editor.

Styling is inconsistent with some in XM, some in scss, and some in bootstrap. What would we recommend what do we want to showcase?

Currently we're just running a .NET Core 3.1 application using the .NET6 runtime. We should upgrade the rendering host to leverage the new functionality released with .NET 6

Some examples:
https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60-samples?view=aspnetcore-6.0
https://docs.microsoft.com/en-us/aspnet/core/migration/31-to-60?view=aspnetcore-6.0&tabs=visual-studio

The Sitemap for the MVP site needs creating.

This should be built to leverage the GraphQLSitemapService provided by the LayoutService as leveraged by the SUGCON sites.

The Sitemap in XMC is autogenerated in to the media library. this ticket has two tasks

• Figure out how to hook into the SXA Headless Sitemap Generation functionality - even though the MVP site isn't built with SXA Headless
• Update the MVP head to leverage the generated Sitemap XML that is served from Edge.

Workflow is pending manual review.
URL: https://github.com/Sitecore/XM-Cloud-Introduction/actions/runs/2701903393

Required approvers: [robearlam]

Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel.

Reproduction steps:

1. Launch Pages on SUGCON EU production XM Cloud environment.
2. Select the "Fixed Width Container" below the BackgroundImage component/banner
3. Click on the down arrow to move it down one position
4. Click on "Preview" to verify it displays correctly (this works and displays the new layout order)
5. Click "Publish item" and wait for publishing to complete.
6. Refresh the Vercel site (https://sugcon-eu.vercel.app/) to trigger an ISR check.
7. Wait for a while, then refresh the page again to see the new page layout.

It does not display the new layout and keeps the old layout.

NOTE: I did test the same process by changing content, and if the content was changed the page did update on Vercel. It seems that if data is the same, but layout changed, ISR is not determining a change was made (or possibly the change is not getting to Edge?) Either way, something does not seem to be working

When trying to access Application page (https://mvp-production.azurewebsites.net/Application) from my Android device (Moto G G5 / Android 11) via Chrome, I am getting 404 Page not found error. Therefore I cannot see login button on top of the page.

Add social icons to the SUGCON sites footer (twitter, youtube, github etc)

Need favicons setup for SUGCON EU and ANZ

I'm getting an error on the Objectives step

From the XM Cloud Dashboard, launch the PowerShell Reports application option.

"No report data available.
Is the remoting service enabled?
Are the reporting modules installed and enabled?"

I'm not sure if this is a product issue or a configuration issue.

Saw markup at the top of the contributions page.

When running in 'Edge Mode' we're only running containers for the Hosts and Traefik, so it would be really nice to change over to run in Linux Container mode as they're much more lightweight.

We need styled 404 and 500 pages for the MVP site.

As it's SSR the layout can't be controlled via CMS unless the connection is down, we want to still be able to serve error pages.

Wondering if there is a way to default the country to the last one used or based on the location.