Migrate hubstry.dev to Hubstry Deep Tech site and retain current homepage as legacy - #10
Conversation
…shot Co-authored-by: marcabru-tech <176715578+marcabru-tech@users.noreply.github.com>
PR Summary by QodoMigrate hubstry.dev to Hubstry Deep Tech site (keep legacy homepage)
AI Description
Diagram
High-Level Assessment
Files changed (4)
|
There was a problem hiding this comment.
Pull request overview
Migrates the hubstry.dev homepage to a bundled static app (JS/CSS) sourced from the Hubstry Deep Tech site, while preserving the previous homepage as a local legacy snapshot.
Changes:
- Replaces the root
index.htmlwith a minimal app shell that mounts into#rootand loads the bundled assets from/assets. - Adds
index-legacy-local.htmlcontaining the previous homepage content as a snapshot. - Adds the bundled Tailwind-based stylesheet under
assets/.
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| index.html | Swaps the previous static homepage for an app shell that loads the migrated site bundle from /assets. |
| index-legacy-local.html | Preserves the prior homepage as a legacy snapshot file. |
| assets/index-DBdy33V5.css | Adds the bundled/minified stylesheet used by the migrated site. |
Files not reviewed (1)
- assets/index-DBdy33V5.css: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| <body class="bg-black text-white font-['Ruda',sans-serif] antialiased selection:bg-[#00ffff] selection:text-black"> | ||
| <div id="root"></div> |
|
|
||
| <!DOCTYPE html> |
| .cta-links{gap:18px} | ||
| } | ||
| </style> | ||
| <base target="_blank"> |
Code Review by Qodo
1. Legacy snapshot deployed
|
| <head> | ||
| <meta charset="UTF-8"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>Hubstry — Operating Deep Tech Venture Builder</title> |
There was a problem hiding this comment.
1. Legacy snapshot deployed 🐞 Bug ⚙ Maintainability
The PR adds index-legacy-local.html at the repository root without any noindex/canonical guard, making it likely to be published as a second public page (e.g., /index-legacy-local.html) alongside the new SPA homepage. This can expose stale/duplicate content and outdated links under the production domain.
Agent Prompt
## Issue description
`index-legacy-local.html` was added at the site root and appears intended as a local-only snapshot, but in a static-root deployment it will be served publicly and can be indexed.
## Issue Context
This repository is structured like a static site root (has `index.html`, `/assets/*`, and a `CNAME` for `hubstry.dev`). Any extra root-level HTML file is typically reachable as a public URL.
## Fix Focus Areas
- index-legacy-local.html[1-20]
- index-legacy-local.html[270-280]
### What to change
Choose one (preferred first):
1) **Exclude from production publishing**: move the snapshot out of the published root (e.g., to a non-published location used only for local reference), OR
2) If it must remain reachable: add in `<head>`:
- `<meta name="robots" content="noindex,nofollow">`
- optionally a canonical to the main homepage: `<link rel="canonical" href="https://hubstry.dev/">`
- and consider adding a visible banner "Legacy (not current)" to prevent user confusion.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Este PR substitui o conteúdo atual publicado neste repositório pelo site da outra conta (
guilherme-machado-ceo/hubstry-deep-tech-site) para quehubstry.deventregue a mesma experiência. O site anterior foi preservado localmente como versão de legado.Origem do conteúdo
index.htmlpublicado na branchgh-pagesdo repositório de origem.assets/index-Bdy9wbPf.jseassets/index-DBdy33V5.css) para manter deploy independente.Ajuste para domínio raiz (
hubstry.dev)Legado preservado
index-legacy-local.html, mantendo o conteúdo histórico disponível sem bloquear a migração.