What changed, why it matters, and which routes are ready to review. Times are sourced from Git and shown in China Standard Time (UTC+8).
Compatibility ecosystem cards and filters restored
All compatibility ecosystem cards remain available while brand, device type, product path and review-status filters now update the visible results immediately.
Connected the brand search and three select controls to the 12-card compatibility ecosystem list.
Added searchable device-series aliases and explicit device, product-path and review-status metadata.
Added a live result count, clear-filters control and explicit no-results state.
Removed the duplicate review-status option and added regression coverage for combined filters.
Synchronized Progress, Changelog and Page map for v0.18.128.
CMS-managed product details now combine current CMS content with the full imported model matrix instead of reducing multi-model products to one derived row.
Prefer the full imported options matrix whenever the CMS product slug matches a migrated catalogue record.
Keep the derived single-row fallback only for CMS-only products and the two legacy products that have no imported matrix.
Align catalogue option counts and primary part numbers with the restored imported matrix.
Added merge regression coverage and synchronized Progress, Changelog and Page map for v0.18.121.
Every product detail page now shows model data below the matrix headers, including CMS-managed products and legacy records without an imported options matrix.
Stopped CMS product normalization from replacing model options with an empty array.
Preserved every imported options-matrix row and derive a single fallback row from the product code and existing technical specifications only when source rows are absent.
Covered product type, data rate, wavelength, reach and connector mappings without inventing unavailable specification values.
Added regression coverage and synchronized Progress, Changelog and Page map for v0.18.120.
Products navigation spacing and footer continuity restored
The selected Products navigation state now has balanced breathing room, and page endings flow directly into the footer without an exposed background strip.
Restored 16px desktop padding on both sides of the active Products navigation trigger after a later header rule removed it.
Removed the global 10px footer offset that exposed a white strip between dark final sections and the shared footer.
Kept the existing dropdown interaction, mobile navigation spacing and header layout unchanged.
Verified full-page section continuity, desktop and mobile rendering, dropdown keyboard activation, zero horizontal overflow and a clean browser console.
Progress, Changelog and Page map are synchronized for v0.18.115.
Page guide navigation now avoids unnecessary background requests
Website progress and Page guide links now load only when selected, reducing repeated tracker and recommendation prefetch traffic during rapid multi-page browsing while preserving every destination.
Disabled automatic Next.js prefetch for Progress, Changelog and Page map links in the floating workspace window.
Disabled automatic prefetch for Page guide recommended next-step links while preserving normal navigation on click.
Route-aware Page guide added across the Fiberland site
The Website progress window now opens a route-specific walkthrough that explains each page section, scrolls buyers to the selected content and recommends the most relevant next steps.
Added Page guide as the fourth Website progress action without changing the existing Progress, Changelog or Page map routes.
RFQ draft fields now transfer through the intended contact form
The production verification follow-up places RFQ draft transport fields on the Contact form and removes them from the FAQ form so both paths keep their own product values.
Moved the hidden product, quantity and compatible-brand transport fields from FAQ to Contact.
Preserved the visible FAQ product field as the only product source on that form.
Added browser verification for the exact Contact and RFQ field sets without submitting an inquiry.
Progress, Changelog and Page map are synchronized for v0.18.111.
Inquiry submissions now reach the CMS as clean structured fields
Contact and RFQ drafts now preserve product, quantity, compatible brand, destination and document needs as structured submission fields while leaving the buyer message unchanged.
Stopped appending contact-form selections to the free-text message, eliminating duplicated inquiry content in CMS leads.
RFQ draft values now transfer to hidden structured fields on the contact form instead of being flattened into the message.
Product interest, compatible brand, destination and document needs are submitted with canonical CMS field names.
Progress, Changelog and Page map are synchronized for v0.18.110.
Shared header styling now matches the approved homepage design
The shared desktop header now restores the approved typography, spacing, search proportions and compact quote-button treatment without changing any navigation, dropdown, search or destination behavior.
Restored the 1240px desktop header rail, 15px medium-weight navigation and 24px menu spacing from the approved design.
Restored the fixed 300px search area with a 220px field and 40px rounded-square search control.
Restored the compact 156px quote button and removed only its decorative arrow from presentation.
Preserved all six navigation entries, dropdown behavior, search submission, Company route and RFQ destination.
Progress, Changelog and Page map are synchronized for v0.18.109.
Shared desktop header scale restored to the approved design
The shared desktop header is taller and its logo, navigation, search control and quote action now use the stronger visual scale shown in the approved design while retaining the complete navigation set.
Raised the desktop header rail from 64px to 74px and enlarged the Fiberland logo from 104px to 114px.
Increased desktop navigation and quote-action text from 13px to 14px.
Adjusted search control proportions while preserving the Products, Solutions, Support, Resources, Company and Contact entries.
Kept the established 58px mobile header and compact mobile logo unchanged.
Progress, Changelog and Page map are synchronized for v0.18.108.
Company CTA and footer now join without a white gap
The Company page closing navy CTA now connects directly to the footer, removing the visible 10px white separator while leaving other information pages unchanged.
Removed the visible white strip between the Company next-step CTA and the site footer.
Scoped the flush-footer treatment to the Company page so Payment, Shipping and Site map retain their existing spacing.
Added regression coverage for the Company-only footer treatment.
Progress, Changelog and Page map are synchronized for v0.18.107.
Website progress shortcuts restored across public pages
The floating Website progress window is visible again across the public site with direct Progress, Changelog and Page map links, while preserving footer-aware hiding and Assist clearance.
Removed the RFQ-only route restriction that suppressed the progress window on Home, About, Products and other public pages.
Restored the three direct shortcuts for Progress, Changelog and Page map site-wide.
Preserved automatic hiding when the footer enters view and active-link highlighting on project routes.
Progress, Changelog and Page map are synchronized for v0.18.106.
Warranty RMA content width restored to the approved design
The RMA Process table and Support Review Steps now share the centered 1180px content rail shown in the approved Warranty layout, with responsive side gutters on smaller screens.
Restored equal desktop whitespace on both sides of the RMA table and review-step cards.
Kept both sections aligned to the same 1180px content rail used by the approved page design.
Preserved 14px mobile safety gutters without introducing horizontal page overflow.
Progress, Changelog and Page map are synchronized for v0.18.104.
Site-wide product imagery audited and all remaining low-resolution QSFP28 instances upgraded
A full rendered-media audit confirmed the homepage and product directory already use 532–1600px originals; the remaining 160x106 QSFP28 copies now use Fiberland's official 632x422 source.
Audited every rendered product and catalog image on the homepage, product directory, QSFP28 category, detail, Resources, selection guide and Solutions entries.
Confirmed homepage and product-directory originals are already 532–1600px and are never enlarged beyond their source dimensions.
Replaced every remaining low-resolution embedded QSFP28 instance across four buyer-entry surfaces with the verified Fiberland catalog asset.
Preserved every page's approved layout, image proportions, alternative text and loading priority.
Added regression coverage so the related pages cannot silently return to enlarged base64 thumbnails; the full-site rendered audit now reports zero low-resolution product sources.
Progress, Changelog and Page map are synchronized for v0.18.103.
Homepage banner overlay tags restored and extra promo rail removed
The rotating homepage banner again presents two slide-specific floating specification tags directly over each image, without the unapproved promotional rail below it.
Removed the obsolete banner-slide metadata rail from both the rendered structure and carousel runtime.
Guaranteed both floating callouts exist and update their labels, values and slide-specific positions with every banner image.
Preserved the synchronized image-and-tag crossfade for every slide.
Progress, Changelog and Page map are synchronized for v0.18.102.
100G QSFP28 LR4 detail imagery upgraded to the official high-resolution source
The product detail hero and gallery now use Fiberland's original 632x422 product image instead of a 160x106 embedded thumbnail and empty gallery placeholders.
Replaced the enlarged low-resolution base64 thumbnail with the matching Fiberland catalog asset.
Added high-resolution front, side, label-detail and connector-detail gallery treatments from the verified product source.
Preserved responsive image proportions, meaningful alternative text and lazy loading below the fold.
Progress, Changelog and Page map are synchronized for v0.18.101.
The Resources landing page now consistently uses the approved resource-hub layout instead of switching to a different data-driven directory when articles are present.
Restored the approved Resources hero composition, topic finder, buyer task lanes and featured 100G QSFP28 guide.
Removed the extra Search action and restored the approved Guides, Trends and Internal Updates section copy.
All existing resource article detail routes remain available under /resources/[slug]/.
Progress, Changelog and Page map are synchronized for v0.18.98.
The homepage now explicitly resets the mobile document margin so the header, product cards and floating support entry remain within the 390px viewport.
Removed the browser-default 8px mobile document margin that caused horizontal overflow after responsive rendering.
Verified the ten-card new-products section remains single-column on mobile without clipping or horizontal scrolling.
Progress, Changelog and Page map are synchronized for v0.18.86.
Homepage new-products grid restored to the approved design
The homepage new-products section again displays two complete rows of five products, with product-specific tags and the View details arrow action on every card.
Restored the missing second row so the section presents the approved ten-product grid at desktop width.
Assigned distinct New, Hot, Kit, Optics and CWDM labels to the visible product cards instead of repeating generic category pills.
Restored the right-arrow affordance in each View details action while retaining the complete card as the navigation target.
Progress, Changelog and Page map are synchronized for v0.18.85.
Homepage banner carousel and technical callouts restored
The homepage equipment banner again rotates through four visual slides, with both floating technical labels updating from the active slide data.
Connected the carousel to the homepage design structure: its image, existing four indicators and two floating technical cards.
Added slide-specific product and application callouts so the labels no longer remain on the initial QSFP-DD and link-loss values after an image change.
Restored keyboard-accessible slide indicators while retaining reduced-motion support and image fade transitions.
Progress, Changelog and Page map are synchronized for v0.18.84.
Products inquiry form restored to the approved design
The Products-page inquiry section again uses the approved white panel, readable heading and compact three-column buyer form without the generic consent layout.
Restored the dark Products inquiry heading and supporting copy on the white panel instead of inheriting the navy-section white heading color.
Reinstated the approved Product family, Target device, Quantity, Receiving country, Business email, Target speed / reach and Requirement details fields.
Kept the validated inquiry API and CMS delivery path while removing the generic nested card and oversized visible consent control from this design-specific form.
Preserved the independent Request a Quote contact disclosure and all shared form behavior.
Progress, Changelog and Page map are synchronized for v0.18.83.
The homepage hero now matches the approved composition, the Website progress dock no longer covers buyer pages, and tabs use a dedicated Fiberland favicon.
Removed the detached Featured Optics strip and restored the approved in-banner metric cards and compact slide indicators.
Restricted the Website progress dock to Request a Quote and project workspace routes so it cannot cover homepage or catalog content.
Replaced the horizontal wordmark favicon with a square Fiberland brand mark designed to remain legible at browser-tab size.
Desktop and mobile browser acceptance covers the homepage layout, RFQ progress entry, navigation, favicon response and console health.
Progress, Changelog and Page map are synchronized for v0.18.80.
Workspace dock footer observer follows client navigation
The Website progress dock now rebinds to the current page footer after client-side navigation, preserving footer clearance on RFQ and every public route.
Footer visibility state is tied to the current pathname, so a detached footer from the previous page cannot leave the dock visible over new footer content.
The dock stays hidden while a route-level footer observer is being established and becomes visible only after the current footer is confirmed outside the viewport.
Products-to-RFQ client navigation, direct RFQ loading, mobile menu behavior and project shortcuts retain their existing placement and labels.
Progress, Changelog and Page map are synchronized for the v0.18.77 production acceptance repair.
Frontend API redirects removed from buyer workflows
Inquiry, form-definition, project-feedback and Datasheet requests now call canonical same-origin API paths without an intermediate 308 redirect.
RFQ and reference-page inquiry submissions now post directly to /api/inquiries/ while preserving validation, fail-closed persistence and buyer success messaging.
Optional form definitions and project feedback use their canonical trailing-slash routes, removing an unnecessary browser round trip.
Public Datasheet links now target the canonical protected delivery route directly and continue to hide the CMS application port.
Progress, Changelog and Page map are synchronized for the v0.18.76 production acceptance repair.
The Website progress dock stays hidden until footer visibility is known, eliminating the brief pre-hydration overlap seen in fast bottom-of-page navigation.
Server-rendered and pre-hydration output now keeps the floating progress dock hidden by default.
The dock becomes visible only after the footer observer confirms that buyer footer content is outside the viewport.
Desktop, mobile and project-route shortcuts retain their existing placement and navigation once clearance is confirmed.
Progress, Changelog and Page map are synchronized for the v0.18.75 Alibaba acceptance repair.
Alibaba footer, form fallback and Datasheet runtime repaired
The Website progress dock now clears the footer, optional form-definition failures fall back cleanly, and Datasheets load CMS content immediately after a zero-CMS build.
The floating Website progress dock observes the public footer and hides while footer content is visible on desktop and mobile.
The CMS form-definition proxy now returns the built-in form fallback when its optional upstream definition is unavailable.
The Datasheet directory now renders dynamically at runtime, so a zero-CMS production build cannot publish an empty one-hour ISR snapshot.
The Alibaba frontend now reads the healthy same-server CMS through its private loopback endpoint instead of the unavailable external CMS deployment.
Buyer forms, inquiry submission transport and independently controlled CMS publication settings remain unchanged.
Progress, Changelog and Page map are synchronized for the v0.18.74 Alibaba acceptance repair.
RFQ restores the shared navigation and progress entry
Aligned the Request a Quote route with the full site header and restored the floating Progress, Changelog and Page map shortcuts beside Fiberland Assist.
The RFQ page now uses the same Products, Solutions, Support, Resources, Company and Contact navigation as every other buyer route.
Products and section menus retain their full hover, keyboard and mobile-menu behavior after entering RFQ from the shared Request a Quote action.
The Website progress dock is mounted from the root layout on RFQ and other public pages, with direct Progress, Changelog and Page map links.
Desktop and mobile positioning keeps the progress dock separated from Fiberland Assist, while the dock hides automatically whenever the mobile navigation is open.
Playwright verified the Products to Request a Quote click path, both dropdown types, six shared navigation destinations, Progress visibility, Submit RFQ clearance, 390px layout and zero console errors.
Progress, Changelog and Page map were synchronized for the shared RFQ navigation repair.
Production P1/P2 defects and B2B buyer journey repaired
Completed the QA repair cycle for product discovery, inquiry conversion, technical documents, catalog completeness, buyer-facing copy, on-page SEO and mobile acceptance.
Product search now applies every search token immediately, while large category pages expose the full catalog through accessible 12-item pagination.
RFQ, contact, sample and compatibility forms now show buyer-visible validation; RFQ contact fields stay open and valid submissions reach the inquiry API exactly once.
Public Datasheet links now use a same-origin protected delivery route instead of exposing or depending on the CMS application port.
CMS image filenames resolve to audited local legacy assets, including the seven previously broken product-image variants.
Buyer pages no longer expose the development workspace or CMS implementation language, and all inquiry routes now include the shared proof and Submit to Review to Reply guidance.
Thin Selection Guide, Datasheet Downloads and Uncategorized category URLs now redirect to useful canonical hubs and are excluded from the XML sitemap.
Datasheets publish CollectionPage markup, case details publish Article and Breadcrumb markup, category descriptions use buyer selection language, and blocking external font requests were removed.
All 28 automated tests, TypeScript, ESLint, the zero-CMS production build and local Chrome desktop/mobile regression passed before release packaging.
Progress, Changelog and Page map were synchronized for the P1/P2 and B2B QA acceptance release.
CMS master content now controls both frontends directly
Products, articles and cases are selected for Fiberland and Astra Photon in CMS without either frontend becoming the other site's content source.
Fiberland continues to query its own CMS project endpoint while receiving records assigned to the Fiberland publication target.
The Cases page no longer substitutes six static application scenarios when the CMS has no published case records.
Shared CMS records retain site-specific URLs, SEO framing and frontend presentation while their canonical product, article and case content stays aligned.
Progress, Changelog and Page map were synchronized for the CMS master-content release.
Reworked fixed and dynamic page metadata so every rendered title stays within 60 characters and every description stays within 160 characters.
Thirty fixed buyer and workspace routes now use reviewed, page-specific titles and descriptions instead of legacy titles or generic fallback copy.
All 661 snapshot product pages and 467 resource pages now pass search-intent cleanup and final metadata length guards, with matching Open Graph and Twitter copy.
Dynamic product categories, CMS pages, cases, compatible brands and certification details now share the same metadata rules and canonical output.
Automated coverage checks every migrated product, resource and fixed route against the 60-character title and 160-character description limits.
Progress, Changelog, and Page map were synchronized for the metadata optimization.
Sitewide heading hierarchy aligned for on-page SEO
Removed skipped heading levels from the homepage and all reference templates while preserving the approved card and footer styling.
Homepage product categories now use parallel H2 headings, while product, data-center, and patch-cord cards use H3 headings beneath their section H2.
The shared reference-page renderer now normalizes homepage category cards and legacy footer groups before output, covering every existing reference template and future route use.
Generated homepage cards now emit H3 headings, and an automated full-template check fails when any rendered reference heading jumps more than one level.
Progress, Changelog, and Page map were synchronized for the semantic heading repair.
RFQ reference layout and focused quote flow restored
Restored the approved RFQ first viewport with the compact navigation, buyer-facing CTAs, and five-field quote brief.
The RFQ header now matches the approved reference navigation: Products, Solutions, Support, Resources, Contact, search, and a direct Request a Quote action.
The hero now uses the approved title treatment, CTA labels, spacing, an empty Requirement details prompt, and compact Product, Quantity, Compatible brand, Destination, and Requirement details fields.
The internal development workspace dock is suppressed on the RFQ route so it cannot cover the primary submit action.
Production prelaunch checks now verify legacy URLs redirect to the current canonical product and resource routes.
Contact details stay available on demand before a submission so the quote workflow remains deliverable without crowding the first viewport.
Progress, Changelog, and Page map were synchronized for the RFQ fidelity repair.
Corrected canonical and sitemap coverage to use current Fiberland URLs, then added page-level social metadata and structured data for key buyer paths.
Canonical URLs for products, resources, support pages, shipping, payment, company, and the human-readable site map now use current public routes instead of legacy aliases.
The XML sitemap now excludes legacy and redirect-only URLs while keeping current product, category, resource, support, and company pages discoverable.
Added consistent Open Graph and Twitter metadata, WebSite search markup, BreadcrumbList markup for products, categories, and resources, CollectionPage markup for catalog hubs, and FAQPage markup for published CMS FAQs.
Product and resource data now generate current canonical URLs, preserving their legacy source URL separately for redirects and migration reference.
Progress, Changelog, and Page map were synchronized for the on-page SEO release.
Buyer paths simplified across product and inquiry pages
Applied the B2B inquiry-site review to reduce repeated proof and preparation content, clarify buyer-facing headings, and keep immediate quote or contact actions visible.
Product detail pages now use six anchored buyer tasks: overview, specifications, compatibility, documents, FAQ, and RFQ; duplicate gallery, commercial, quality, and application floors were removed.
Homepage proof content now uses the shared Datasheets, Compatibility, Testing & QC, and Compliance strip instead of repeating separate warranty, quality, certification, and compatibility blocks.
Contact is now the single general inquiry route; the legacy enhanced-contact URL redirects to it, while RFQ and Sample retain their dedicated immediate forms and embedded Submit, Review, Reply guidance.
Resources copy now uses buyer-facing language, and Datasheets adds product-path shortcuts alongside the working keyword and document-type filters.
Progress, Changelog, and Page map were synchronized for the buyer-path repair.
Production imagery completed across public buyer paths
Replaced remaining image placeholders, restored missing homepage and catalogue assets, and delivered optimized local media for the Fiberland and Astra public sites.
Fiberland quality and factory evidence cards now use dedicated DDM testing, final inspection, warehouse packing, and engineering-team photography.
Existing Fiberland homepage and solution imagery was converted to high-quality WebP, reducing the media payload from about 31 MB to about 2.8 MB.
Astra solution cards now use four distinct production photographs instead of schematic placeholders.
Astra fallback catalogue media is now served from local assets, including a formal image for the 400G QSFP-DD entry, with no dependency on the old preview domain.
Progress, Changelog, and Page map were synchronized for the production-media release.
AI tasks now call configured providers with timeout, retry and fallback, then produce reviewable field diffs instead of directly publishing content.
Editor, reviewer and owner/admin publishing boundaries are enforced in Payload hooks and field access rules, including protected deletion.
Signed ten-minute preview tokens scope every draft read to one project, collection, document and optional locale.
CMS form definitions now drive Fiberland and Astra fields, required states and success copy while preserving custom lead data and anti-abuse controls.
Cases, compatibility brands, certifications and managed pages now have frontend list/detail consumption paths with bounded fallbacks.
Reviewed translations are stored by locale and overlaid by the site content API; AI suggestions and translations remain gated by Change Request review.
Progress, Changelog, and Page map were synchronized for the completed CMS workflow implementation.
Replaced the static prototype-only Datasheet finder with real keyword and document-type filtering, result counts, and an honest empty state that works without Neon.
PRD browser acceptance identified that the former Datasheet controls did not change results or expose a no-results state.
The CMS-backed directory now filters titles, summaries, categories, and slugs by keyword and document type with an accessible live result count.
Snapshot and newly installed environments now show an explicit zero-document state instead of presenting inert development-placeholder controls.
The repair requires no Neon read and remains ready to populate from the audited 202-record Datasheet import on the target server.
Progress, Changelog, and Page map were synchronized for the Datasheet functional acceptance repair.
CMS, migration, and conversion acceptance hardened
Added production-safe evidence and fail-closed behavior for CMS readiness, legacy migration, RFQ persistence, notifications, and project feedback while preserving the zero-Neon deployment flow.
Neon connectivity and the complete migration chain were rechecked in production; readiness now emits sanitized operational events for dependency and initialization failures.
Storage readiness now performs a real authenticated S3 HeadBucket probe, so an invalid endpoint, bucket, or credential can no longer pass based on environment-variable presence alone.
A protected operations-audit endpoint reports production counts, storage readiness, SMTP state, and recipient count without exposing credentials, addresses, lead payloads, or database URLs.
The repeatable offline migration audit verifies 10 FAQ records, 202 complete Datasheets, and 636 unique product media assets while retaining ten documented legacy-source exceptions.
The verified media manifest now allows product images to use their original assets without a build-time filesystem scan, removing a 17,812-file Turbopack trace warning.
Production inquiries no longer fall back to ephemeral Vercel JSONL storage: they require authenticated CMS persistence and return a retryable 503 when safe storage is unavailable.
Accepted leads schedule immediate queue processing, project-feedback failures use safe public messages, and daily recovery workers accept independent operator and Vercel Cron secrets.
The prelaunch check now validates the on-demand ISR product route instead of requiring a removed static product HTML artifact.
Progress, Changelog, and Page map were synchronized for the CMS, migration, and conversion acceptance work.
Separated code deployment from content synchronization so every production build uses checked-in migration snapshots and makes zero CMS or Neon reads.
The default pnpm build command now starts Next.js with FIBERLAND_CMS_BUILD_MODE=snapshot, which blocks every CMS read during static generation.
Product, article, FAQ, Datasheet, sitemap, and project-tracker pages use checked-in migration data while the deployment artifact is built.
The snapshot-only flag is scoped to the build child process, so deployed runtime functions still read CMS content when an ISR path or cache tag is refreshed.
CMS publishing now uses /api/revalidate instead of requesting a new frontend deployment, keeping content updates independent from code releases.
Vercel is pinned to the safe pnpm build command, so each code release performs one snapshot-only production build without a second CMS-backed build.
Progress, Changelog, and Page map were synchronized for the zero-Neon deployment architecture.
Removed full-catalog static generation from deployments so detail routes are generated on first access, cached for one hour, and refreshed through the existing revalidation workflow.
All 661 product and 467 resource detail routes now return an empty build-time parameter list and remain available through dynamic parameters with hourly ISR.
Legacy reference aliases are no longer prebuilt; the existing proxy handles known redirects while valid fallback documents remain available on demand.
Product and resource detail lookups now query the CMS by exact slug, and related resource cards request only the small result window they need.
Page map builds its complete route inventory from the local migration snapshot instead of downloading the CMS collections during every deployment.
The verified production build dropped from 1,196 generated pages to 44, while static generation time fell from about 28.0 seconds to 2.2 seconds.
Progress, Changelog, and Page map were synchronized for the on-demand ISR architecture.
Reclassified the complete release history so major delivery milestones advance the second segment while regular changes advance the final segment without resets.
Reviewed all 70 prior entries by development scope instead of treating every change as the same size.
Platform foundations, repositories, public releases, data migrations, cross-site infrastructure, CMS transfer optimization, and complete P1/P2 repairs are classified as major updates.
A regular update changes v0.1.1 to v0.1.2; a major update changes v0.1.1 to v0.2.1, so the unchanged segment never resets or moves backwards.
The visible history now runs from v0.1.0 through v0.14.57 with the same impact-aware rule applied to fallback and CMS-backed records.
Progress, Changelog, and Page map were synchronized for the complete version-history reclassification.
P2 navigation, accessibility, SEO, and reference-page issues repaired
Completed the P2 cross-site repair for missing page tasks, mobile overlays, hidden form controls, metadata continuity, and invalid footer actions.
Testing and Quality and Application Cases now expose one clear page-level heading, task copy, actions, and anchored content entry.
The mobile navigation now exposes the correct open and close state, closes with Escape, locks background scrolling, and temporarily hides fixed support tools that would cover the menu.
Inquiry honeypot controls now use clipped accessible hiding instead of an off-canvas field that expanded the page layout.
Footer social actions now use verified Fiberland destinations, placeholder links were removed, and utility links point to real site pages.
Reference titles no longer repeat the Fiberland suffix; canonical metadata and the XML sitemap now cover the current-only support and solution routes.
Progress, Changelog, and Page map were synchronized for the complete P2 repair.
Product detail routes now own the shared site shell
Moved the common header, footer, trust strip, and floating inquiry launcher into the product-detail route layout so every product page receives the same outer framework.
Every /products/[slug] route now receives SiteHeader and SiteFooter from its dedicated Next.js layout instead of relying on the inner product content component.
ProofStrip and FloatingInquiry are mounted once by the same route shell, preventing duplicate or missing shared chrome when the product template changes.
The product content component now owns only the main product page, keeping the route framework separate and reusable.
Progress, Changelog, and Page map were synchronized for the product-detail framework repair.
CMS data transfer and build request volume optimized
Replaced per-detail CMS queries with shared collection snapshots and added quota-aware failure protection for production builds.
Product and resource detail pages now resolve slugs from one shared paginated snapshot per collection instead of querying CMS once per generated page.
Static generation now runs in one database-aware worker so every collection reuses one in-flight snapshot; successful snapshots remain reusable for one hour and failed requests pause retries for 15 minutes.
CMS fetch revalidation now matches the one-hour page policy, while authorized on-demand revalidation clears both Next.js tags and the process snapshot.
Progress, Changelog, and Page map were synchronized for the database-transfer optimization.
P1 catalog, search, inquiry, and content-page issues repaired
Restored canonical product categories, activated the live catalog finder, connected reference inquiry forms, and separated company and commercial information pages.
All ten product families now use one canonical CMS and legacy-data mapping, keeping SFP and SFP+ separate and restoring previously empty category pages.
The Products page now uses the live 661-record finder with URL query handoff, filters, pagination, and a real no-results state.
Product, contact, FAQ, datasheet, and compatibility inquiries now use the validated inquiry API instead of inert buttons or field-dropping redirects.
The legacy-route proxy now treats slash and non-slash forms as the same route, preventing the FAQ trailing-slash rewrite loop.
About, Shipping, Payment, and Site map now have distinct responsive content while Warranty retains its dedicated RMA policy page.
Progress, Changelog, and Page map were synchronized for the complete P1 repair.
Product detail presentation and delivery timestamp corrected
Restored the shared product-detail page framework, stabilized the product image, and synchronized the public delivery record with China Standard Time.
Product detail routes now render the shared site header, breadcrumb, commercial actions, specifications, and supporting page sections consistently.
The 100G QSFP28 breakout AOC image now loads directly from the verified local high-resolution asset instead of depending on the redirected image optimizer request.
Progress, Changelog, and Page map now reference the verified delivery time in China Standard Time (UTC+8).
Replaced the separate reference-page navigation with the same shared header used by product category and detail pages.
Homepage, Products, and the remaining reference-backed routes now render the shared SiteHeader component instead of maintaining a second header implementation.
Products, Solutions, Support, and Resources consistently show dropdown arrows and open their shared navigation menus.
Reference-page CSS is isolated to page content so it can no longer restyle the shared header.
