Skip to content

Conversation

@gkLeo
Copy link
Contributor

@gkLeo gkLeo commented Dec 9, 2024

Description / Motivation

Update the following pages to align with the restructured XM Cloud Foundation Head.
/learn/getting-started/xm-cloud/tutorials/create-a-site
/learn/accelerate/xm-cloud/appendix-ii/example-code/xmcloud-build-json
/learn/accelerate/xm-cloud/pre-development/developer-considerations/dev-workflow-codespaces
/learn/accelerate/xm-cloud/pre-development/project-architecture/rate-limits-and-caching

How Has This Been Tested?

Local.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update (non-breaking change; modified files are limited to the /data directory or other markdown files)

Checklist:

  • I have read the Contributing guide.
  • My code/comments/docs fully adhere to the Code of Conduct.
  • My change is a code change.
  • My change is a documentation change and there are NO other updates required.
  • My change has new or updated images which are stored in the /public/images folder that need to be migrated to Sitecore DAM

@vercel
Copy link

vercel bot commented Dec 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
developer-portal ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 9, 2024 9:02am

@vercel
Copy link

vercel bot commented Dec 9, 2024

@gkLeo is attempting to deploy a commit to the Sitecore Technical Marketing Team on Vercel.

A member of the Team first needs to authorize it.

@gkLeo gkLeo changed the title Update contents to align with the restructured XM Cloud Foundation Head Updated contents to align with the restructured XM Cloud Foundation Head Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant