Skip to content

Migrate hubstry.dev to Hubstry Deep Tech site and retain current homepage as legacy - #10

Merged
marcabru-tech merged 1 commit into
mainfrom
copilot/hubstry-deep-tech-site
Aug 10, 2026
Merged

Migrate hubstry.dev to Hubstry Deep Tech site and retain current homepage as legacy#10
marcabru-tech merged 1 commit into
mainfrom
copilot/hubstry-deep-tech-site

Conversation

Copilot AI commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Este PR substitui o conteúdo atual publicado neste repositório pelo site da outra conta (guilherme-machado-ceo/hubstry-deep-tech-site) para que hubstry.dev entregue a mesma experiência. O site anterior foi preservado localmente como versão de legado.

  • Origem do conteúdo

    • Homepage atualizada com o index.html publicado na branch gh-pages do repositório de origem.
    • Bundle estático incorporado neste repositório (assets/index-Bdy9wbPf.js e assets/index-DBdy33V5.css) para manter deploy independente.
  • Ajuste para domínio raiz (hubstry.dev)

    • Referências de assets foram reescritas de base path de projeto para root path, evitando resolução incorreta em domínio customizado.
    <!-- antes -->
    <script type="module" src="/hubstry-deep-tech-site/assets/index-Bdy9wbPf.js"></script>
    <link rel="stylesheet" href="/hubstry-deep-tech-site/assets/index-DBdy33V5.css">
    
    <!-- depois -->
    <script type="module" src="/assets/index-Bdy9wbPf.js"></script>
    <link rel="stylesheet" href="/assets/index-DBdy33V5.css">
  • Legado preservado

    • A homepage anterior foi salva como snapshot em index-legacy-local.html, mantendo o conteúdo histórico disponível sem bloquear a migração.

…shot

Co-authored-by: marcabru-tech <176715578+marcabru-tech@users.noreply.github.com>
@marcabru-tech
marcabru-tech marked this pull request as ready for review August 10, 2026 21:51
Copilot AI lite review requested due to automatic review settings August 10, 2026 21:51
@marcabru-tech
marcabru-tech merged commit 7ade07c into main Aug 10, 2026
1 check passed
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Migrate hubstry.dev to Hubstry Deep Tech site (keep legacy homepage)

✨ Enhancement 🕐 10-20 Minutes

Grey Divider

AI Description

• Replace root homepage with Hubstry Deep Tech single-page app entrypoint.
• Vendor the built JS/CSS bundles and point asset URLs to root (/assets).
• Preserve the previous homepage as a local legacy snapshot for reference.
Diagram

graph TD
U([Browser]) --> H["index.html"] --> J["assets/index-Bdy9wbPf.js"] --> A["SPA renders into #root"]
H --> C["assets/index-DBdy33V5.css"]
H -. "not referenced" .-> L["index-legacy-local.html"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Build from source via GitHub Actions
  • ➕ Avoids committing large/minified build artifacts
  • ➕ Ensures reproducible builds and easier auditing of changes
  • ➕ Can enforce asset base path and other build-time settings consistently
  • ➖ Requires CI configuration and potentially a build toolchain in this repo
  • ➖ Slightly more moving parts for deployment
2. Use a submodule (or subtree) for the Deep Tech site
  • ➕ Keeps source history and updates easier to pull
  • ➕ Avoids manual copying between repos
  • ➖ Git submodules add workflow friction for contributors
  • ➖ Still needs a build step (unless also committing build output)
3. Keep deployment in the original repo and repoint domain
  • ➕ Single source of truth for the Deep Tech site
  • ➕ No duplication of artifacts across repos
  • ➖ Requires changing Pages settings/DNS and may not fit current ownership/access constraints
  • ➖ Harder to keep legacy snapshot alongside without additional hosting decisions

Recommendation: If the goal is a quick migration with fully self-contained deploy, this PR’s approach (vendoring the built assets and fixing root-relative paths) is pragmatic. For longer-term maintainability, consider moving to a CI-driven build from source (either in this repo or via a linked source repo) to avoid reviewing/merging opaque minified bundles and to make updates repeatable.

Files changed (4) +732 / -662

Enhancement (4) +732 / -662
index-Bdy9wbPf.jsVendor Deep Tech SPA JavaScript bundle +49/-0

Vendor Deep Tech SPA JavaScript bundle

• Adds/updates the built, minified JavaScript bundle that bootstraps the Hubstry Deep Tech single-page app. This file is the runtime payload referenced by the new root index.html.

assets/index-Bdy9wbPf.js

index-DBdy33V5.cssVendor Deep Tech SPA stylesheet bundle +1/-0

Vendor Deep Tech SPA stylesheet bundle

• Adds the built, minified CSS bundle (Tailwind output) required by the new SPA-based homepage. Referenced directly from index.html using a root-relative URL.

assets/index-DBdy33V5.css

index-legacy-local.htmlPreserve prior homepage as legacy snapshot +662/-0

Preserve prior homepage as legacy snapshot

• Introduces a standalone snapshot of the previous static homepage content for local reference. It is not wired into navigation and does not affect the deployed entrypoint unless manually accessed.

index-legacy-local.html

index.htmlSwitch homepage entrypoint to Deep Tech site and fix asset base path +20/-662

Switch homepage entrypoint to Deep Tech site and fix asset base path

• Replaces the previous long-form static homepage with a minimal SPA entrypoint containing #root. Updates asset references to use root-relative /assets paths to work correctly on the hubstry.dev root domain.

index.html

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.html with a minimal app shell that mounts into #root and loads the bundled assets from /assets.
  • Adds index-legacy-local.html containing 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.

Comment thread index.html
Comment on lines +16 to +17
<body class="bg-black text-white font-['Ruda',sans-serif] antialiased selection:bg-[#00ffff] selection:text-black">
<div id="root"></div>
Comment thread index-legacy-local.html
Comment on lines +1 to +2

<!DOCTYPE html>
Comment thread index-legacy-local.html
.cta-links{gap:18px}
}
</style>
<base target="_blank">
@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Grey Divider


Remediation recommended

1. Legacy snapshot deployed 🐞 Bug ⚙ Maintainability
Description
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.
Code

index-legacy-local.html[R4-7]

+<head>
+<meta charset="UTF-8">
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<title>Hubstry — Operating Deep Tech Venture Builder</title>
Evidence
The legacy snapshot is added as a standalone root-level HTML page and its <head> closes without any
robots noindex directive. Given the repo is clearly laid out as a static site root (index.html +
assets + CNAME), additional root HTML files are very likely to be deployed and reachable under the
production domain.

index-legacy-local.html[1-10]
index-legacy-local.html[276-278]
index.html[1-20]
CNAME[1-1]
index-legacy.html[1-6]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## 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


Grey Divider

Tip of the day
💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread index-legacy-local.html
Comment on lines +4 to +7
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Hubstry — Operating Deep Tech Venture Builder</title>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants