Skip to content

[Task] track OINK homepage visual directions #467

Open
Open
[Task] track OINK homepage visual directions#467
Labels
enhancementNew feature or request

Description

@imbajin
imbajin
opened on Aug 31, 2026

Purpose

Track the homepage visual history for the OINK 1.0 migration without replacing earlier evidence. Each visual checkpoint will be added as a separate comment with its screenshot, immutable source/artifact commits, viewport, theme, and image checksum.

Planned snapshots

  • V0: Docsy production baseline
  • V1: initial OINK migration shell before visual selection
  • V2: retained alternative direction (split documentation entry)
  • V3: selected direction (brand scene recomposition) after implementation and staging verification

The migration implementation remains in #466. This issue is only the durable design comparison timeline; it does not change the selected direction by itself.

Decision

Direction 1 is selected for the migration. Direction 2 is retained here as a future alternative so its layout can be revisited without reconstructing the original comparison.

Activity

  1. imbajin
    added
    enhancementNew feature or request
    on Aug 31, 2026

  2. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    V0 — Docsy production baseline

    Legacy homepage before the OINK migration. This preserves the original brand scene, title, calls to action, and introductory copy as the content baseline.

    • Evidence: user-provided production screenshot
    • Viewport: 1265 × 712
    • Theme: light
    • Image SHA-256: eedbbb71d5048e747ec12d06ef3008e80e6359ac9b20720e0850b7f0e532eb47
    • Source/artifact commit: not reconstructed from the screenshot; intentionally left unknown rather than inferred
    Image

  3. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    V1 — Initial OINK migration shell

    First complete OINK shell before the final homepage visual direction was selected. It established the task-oriented navigation, local search, language/version controls, and the central multi-version rendering baseline.

    • Source commit: 4d43cf3231b5655f6e3b9224da696cd0280df1f3
    • ASF staging commit: 3f653c53d5d481ceb4f52a3443da94af03c2d495
    • Viewport: 1265 × 712
    • Theme: light
    • Image SHA-256: e13e95942b68a56c3c1e6a7fcb41bd836806f50b9f882208d27c1983056f962c
    • Status: deployed historical checkpoint; superseded visually by the selected direction
    Image

  4. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    V2 — Retained alternative: split documentation entry

    Design-only alternative retained for future consideration. It separates the documentation entry path from the product story while preserving the original HugeGraph copy and core brand artwork. Direction 1 was selected instead, so this candidate was never deployed.

    • Status: design candidate only; not implemented or staged
    • Canvas: 1487 × 1058
    • Theme: light
    • Image SHA-256: 621ad821943eea959f6c5bf7a4017538096c7ed5a5667b18bf6000c3804ec8b8
    • Decision: retained here so the layout can be revisited without reconstructing the comparison
    Image

  5. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    V3 — Selected direction: brand scene recomposition

    Final OINK migration homepage, deployed and verified on ASF staging. This direction keeps the original HugeGraph title, two product-description paragraphs, calls to action, and five-object brand illustration while using the new OINK navigation, search, task paths, responsive behavior, and accessibility shell.

    • Source commit: 352953fa4546c63980a78ed1bca222f38adbf50a
    • Exact-head CI: run 33373403986
    • ASF staging commit: 91bb25950ca3c175694f50dde3da2726bea6e7d7
    • Live preview: https://hugegraph-oink.staged.apache.org/
    • Artifact: 2,274 files; path/content SHA-256 ea4b47cabf6e140b5b7d1b20327face52f1f537fde890a6356de4c03aa016b54
    • Desktop: 1280 × 720, light, image SHA-256 5596c1ba7a420635290e1154f7d151d095461911da3d8b1f9dd22d23bf73a12e
    • Mobile: 390 × 844, light, image SHA-256 c3bd96682ee58275ef5b2884862d6f4ba13562dff7c5e7ab605d5789933090d6
    • Status: selected, implemented, staged, and browser-verified
    Image Image

  6. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    V4 — Selected direction with corrected language and TOC semantics

    The selected homepage direction is visually unchanged: it still preserves the original HugeGraph title, two product-description paragraphs, calls to action, and five-object brand illustration. This checkpoint records the corrected archived-language targets and localized TOC accessible names on the exact reviewed source.

    • Source commit: 2f033ebe417ed90903ec23141ff57852326a3827
    • Source tree: 5312b3ac1bdd916a933105a0a21cb49df97d9595
    • Exact-head CI: run 33385294358 — prepare, 6/6 builds, and required deploy passed; PR publish skipped
    • ASF staging commit: b8df2c1f3990622aabe70fb8346be287154fcb8a
    • ASF staging tree: eea70df73e6ca587037596edbd31bc68d36c970c
    • Live preview: https://hugegraph-oink.staged.apache.org/
    • Artifact: 2,274 files; 684 HTML; path/content SHA-256 044e6e526cb52e8b72640cff77c6bd872c3c04e0aa7bccdc56ee5c16ee5f1082
    • Live audit: 684/684 HTML and 1,005/1,005 same-origin resources byte-identical; 414/414 named TOCs; 658/658 language actions; 6/6 search indexes and 6/6 error documents
    • Desktop: 2033 × 977, light, image SHA-256 d85801a5bc802089ec2aeab6024d3c51f12383105812a93d214af61d65d49569
    • Mobile: 390 × 844, light, image SHA-256 e7bfdd56f743ab4e95d716bb69ad5e9f697c3e7b25032ffc9e8a27523bc070dd
    • Status: deployed and browser-verified corrective checkpoint; later IA refinements should be appended as a new version rather than replacing this record
    Selected OINK homepage after language and TOC corrections Selected OINK mobile homepage after language and TOC corrections

  7. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    V5 — Final refined OINK homepage and Community restoration

    Final migration checkpoint on the dedicated ASF OINK staging site. The header now forms one continuous surface with the original HugeGraph hero, the familiar homepage descriptions are restored below it, the ASF footer is simpler, and the Community page again exposes the original learning and contribution paths.

    • Source commit: 0a5f402479606f34a87b46691c1a6ce47fc17b4c
    • ASF OINK staging commit: c93269ee903d853d851ca1f808c308d729f8fbdf
    • Live preview: https://hugegraph-oink.staged.apache.org/
    • Desktop: 1905 × 960, light, image SHA-256 b4ff3b8fbaea6383d4831cf6bdd2b0b7cb0884b08b041061aec0f1f0b6eccf0c
    • Mobile: 390 × 844, light, image SHA-256 35356e82172ef5b517d657bce744d73a61cce45b8190ab523217555d93b46d2c
    • Community: 1905 × 960, light, image SHA-256 1ede864f8035fe5e2be18016a8b543fe13db94b98802c48927047d449c009b10
    • Status: selected, deployed, and verified in Chrome; the standard ASF staging site remains unchanged

    Final refined OINK homepage on the dedicated ASF staging site

    Final refined OINK mobile homepage on the dedicated ASF staging site

    Restored Apache HugeGraph Community landing page

  8. imbajin commented on Aug 31, 2026

    @imbajin
    imbajin
    on Aug 31, 2026
    MemberAuthor

    Reference — existing standard staging direction

    This is a separate homepage currently available at https://hugegraph.staged.apache.org/. It is not the selected OINK migration checkpoint and was not overwritten. The snapshot is retained only as a design reference for later iterations.

    Patterns worth revisiting independently:

    • the stack-oriented entry cards;
    • the visible quick-start command block;
    • the compact workload/proof strip;
    • direct top-level access to Team and Users.

    Direction 1 remains selected for #466, with the original HugeGraph hero and copy preserved.

    • Viewport: 1905 × 905
    • Theme: dark
    • Image SHA-256: 0d8ed1f48ce89568c39b50633eaf1adc5357ade8ce3789cce686c5b4babc1645

    Existing standard ASF staging homepage retained as a future design reference

  9. imbajin commented on Sep 1, 2026

    @imbajin
    imbajin
    on Sep 1, 2026
    MemberAuthor

    V6 — global navigation and compact ASF footer

    This checkpoint restores version discovery consistently across direct local builds, desktop navigation, and both mobile drawers.

    Desktop Documentation versions Compact ASF footer
    Documentation hover menu with latest, 1.7, and 1.5 Compact ASF footer without Privacy or duplicate utilities
    Homepage mobile drawer Docs mobile drawer
    Homepage mobile drawer with versions, languages, themes, and GitHub Docs mobile drawer with versions, languages, themes, and GitHub

    Chrome verification covers pointer hover, Arrow Down focus, header help, 390 × 844 drawers, language/theme controls, and zero horizontal overflow. The staging replay also caught Apache's reserved /icons/ alias; the ASF wordmark now uses /img/apache_logo.svg and loads successfully.

  10. imbajin commented on Sep 1, 2026

    @imbajin
    imbajin
    on Sep 1, 2026
    MemberAuthor

    V7 — Unified HugeGraph lockup and continuous Docs header

    This checkpoint separates the visible shell brand from the longer page/SEO identity. Navbar, Docs sidebar, collapsed state, and subnav now share the configurable HugeGraph lockup, while document titles remain Apache HugeGraph. The fixed sidebar identity row and global navbar form one continuous purple band without URL/title conditions or a fixed sidebar width.

    • Source: afed4bd11
    • ASF OINK staging: b2edfd412
    • Live preview: hugegraph-oink.staged.apache.org/docs/
    • Chrome viewport: 1230 × 536; captured bitmap 1215 × 529 after scrollbar
    • Theme: light
    • Image SHA-256: 70b3a34d86df909c7726366191717f07a7d74b0cd2ea7d355223870522da3f52
    • Runtime checks: expanded/collapsed desktop, 390 × 844 mobile, English/Chinese Homepage and Community, zero document overflow
    • Status: deployed and verified in Chrome; standard ASF staging and production remain unchanged
    Image
  11. imbajin
    added a parent issue on Sep 2, 2026
  12. imbajin
    changed the title [-]docs: track OINK homepage visual directions[/-] [+][Task] track OINK homepage visual directions[/+] on Sep 4, 2026

  13. imbajin commented on Sep 4, 2026

    @imbajin
    imbajin
    on Sep 4, 2026
    MemberAuthor

    V8 — Ask AI interaction direction

    This comparison records the interaction decision for the optional Kapa enhancement before staging activation.

    • Selected: combine a contextual Search Tail with a persistent but restrained Floating Launcher.
    • Rejected: a persistent side panel, because it competes with documentation reading space and duplicates the native summary-search path.
    • Visual constraint: use the shared HugeGraph purple theme token; do not revive the old red/pink assistant treatment.
    • Behavior constraint: native summary search remains primary. Kapa loads only after an explicit click, is locale-bound, and any timeout or failure remains isolated from local search and publication.
    • Canvas: 1717 × 916
    • Image SHA-256: 68a97ffa93941608fa6d112e77331e464df59a824b8073ebf1c5543a472c98c2
    • Status: selected design direction; final staging screenshots and real Kapa smoke evidence will be appended separately after deployment.
    Image

  14. imbajin commented on Sep 18, 2026

    @imbajin
    imbajin
    on Sep 18, 2026
    MemberAuthor

    Current OINK staging evidence is now refreshed from candidate 07094e642a29f882b94abcf98c0228ddc84d008a: full five-version staging run, EN docs, 中文文档, EN LLMSFULL, and 中文 LLMSFULL.\n\nRepresentative current screenshots are attached in Apache PR #493 under .github/oink-evidence/: EN/CN docs, sidebar, search, Community, desktop/mobile, and light/dark variants. Real Kapa remains a separate pending acceptance gate; AI is not claimed enabled.

  15. imbajin commented on Sep 18, 2026

    @imbajin
    imbajin
    on Sep 18, 2026
    MemberAuthor

    Latest integration checkpoint: organization PR #36 is merged at 143c980fa; Apache delivery PR #493 remains Open/non-Draft at candidate 659f94dd3. The current candidate CI is green across all five builds, aggregate, Chromium/E2E, visual and deploy, with three bounded independent reviews clear.

    The last published staging remains 07094e642. A master-loaded staging dispatch for the current candidate is intentionally held because Apache master still has the old checkout behavior; the attempted run failed before publish with asf-downloads missing. The reviewed immutable-SHA workflow fix is in PR #493. Final staging screenshots and real Kapa evidence will be appended after the trusted path is available.

  16. imbajin commented on Sep 18, 2026

    @imbajin
    imbajin
    on Sep 18, 2026
    MemberAuthor

    Focused visual evidence — current candidate

    Apache PR #493 is at head 225537d1. The PR description now keeps English desktop screenshots primary, separates Mobile, and limits images to changed surfaces:

    Desktop

    Mobile

    The Ask AI images show the native search entry and pre-request consent boundary only; they do not claim a live Kapa answer. Current local evidence remains roster 38/38, full Python contracts 169 tests (one skipped), Hugo builds passed, Chromium platform/accessibility/visual 23/23, and three scoped reviewers CLEAR on the current org/Apache heads. The candidate remains open/non-draft and awaits human review plus the protected trusted staging publication path. Mapped cards default to verified GitHub login with six explicit display-name overrides (Imba Jin, Jermy Li, Jacky Yang, Jason, Thespica, and Willem Ning Jiang); four ASF-only entries remain static cards.

  17. imbajin
    added a commit that references this issue on Sep 19, 2026

    feat: complete OINK site integration (#493)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions