Repository navigation
docs(hub): define backend code conventions - #102
Merged
Merged
Conversation
Copilot
AI
changed the title
docs(hub): define the TypeScript rebuild architecture
docs(hub): document repositories, integrations, utilities, and domains
Oct 23, 2026
Co-authored-by: Nishiki Liu <hello@nshki.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot
AI
changed the title
docs(hub): document repositories, integrations, utilities, and domains
docs(hub): define backend code conventions
Oct 23, 2026
Copilot
AI
force-pushed
the
copilot/hub-new-conventions
branch
from
October 23, 2026 18:54
bbdf1e3 to
3b51f1a
Compare
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
weastler
approved these changes
Oct 23, 2026
nshki
approved these changes
Oct 23, 2026
nshki
added a commit
that referenced
this pull request
Oct 23, 2026
<!-- Use a conventional commit-style title, such as "fix(hub): retain prototype history". --> ## Why <!-- Explain the problem and why this change matters in a short, plain-English paragraph. Link the issue when applicable. --> Give the team a clean starting point for rebuilding Hub without porting product features yet. This follows #102 in the stack for #101. The stack builds on `build/hub/new`, not `main`. ## What changes <!-- Describe what becomes different for a first-time reader. Explain necessary terms. Include accurate Mermaid diagrams when they clarify the proposal, using before/after diagrams when helpful. Add screenshots for meaningful UI changes. --> <!-- Omit validation sections, checklists, and routine test/CI summaries such as "CI is green" or "tests passed". Mention only known verification gaps that affect the change, not disclaimers about drafting this description. --> <!-- For UI changes, prune obsolete and duplicate stories in the affected catalogues as part of the change. Explain removed UI or consolidated coverage where needed; see hub/docs/storybook.md#ui-changes-and-pull-request-evidence. --> Replace Rails and Superglue with a TypeScript Express API and React + Vite app. The API has a health endpoint; the frontend shows the existing logo and theme. Database, sign-in, and deployment choices remain open. Keep the frontend components, styles, Storybook examples, and shared canvas and Controls code for reuse. Remove the old backend, database files, deployment setup, and live-update connection. The canvas keeps its periodic refresh. Keep the presentation stories, move template examples out of database seeds, and remove the deleted view from the component-usage example. Rewrite shared Ruby checks in TypeScript with function directories and colocated Vitest tests. Update CI, local commands, and documentation for the new setup. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Nishiki Liu <hello@nshki.com>
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
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.
Why
The team needs shared code conventions before rebuilding Hub. This is the first PR for #101. It targets build/hub/new, not main.
What changes
Document repositories for database calls, integrations for API and SDK calls, utilities for general functions, and domains for business logic. Include the directory examples and rules for which layers may import others.
This PR changes only those conventions. The next PR covers the chosen tools, frontend setup, and removal of the old backend.