CMS-45730 Add alloy template #139
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TRomesh
had a problem deploying
to
Vercel preview environment
GitHub Actions
Failure
TRomesh
force-pushed
the
feature/CMS-45730-add-alloy-template
branch
from
892c021 to
0277cd3
Compare
TRomesh
force-pushed
the
feature/CMS-45730-add-alloy-template
branch
from
0277cd3 to
1458a0a
Compare
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new alloy-template to the templates directory, providing a Next.js-based starter template for Optimizely CMS projects. The template includes pre-configured components, TypeScript configuration, and Tailwind CSS styling.
- Adds a complete Next.js 15.5.4 template with React 19.1.0
- Includes various reusable CMS components (Teaser, Notice, Contact, etc.)
- Configures TypeScript, Tailwind CSS v4, and PostCSS
- Updates workspace configuration to include the templates directory
Reviewed Changes
Copilot reviewed 28 out of 36 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| templates/alloy-template/package.json | Defines project dependencies including Next.js, React 19, and Tailwind CSS v4 |
| templates/alloy-template/tsconfig.json | TypeScript configuration with Next.js and bundler module resolution |
| templates/alloy-template/src/components/*.tsx | Component files for Teaser, Notice, Contact, Editorial, Article, and other CMS content types |
| templates/alloy-template/src/components/Start.tsx | Start page component with composition support |
| templates/alloy-template/src/app/*.tsx | Next.js app router pages including layout, dynamic routes, and preview |
| templates/alloy-template/next.config.ts | Next.js configuration for remote image patterns |
| pnpm-workspace.yaml | Updated to include templates directory in workspace |
| pnpm-lock.yaml | Lock file updated with new template dependencies |
Files not reviewed (2)
- pnpm-lock.yaml: Language not supported
- templates/alloy-template/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
TRomesh
force-pushed
the
feature/CMS-45730-add-alloy-template
branch
from
1458a0a to
baf3440
Compare
|
|
Contributor
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 28 out of 36 changed files in this pull request and generated 5 comments.
Files not reviewed (2)
- pnpm-lock.yaml: Language not supported
- templates/alloy-template/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
TRomesh
force-pushed
the
feature/CMS-45730-add-alloy-template
branch
from
baf3440 to
7b71628
Compare
…out and content handling; enhance Teaser component with link wrapping functionality.
…mple and update page.tsx to use the new variable
…Header and update layout structure
TRomesh
force-pushed
the
feature/CMS-45730-add-alloy-template
branch
from
7b71628 to
b191041
Compare
TRomesh
force-pushed
the
feature/CMS-45730-add-alloy-template
branch
from
2e260c1 to
ccbb46b
Compare
exacs
reviewed
Dec 2, 2025
Contributor
exacs
left a comment
exacs
left a comment
There was a problem hiding this comment.
Overall the code looks good to me!
|
|
||
| const nextConfig: NextConfig = { | ||
| images: { | ||
| domains: ['app-opinjssdk1sob7t001.cms.optimizely.com'], |
Contributor
There was a problem hiding this comment.
Shouldn't this be an env variable?
Comment on lines
+11
to
+13
| type: 'url', | ||
| displayName: 'Button Link', | ||
| group: 'Information', |
Contributor
There was a problem hiding this comment.
Maybe this property should be required?
Comment on lines
+18
to
+48
| const allLinks = await Promise.all([ | ||
| client.getItems('/en/'), | ||
| client.getItems('/en/about-us'), | ||
| client.getItems('/en/about-us/news-events'), | ||
| ]); | ||
|
|
||
| // Flatten the array of arrays and map to FooterLink format | ||
| const footerLinks = allLinks.flat().map((ancestor: any) => ({ | ||
| key: ancestor._metadata?.key, | ||
| label: ancestor._metadata?.displayName, | ||
| href: ancestor._metadata?.url?.hierarchical, | ||
| })); | ||
|
|
||
| // Group links by category based on URL patterns | ||
| const categorizedLinks = footerLinks.reduce<{ | ||
| products: FooterLink[]; | ||
| company: FooterLink[]; | ||
| news: FooterLink[]; | ||
| }>( | ||
| (acc, link) => { | ||
| if (link.href?.match(/\/about-us\/news-events\/.+/)) { | ||
| acc.news.push({ label: link.label, href: link.href }); | ||
| } else if (link.href?.includes('/about-us')) { | ||
| acc.company.push({ label: link.label, href: link.href }); | ||
| } else if (link.href) { | ||
| acc.products.push({ label: link.label, href: link.href }); | ||
| } | ||
| return acc; | ||
| }, | ||
| { products: [], company: [], news: [] } | ||
| ); |
Contributor
There was a problem hiding this comment.
I don't understand why you need to flatten the links and re-categorize them.
Why not using the response from getItems directly?
newsLinks = await client.getItems("/en/about-us/news/events")
//etc.
exacs
reviewed
Dec 2, 2025
| # From here, all environmental variables are optional | ||
| # | ||
| # Endpoint of GraphQL. Use this variable if you use a non-production instance or a different version | ||
| # OPTIMIZELY_GRAPH_URL=https://cg.optimizely.com/content/v2 |
Contributor
There was a problem hiding this comment.
This is called "OPTIMIZELY_GRAPH_GATEWAY" everywhere else: https://github.com/episerver/content-js-sdk/blob/main/samples/nextjs-template/.env.in
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This template is 75% complete. The remaining features can be implemented once the tasks in CMS-46339 are resolved.