🌐 US-Proxy
class="logged-out env-production page-responsive" style="word-wrap: break-word;" >
Skip to content

feat(site/src/pages/TemplateBuilder): prioritize template builder module display order - #26835

Merged
jeremyruppel merged 1 commit into
mainfrom
jeremy/devex-560-sort-modules-according-to-atif-alis-list
Jun 29, 2026
Merged

feat(site/src/pages/TemplateBuilder): prioritize template builder module display order#26835
jeremyruppel merged 1 commit into
mainfrom
jeremy/devex-560-sort-modules-according-to-atif-alis-list

Conversation

@jeremyruppel

Copy link
Copy Markdown
Contributor

Adds a curated priority ordering for modules in the template builder module picker. Modules in the priority list appear first in the specified order; unlisted modules appear after in their original order.

Changes

  • Added MODULE_PRIORITY constant in ModuleSelectStep.tsx with the preferred display order
  • Added sortByPriority() helper to sort modules against the priority list
  • Not-yet-imported module IDs (codex, antigravity, kasmvnc) are included but commented out
  • Both the module grid and category tabs respect the new ordering
  • Search results still use fuzzy relevance ordering

Generated by Coder Agents on behalf of @jeremyruppel

@linear-code

linear-code Bot commented Jun 29, 2026

Copy link
Copy Markdown

DEVEX-560

@jeremyruppel jeremyruppel changed the title feat(site): prioritize template builder module display order feat(site/src/pages/TemplateBuilder): prioritize template builder module display order Jun 29, 2026
Comment on lines +75 to +92
const MODULE_PRIORITY: readonly string[] = [
"claude-code",
// "codex",
"cursor",
"vscode-desktop",
"code-server",
"jetbrains",
"vscode-web",
"zed",
// "antigravity",
"windsurf",
"git-clone",
"dotfiles",
"git-config",
"personalize",
"filebrowser",
// "kasmvnc",
];

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rather than trying to make a backend concept for this, I'm opting to keep this list on the frontend because it's used for display/sorting purposes only. the Simplest Thing That Could Possibly Work™

@jeremyruppel
jeremyruppel requested a review from matifali June 29, 2026 20:52
// in this order. Unlisted modules appear after, in their original order.
const MODULE_PRIORITY: readonly string[] = [
"claude-code",
// "codex",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this commented?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not-yet-imported module IDs (codex, antigravity, kasmvnc) are included but commented out

I see that, but is there a plan for when these will be imported?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the commented modules haven't been imported into the template builder catalog yet. it's trivial to import them though (we have a script), so say the word and I'll whip up a backend PR for the commented out ones

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please. I think these are worth showing in the builder.

Comment thread site/src/pages/TemplateBuilder/ModuleSelectStep.tsx
Comment thread site/src/pages/TemplateBuilder/ModuleSelectStep.tsx
@jeremyruppel
jeremyruppel merged commit 9f7caa0 into main Jun 29, 2026
51 of 53 checks passed
@jeremyruppel
jeremyruppel deleted the jeremy/devex-560-sort-modules-according-to-atif-alis-list branch June 29, 2026 21:04
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 29, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants