- Add utility function for cascading hideBranding logic
- Update all getServerSideProps files to check organization hideBranding as fallback
- Ensure team queries include parent hideBranding data
- Fix hideBranding not working for organization members and teams
Fixes the issue where organization-level branding settings were not
being applied to user and team event pages when the direct entity
didn't have hideBranding enabled.
Co-authored-by: Hariom Balhara <hariombalhara@gmail.com>
* Remove BookerSeo from instant-meeting-view
* remove route from pages router
* make eventData passed from getServerSideProps
* refactor route in app router and move it outside of /future
* update env vars
* update middleware
* remove pages router and move pages to /app
* move to /team
* update imports
* fix
* remove pages router and move org pages to /app
* wip
* fix orgSlug/user pages
* fix orgSlug/user/type pages
* remove generateMetadata from embed pages
* fix
* remove pages router for /user pages
* generateMetadata is not needed in embed pages
* remove future/org
* no layout in [user] page
* simplify
* fix
* fix OG image for [user]
* fix OG images for org/user and team/slug
* fix OG images for booking page
* fix all metadata
* use isBrandingHidden
* remove BookerSeo and its usages
* rename excludeAppNameFromTitle -> hideBranding
* remove logic for meeting type in HeadSeo
* remove BookerSeo instances from team-view and users-public-view
* create generateMeetingMetadata util and use it to reduce duplicate code
* remove BookerSeo imports
* fix spacing
* remove constructMeetingImage mock from head-seo.test
* fetch avatarUrl using user id for user page metadata
* fix test
* remove unused test cases
* index and follow must be true by default
* invert noindex/nofollow flags
* remove HeadSeo for already migrated pages and refactor prepareMetadata
* fix organization-settings.e2e.ts
* fix order
* enable parallel test execution for dynamic-booking e2e test
* fix
* + could be %2B in app router
* refactor handling logic for embeds in app router
* fix isEmbed
* fix embed-core
* remove dead code
* move embed pages back to /future
* add back embed pages in pages router
* revert some changes
* fix import type checks
* simplify
* fix
* feat: Implement generateBookingPageMetadata function for improved SEO and metadata handling across user and event pages (#18440)
- Added a new utility function `generateBookingPageMetadata` to streamline the generation of metadata for booking and user profile pages.
- Updated multiple page components to utilize the new function, enhancing SEO indexing and metadata consistency.
- Removed redundant code related to previous metadata generation methods, improving code clarity and maintainability.
* fix dirs
* Pr-review-fixes-app-router-team-pages (#18450)
* Remove unnecessary getPublicEvent call
* Remove unused variable
* Fix 404 for team page (#18451)
* Remove console log
---------
Co-authored-by: Hariom Balhara <hariombalhara@gmail.com>
## What does this PR do?
<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
Fixes # (issue)
<!-- Please provide a loom video for visual changes to speed up reviews
Loom Video: https://www.loom.com/
-->
## Requirement/Documentation
<!-- Please provide all documents that are important to understand the reason of that PR. -->
- If there is a requirement document, please, share it here.
- If there is ab UI/UX design document, please, share it here.
## Type of change
<!-- Please delete bullets that are not relevant. -->
- Bug fix (non-breaking change which fixes an issue)
- Chore (refactoring code, technical debt, workflow improvements)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Tests (Unit/Integration/E2E or any other test)
- This change requires a documentation update
## How should this be tested?
<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Write details that help to start the tests -->
- Are there environment variables that should be set?
- What are the minimal test data to have?
- What is expected (happy path) to have (input and output)?
- Any other important info that could help to test that PR
## Mandatory Tasks
- [ ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.
## Checklist
<!-- Remove bullet points below that don't apply to you -->
- I haven't read the [contributing guide](https://github.com/calcom/cal.com/blob/main/CONTRIBUTING.md)
- My code doesn't follow the style guidelines of this project
- I haven't commented my code, particularly in hard-to-understand areas
- I haven't checked if my PR needs changes to the documentation
- I haven't checked if my changes generate no new warnings
- I haven't added tests that prove my fix is effective or that my feature works
- I haven't checked if new and existing unit tests pass locally with my changes
Alex van Andel