From 2cb1c245f5893026b1942b1aa15248771d425a94 Mon Sep 17 00:00:00 2001 From: Florin Barbu Date: Mon, 21 Sep 2026 13:44:32 +0300 Subject: [PATCH 01/10] docs(web): add 2026 Q4 commitments and tasks --- content/web/ift/2026q4-demos.md | 37 ++++++++++++ content/web/ift/2026q4-maintenance.md | 63 +++++++++++++++++++++ content/web/index.md | 15 +++++ content/web/logos/2026q4-logos-website.md | 57 +++++++++++++++++++ content/web/status/2026q4-status-website.md | 57 +++++++++++++++++++ 5 files changed, 229 insertions(+) create mode 100644 content/web/ift/2026q4-demos.md create mode 100644 content/web/ift/2026q4-maintenance.md create mode 100644 content/web/logos/2026q4-logos-website.md create mode 100644 content/web/status/2026q4-status-website.md diff --git a/content/web/ift/2026q4-demos.md b/content/web/ift/2026q4-demos.md new file mode 100644 index 0000000000..51ff4db289 --- /dev/null +++ b/content/web/ift/2026q4-demos.md @@ -0,0 +1,37 @@ +--- +title: Demos +tags: + - "2026q4" + - "web" + - "ift" +draft: false +description: Demonstrate completed Web team work at IFT Townhalls, share implementation learnings, and gather feedback. +--- + +`ift-ts:web:ift:2026q4-demos` + +## Description + +Continue the Web team's recurring demonstrations of completed work during Q4. +Show shipped website features, fixes, and improvements to the organization, share useful implementation learnings, and capture stakeholder feedback for follow-up. + +## Task List + +### IFT Townhall demos (recurring) + +* fully qualified name: `ift-ts:web:ift:2026q4-demos:ift-townhall` +* owner: unassigned +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Prepare and deliver demonstrations of completed Web work at the biweekly IFT Townhalls during Q4. +Select relevant deliverables and a presenter for each session, explain the user-facing changes, and gather feedback from other teams. +Track actionable feedback in the relevant website or maintenance task. + +#### Deliverables + +- Presentation materials and demo recordings or documentation for each session delivered. +- Links to demonstrated work and tracked follow-ups from stakeholder feedback. diff --git a/content/web/ift/2026q4-maintenance.md b/content/web/ift/2026q4-maintenance.md new file mode 100644 index 0000000000..90feada692 --- /dev/null +++ b/content/web/ift/2026q4-maintenance.md @@ -0,0 +1,63 @@ +--- +title: Web Maintenance & Support +tags: + - "2026q4" + - "web" + - "ift" +draft: false +description: Maintain shared Web tooling, dependencies, and deployment workflows, and improve AI-assisted development practices. +--- + +`ift-ts:web:ift:2026q4-maintenance` + +## Description + +Continue recurring Web maintenance from Q3, focusing on common tooling and workflows used by the team's websites. +Keep shared dependencies, CI, preview deployments, and hosting integrations reliable. +Build on Q3 AI review workflows and improve agent-assisted debugging, testing, and implementation across Web repositories. +Triage incoming requests with the team and track scope, priorities, and follow-up ownership. +Record site-specific upkeep and implementation under [[web/logos/2026q4-logos-website|Logos Website]] or [[web/status/2026q4-status-website|Status Website]], with shared changes tracked here once. + +## Task List + +### Maintenance + +* fully qualified name: `ift-ts:web:ift:2026q4-maintenance:maintenance` +* owner: Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain common build tools, shared dependencies, CI checks, preview deployments, and hosting workflows. +Resolve shared infrastructure or tooling failures, coordinate with Infra where needed, and document changes that affect website development or releases. + +#### Deliverables + +- PRs updating shared dependencies, tooling, and CI or deployment configuration. +- Verified fixes for shared workflow failures and relevant operational documentation. + +### AI and agentic workflow improvements + +* fully qualified name: `ift-ts:web:ift:2026q4-maintenance:ai-agentic-improvements` +* owner: JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Continue the AI and agent-assisted development work from Q3: +- Improve the existing shared AI PR review workflow, tune repository context and instructions, and reduce false positives. +- Use agents to investigate failures, reproduce bugs, and propose fixes that developers validate. +- Draft or extend unit, integration, and E2E tests with agent assistance, reviewing assertions and checking for flakiness before adoption. +- Extend agent-authored changes for scoped maintenance work, keeping normal PR review and human approval before merge. +- Document effective workflows, handling of sensitive information, and lessons from actual usage so the team can reuse successful approaches. + +#### Deliverables + +- PRs improving shared AI review automation and repository-specific agent instructions. +- Documented examples of agent-assisted debugging, test coverage, and maintenance changes, linked to reviewed PRs. +- Updated team guidance for review, debugging, testing, and agent-authored changes. +- A short assessment of time saved, review quality, false positives, and remaining limitations. diff --git a/content/web/index.md b/content/web/index.md index 314f7cf26c..7937519288 100644 --- a/content/web/index.md +++ b/content/web/index.md @@ -18,6 +18,21 @@ The unit's work directly supports IFT's strategic objective of scaling project c [[web/preview|Roadmap Preview]] +## 2026q4 + +### `ift:` + +* [[web/ift/2026q4-demos|demos]] +* [[web/ift/2026q4-maintenance|maintenance]] + +### `status:` + +* [[web/status/2026q4-status-website|status-website]] + +### `logos:` + +* [[web/logos/2026q4-logos-website|logos-website]] + ## 2026q3 ### `ift:` diff --git a/content/web/logos/2026q4-logos-website.md b/content/web/logos/2026q4-logos-website.md new file mode 100644 index 0000000000..ea3e26c4e2 --- /dev/null +++ b/content/web/logos/2026q4-logos-website.md @@ -0,0 +1,57 @@ +--- +title: Logos Website +tags: + - "2026q4" + - "web" + - "logos" +draft: false +description: Maintain the Logos website, deliver fixes and improvements, and implement prioritized ad hoc features. +--- + +`ift-ts:web:logos:2026q4-logos-website` + +## Description + +Continue supporting the Logos website in Q4 through recurring upkeep, fixes and improvements to existing functionality, and delivery of new features requested during the quarter. +Build on the pages, release information, forms, and newsletter flows delivered in Q3. +Select concrete work with stakeholders as needs arise and record the scope and acceptance criteria in linked issues. + +## Task List + +### Maintenance + +* fully qualified name: `ift-ts:web:logos:2026q4-logos-website:maintenance` +* owner: Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Keep the Logos website and its existing integrations working as dependencies, content, and releases change. +Maintain site-specific dependencies and configuration, release and download links, forms, newsletter flows, and deployment health. +Investigate production failures and ship necessary hotfixes, coordinating shared tooling changes with the Web maintenance commitment. + +#### Deliverables + +- PRs for site upkeep, dependency updates, configuration changes, and production hotfixes. +- Verified release and content updates, with tracked operational issues and resolution notes. + +### Ad hoc features + +* fully qualified name: `ift-ts:web:logos:2026q4-logos-website:ad-hoc-features` +* owner: Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Implement prioritized new Logos website features requested during Q4, including new pages, campaign experiences, forms, or integrations as requirements become clear. +Capture requests, agree scope and acceptance criteria with stakeholders, and schedule delivery according to priority and capacity. +Create dedicated roadmap tasks when a request grows into a substantial project. + +#### Deliverables + +- Scoped feature issues with acceptance criteria and stakeholder requirements. +- PRs and released features with validation or stakeholder review results. diff --git a/content/web/status/2026q4-status-website.md b/content/web/status/2026q4-status-website.md new file mode 100644 index 0000000000..ed782902a4 --- /dev/null +++ b/content/web/status/2026q4-status-website.md @@ -0,0 +1,57 @@ +--- +title: Status Website +tags: + - "2026q4" + - "web" + - "status" +draft: false +description: Maintain the Status website, deliver fixes and improvements, and implement prioritized ad hoc features. +--- + +`ift-ts:web:status:2026q4-status-website` + +## Description + +Continue supporting the Status website in Q4 through recurring upkeep, fixes and improvements to existing functionality, and delivery of new features requested during the quarter. +Maintain the marketing, blog, help, and feed experiences developed in previous quarters. +Select concrete work with stakeholders as needs arise and record the scope and acceptance criteria in linked issues. + +## Task List + +### Maintenance + +* fully qualified name: `ift-ts:web:status:2026q4-status-website:maintenance` +* owner: Felicio/Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Keep the Status website and its existing integrations working as dependencies, content, and releases change. +Maintain site-specific dependencies and configuration, CMS and feed integrations, release and download information, and deployment health. +Investigate production failures and ship necessary hotfixes, coordinating shared tooling changes with the Web maintenance commitment. + +#### Deliverables + +- PRs for site upkeep, dependency updates, configuration changes, and production hotfixes. +- Verified content and integration updates, with tracked operational issues and resolution notes. + +### Ad hoc features + +* fully qualified name: `ift-ts:web:status:2026q4-status-website:ad-hoc-features` +* owner: Felicio/Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Implement prioritized new Status website features requested during Q4, including new pages, marketing experiences, blog features, or integrations as requirements become clear. +Capture requests, agree scope and acceptance criteria with stakeholders, and schedule delivery according to priority and capacity. +Create dedicated roadmap tasks when a request grows into a substantial project. + +#### Deliverables + +- Scoped feature issues with acceptance criteria and stakeholder requirements. +- PRs and released features with validation or stakeholder review results. From 49710392a22104ba71ab0895495da6039754e8de Mon Sep 17 00:00:00 2001 From: jinhojang6 Date: Mon, 21 Sep 2026 22:15:44 +0900 Subject: [PATCH 02/10] docs(web): add 2026 Q4 media migration plan and tasks --- .../web/logos/2026q3-logos-media-migration.md | 80 ++++---- .../web/logos/2026q4-logos-media-migration.md | 179 ++++++++++++++++++ 2 files changed, 219 insertions(+), 40 deletions(-) create mode 100644 content/web/logos/2026q4-logos-media-migration.md diff --git a/content/web/logos/2026q3-logos-media-migration.md b/content/web/logos/2026q3-logos-media-migration.md index f552c2f6b2..9d8f091456 100644 --- a/content/web/logos/2026q3-logos-media-migration.md +++ b/content/web/logos/2026q3-logos-media-migration.md @@ -57,11 +57,11 @@ Here's the URL mapping we're aiming for: ### Article detail page: content, footnotes, table of contents -* fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:article-detail-core` -* owner: jinhojang6 -* status: not started -* start-date: 2026/07/07 -* end-date: 2026/07/31 +- fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:article-detail-core` +- owner: Jinho +- status: not started +- start-date: 2026/07/07 +- end-date: 2026/07/31 #### Description @@ -80,11 +80,11 @@ Content is fetched from the existing Strapi CMS. Handle loading, not-found (404) ### Article detail page: Discussion, Related Articles, From The Same Authors -* fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:article-detail-secondary` -* owner: jinhojang6 -* status: not started -* start-date: 2026/07/07 -* end-date: 2026/07/31 +- fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:article-detail-secondary` +- owner: Jinho +- status: not started +- start-date: 2026/07/07 +- end-date: 2026/07/31 #### Description @@ -99,11 +99,11 @@ Port the supporting sections of the article page. That's **Discussion** (comment ### Podcast detail page: layout, YouTube embed, metadata -* fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:podcast-detail-core` -* owner: jinhojang6 -* status: in progress (90%) -* start-date: 2026/07/07 -* end-date: 2026/07/31 +- fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:podcast-detail-core` +- owner: Jinho +- status: in progress (90%) +- start-date: 2026/07/07 +- end-date: 2026/07/31 #### Description @@ -119,11 +119,11 @@ Build the native podcast detail route at `logos.co/media/podcasts//` becomes `https://logos.co/media/article/` +- `https://blog.logos.co/podcasts//` becomes `https://logos.co/media/podcasts//` + +The cutover must preserve query strings, feed subscriber identity, canonical URLs, and access to content. The legacy blog frontend can be retired only after build fallbacks, editor previews, and any API or static-asset dependencies have a confirmed replacement or an explicitly retained route. + +**What changes** + +- The Q3 migration pull request is updated, reviewed, merged, and deployed to production. +- `logos.co/media` becomes the canonical production home for articles and podcast episodes. +- `blog.logos.co` article, podcast, listing, feed, policy, and legacy paths receive agreed permanent redirects. +- The legacy blog frontend is decommissioned once no required build, CMS preview, API, or asset traffic depends on it. + +**What stays** + +- The existing Strapi content source remains in use. Moving content into the `logos-web` content stack is not part of this cutover. +- Article and podcast features delivered in the Q3 implementation remain: rich content, footnotes, table of contents, discussion, related content, media search, feeds, responsive images, and persistent podcast playback. +- CMS and content operations continue while the public frontend moves to `logos.co`. + +**Why this is its own quarter** + +- The Q3 work has become a broad migration touching rendering security, static-export reliability, search, feeds, media assets, SEO, playback, and infrastructure. +- The application deployment and the `blog.logos.co` redirect switch must be sequenced. Redirects cannot be enabled until the matching production pages and feeds are verified. +- Decommissioning the legacy frontend is a separate gate from redirecting public pages because local and CI fallbacks, CMS draft previews, `/api/*`, and legacy assets may still depend on it. + +**Risks** + +- **Unsafe rich content.** Interactive CMS blocks must not execute untrusted scripts with access to the `logos.co` origin. The rendering boundary must be resolved before merge without losing required article behaviour. +- **Static-export reliability.** Media generation, sitemap creation, image processing, feeds, and search indexing depend on external content services. Unbounded requests or hidden fetch failures can make production builds unreliable or publish incomplete output. +- **Redirect gaps.** The Infra issue and the redirect map in the application PR do not yet describe exactly the same path set. Feed, policy, calendar, preview, API, asset, and non-`logos-state` podcast paths need an agreed disposition before the rules are enabled. +- **Subscriber and search continuity.** Incorrect feed IDs, redirect status codes, canonicals, or sitemap entries can create duplicate podcast episodes or delay search-engine migration. +- **Premature decommissioning.** Turning off the old service while builds or CMS previews still use it would break development or editorial workflows even if public article redirects work. + +**Coordination** + +- **Web** owns pull request readiness, production deployment, content parity, feeds, search, SEO output, and post-launch validation. +- **Infra** owns Jenkins credentials, Cloudflare redirect rules, and decommissioning of the legacy blog service. +- **Content / CMS** confirms that editor previews and publishing workflows continue to work before the old frontend is retired. + +## Task List + +### Complete and merge the media migration implementation + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-media-migration:merge-readiness` +- owner: Jinho +- status: not started +- start-date: 2026/10/01 +- end-date: 2026/10/16 + +#### Description + +Bring [logos-co/logos-web#103](https://github.com/logos-co/logos-web/pull/103) up to date with `develop`, resolve conflicts, and close the remaining review issues that block a safe production release. This includes the rich-content execution boundary, React hook ordering, in-page and footnote links, bounded sitemap fetching, and the reported podcast navigation autoplay behaviour. + +Re-run the complete static-export path with production-equivalent content access. Treat a failed content fetch as a build failure where publishing partial or false 404 output would hide an outage. Review the final diff again after conflict resolution because the pull request spans media rendering, search, feeds, image generation, metadata, and global playback state. + +#### Deliverables + +- PR #103 rebased or merged with current `develop`, with conflicts resolved and no accidental loss of either branch's changes. +- Remaining major review threads resolved with code, tests, or a documented accepted decision. +- Interactive media isolated from the `logos.co` origin or sanitised to an agreed security boundary, with required legacy content verified. +- Footnote and heading fragment links, existing `rel` attributes, and external links behaving correctly. +- Bounded content requests for sitemap and generated media assets, with failures visible to the build. +- Podcast navigation tested for unintended autoplay and player state regressions. +- Passing lint, type checks, tests, production build, and static-export smoke checks on the final PR head. + +### Prepare and deploy the production media build + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-media-migration:production-deployment` +- owner: Jinho +- status: not started +- start-date: 2026/10/12 +- end-date: 2026/10/30 + +#### Description + +Work with Infra to add the Strapi and Simplecast credentials requested in [status-im/infra-sites#168](https://github.com/status-im/infra-sites/issues/168) to the Logos Jenkins job before merging. Confirm that development and production builds read the CMS directly and do not silently fall back to the old public blog API. + +Merge and deploy the migration only after the credentialed Jenkins build succeeds. Before any redirect change, verify a representative set of article and podcast pages on `logos.co`, including YouTube, Spotify, Apple Podcasts or direct-audio episodes, rich interactive articles, discussions, search, responsive images, feeds, sitemap entries, metadata, and structured data. + +#### Deliverables + +- Required Jenkins Secret text credentials configured by Infra without exposing their values in repositories, logs, or roadmap files. +- Successful production build using the intended Strapi and Simplecast integrations. +- PR #103 merged and deployed to `logos.co`. +- Representative article and podcast URLs returning 200 with the correct content, canonical, metadata, and structured data. +- Media search, RSS and Atom feeds, sitemap, generated images, discussion, and podcast playback verified in production. +- A recorded rollback point and named owner for launch-day issues. + +### Cut over blog.logos.co redirects and feeds + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-media-migration:redirect-cutover` +- owner: Jinho +- status: not started +- start-date: 2026/10/26 +- end-date: 2026/11/13 + +#### Description + +Reconcile [status-im/infra-sites#168](https://github.com/status-im/infra-sites/issues/168) with the redirect map in PR #103 before Infra changes Cloudflare. Agree the final first-match rule order and the destination for articles, every podcast show, listing pages, feeds, policy pages, calendar, search, the blog home, and unmatched legacy paths. + +Keep the query string on every redirect. Do not redirect CMS preview, API, or asset paths until their consumers have moved. Deploy the application first, verify the destinations, then enable permanent redirects and re-crawl a representative sample. + +#### Deliverables + +- One approved redirect map shared by Web and Infra, including non-`logos-state` shows and explicit handling for feeds, policy pages, calendar, search, previews, APIs, assets, and unmatched paths. +- Cloudflare 301 rules implemented through Infra issue #168 with query strings preserved. +- Legacy feed paths redirected to working feeds on `logos.co` while retaining stable item identifiers so subscribers do not receive duplicate archive entries. +- Verification that old article and episode URLs return one 301 hop to a 200 destination with a self-referencing canonical. +- Verification that temporary exceptions such as required preview, API, and asset paths still return the expected response until their retirement task is complete. +- A rollback procedure for redirect or feed regressions. + +### Remove legacy dependencies and retire the blog frontend + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-media-migration:legacy-retirement` +- owner: Jinho +- status: not started +- start-date: 2026/11/09 +- end-date: 2026/12/04 + +#### Description + +Inventory the remaining requests to `blog.logos.co` after the public cutover. Replace or deliberately retain every dependency used by local development, CI, CMS draft previews, `/api/*`, `/_next/*`, images, icons, robots, or the legacy sitemap. Give CMS editors a working preview destination before removing the old preview frontend. + +When logs and workflow checks show that the legacy frontend is no longer required, coordinate its decommissioning with Infra. This task retires the public blog application, not the Strapi content service still used by `logos.co`. + +#### Deliverables + +- An owner and disposition for every remaining legacy API, preview, and static-asset path. +- Local, CI, preview, and production builds working without the old public blog fallback. +- CMS draft preview and publishing workflows verified against their post-migration destination. +- Traffic or request-log evidence that no required consumer still uses the legacy frontend. +- Legacy blog frontend decommissioned by Infra, with Strapi and other retained content services explicitly excluded. +- Post-decommission checks covering production pages, builds, previews, feeds, search, and redirects. + +### Monitor SEO, content integrity, and operational health + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-media-migration:post-cutover-monitoring` +- owner: Jinho +- status: not started +- start-date: 2026/11/02 +- end-date: 2026/12/31 + +#### Description + +Monitor the migration after redirects are enabled and again after the legacy frontend is retired. Use Search Console, production crawls, analytics, server or CDN logs, and feed checks to find redirect errors, missing content, indexing regressions, broken embeds, build instability, and playback failures. + +Track old URLs moving to redirect status and new `/media` URLs becoming the indexed canonical pages. Fix migration regressions during Q4 and record longer-term content-platform work separately rather than keeping the legacy frontend alive without an explicit reason. + +#### Deliverables + +- Search Console checks confirming new media URLs are discoverable and old blog URLs are reported as redirected. +- Production crawl covering top article and podcast URLs, redirect chains, canonicals, sitemap membership, structured data, images, and internal links. +- Feed validation showing working endpoints and no archive-wide duplicate delivery. +- Monitoring of 404s, redirect loops, media build failures, search failures, and playback errors, with issues linked and assigned. +- A migration closeout note summarising completed cutover work, retained services, known follow-ups, and final ownership. + +## Out of scope for Q4 + +- Migrating article or podcast content out of Strapi into the `logos-web` content repository or another CMS. +- New editorial, community, or podcast features unrelated to completing and stabilising the migration. From 4f07d59d3015ee0dc20049cfc9f802d395bf9277 Mon Sep 17 00:00:00 2001 From: jinhojang6 Date: Mon, 21 Sep 2026 22:37:28 +0900 Subject: [PATCH 03/10] docs(web): update 2026 Q4 Logos website content and migration details --- content/web/logos/2026q4-logos-website.md | 45 ++++++++++++++++++----- 1 file changed, 35 insertions(+), 10 deletions(-) diff --git a/content/web/logos/2026q4-logos-website.md b/content/web/logos/2026q4-logos-website.md index ea3e26c4e2..c2800583c7 100644 --- a/content/web/logos/2026q4-logos-website.md +++ b/content/web/logos/2026q4-logos-website.md @@ -20,11 +20,11 @@ Select concrete work with stakeholders as needs arise and record the scope and a ### Maintenance -* fully qualified name: `ift-ts:web:logos:2026q4-logos-website:maintenance` -* owner: Jinho/JulesFiliot -* status: not started -* start-date: 2026/10/01 -* end-date: 2026/12/31 +- fully qualified name: `ift-ts:web:logos:2026q4-logos-website:maintenance` +- owner: Jinho/JulesFiliot +- status: not started +- start-date: 2026/10/01 +- end-date: 2026/12/31 #### Description @@ -37,13 +37,38 @@ Investigate production failures and ship necessary hotfixes, coordinating shared - PRs for site upkeep, dependency updates, configuration changes, and production hotfixes. - Verified release and content updates, with tracked operational issues and resolution notes. +### Past Present Future: content update and migration + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-website:past-present-future` +- owner: Jinho +- status: not started +- start-date: 2026/10/01 +- end-date: 2026/12/31 + +#### Description + +Continue the Past Present Future work with the Comms team following the Mike experience. +Turn agreed content updates into an implementation-ready plan, including copy, calls to action, journey changes, media, and supporting assets. +Migrate the approved experience and its assets into the existing `logos-web` repository so it can be maintained, deployed, and measured alongside the main Logos website. +Preserve working routes, responsive behaviour, Umami tracking, and event naming through the migration. + +Coordinate with the agency when content, creative assets, interaction design, or technical handover requires their input. +Document ownership, dependencies, and acceptance criteria before work that crosses the Comms, agency, and web teams begins. + +#### Deliverables + +- A prioritised, approved content and asset update list for the post-Mike experience, with owners and acceptance criteria. +- Migration PRs in `logos-web` for the approved experience, routes, assets, responsive behaviour, and analytics integration. +- Desktop and mobile QA covering key journeys, calls to action, video presentation, and Umami event tracking. +- Agency handover and review notes for any work requiring external creative or technical collaboration. + ### Ad hoc features -* fully qualified name: `ift-ts:web:logos:2026q4-logos-website:ad-hoc-features` -* owner: Jinho/JulesFiliot -* status: not started -* start-date: 2026/10/01 -* end-date: 2026/12/31 +- fully qualified name: `ift-ts:web:logos:2026q4-logos-website:ad-hoc-features` +- owner: Jinho/JulesFiliot +- status: not started +- start-date: 2026/10/01 +- end-date: 2026/12/31 #### Description From 7d92c3fe9ba0b1954ccb0a37d178fb343376b1f9 Mon Sep 17 00:00:00 2001 From: jinhojang6 Date: Mon, 21 Sep 2026 22:47:50 +0900 Subject: [PATCH 04/10] docs(web): add 2026 Q4 logos media migration link --- content/web/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/web/index.md b/content/web/index.md index 7937519288..25fbf3e4f1 100644 --- a/content/web/index.md +++ b/content/web/index.md @@ -31,6 +31,7 @@ The unit's work directly supports IFT's strategic objective of scaling project c ### `logos:` +* [[web/logos/2026q4-logos-media-migration|logos-media-migration]] * [[web/logos/2026q4-logos-website|logos-website]] ## 2026q3 From d267da558fe468ce0c3b9de2986004ab4e7262db Mon Sep 17 00:00:00 2001 From: jinhojang6 Date: Tue, 22 Sep 2026 00:40:45 +0900 Subject: [PATCH 05/10] docs(web): add Logos Zine section with deliverables and implementation details --- content/web/logos/2026q4-logos-website.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/content/web/logos/2026q4-logos-website.md b/content/web/logos/2026q4-logos-website.md index c2800583c7..0f9b3dad6f 100644 --- a/content/web/logos/2026q4-logos-website.md +++ b/content/web/logos/2026q4-logos-website.md @@ -62,6 +62,29 @@ Document ownership, dependencies, and acceptance criteria before work that cross - Desktop and mobile QA covering key journeys, calls to action, video presentation, and Umami event tracking. - Agency handover and review notes for any work requiring external creative or technical collaboration. +### Logos Zine + +- fully qualified name: `ift-ts:web:logos:2026q4-logos-website:logos-zine` +- owner: Jinho +- status: not started +- start-date: 2026/10/12 +- end-date: 2026/12/31 + +#### Description + +Deliver the initial Logos Zine page described in [logos-web#172](https://github.com/logos-co/logos-web/issues/172), at `logos.co/zine`. +The first release will list the available issue or issues and provide PDF downloads, while keeping the content structure flexible for future issues. +It will be responsive on desktop and mobile, but will not include a web-based reader in this phase. + +Before implementation, collect the final PDF, approved copy and assets, and a design wireframe or reference sites from stakeholders. + +#### Deliverables + +- A responsive `logos.co/zine` page listing the current issue and supporting additional issues without a page redesign. +- A verified PDF download for each published issue. +- Final copy, PDF, assets, and design references documented before implementation. +- QA evidence for desktop and mobile presentation, issue links, and downloads. + ### Ad hoc features - fully qualified name: `ift-ts:web:logos:2026q4-logos-website:ad-hoc-features` From af3e432569dea060646670a5b09775b0f238ca90 Mon Sep 17 00:00:00 2001 From: JulesFILIOT Date: Tue, 22 Sep 2026 16:51:17 +0200 Subject: [PATCH 06/10] docs(web): add 2026 Q4 admin-acid commitment --- content/web/ift/2026q4-admin-acid.md | 80 ++++++++++++++++++++++++++++ content/web/index.md | 1 + 2 files changed, 81 insertions(+) create mode 100644 content/web/ift/2026q4-admin-acid.md diff --git a/content/web/ift/2026q4-admin-acid.md b/content/web/ift/2026q4-admin-acid.md new file mode 100644 index 0000000000..f0016b2f6d --- /dev/null +++ b/content/web/ift/2026q4-admin-acid.md @@ -0,0 +1,80 @@ +--- +title: Admin Acid +tags: + - "2026q4" + - "web" + - "ift" +draft: false +description: Maintain the Logos admin dashboard -- Notion infrastructure, Notion-linked emailing, and ad hoc requests from operators. +--- + +`ift-ts:web:ift:2026q4-admin-acid` + +## Description + +[admin-acid.logos.co](https://admin-acid.logos.co/) ([acid-info/admin-acid.logos.co](https://github.com/acid-info/admin-acid.logos.co)) is the internal admin dashboard behind the BD funnel, newsletters, calendar, and contributor data. +Q4 keeps the two surfaces that operators depend on daily working: the Notion integration layer (client, data sources, webhooks, block rendering, file uploads) and the emailing features built on top of it (auto-reply templates, funnel profile emails, internal notification templates, one-pager delivery). +The funnel and email lineage is recorded in [[web/logos/2026q3-logos-crm|Logos CRM]]; this commitment covers upkeep and incoming requests rather than new CRM scope. +Work arrives from operators and stakeholders during the quarter, so scope is agreed per request and tracked in repository issues. + +## Task List + +### Notion infrastructure maintenance + +* fully qualified name: `ift-ts:web:ift:2026q4-admin-acid:notion-infrastructure` +* owner: JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Keep the Notion integration layer working as the Notion API, the workspace schema, and operator usage change. +Covers the Notion client and authentication, data source and database queries, incoming Notion webhooks and automations, block rendering, and file uploads. +Absorb Notion API version bumps and deprecations, repair syncs that drift when operators rename or restructure properties, and harden error handling and logging so failures surface instead of silently dropping records. + +#### Deliverables + +- PRs in [acid-info/admin-acid.logos.co](https://github.com/acid-info/admin-acid.logos.co) updating the Notion client, data source queries, webhook handling, and file uploads. +- Verified fixes for broken Notion syncs and automations, with tracked issues and resolution notes. +- Operator documentation for Notion property and database changes that require a code or configuration update. + +### Notion-linked emailing features + +* fully qualified name: `ift-ts:web:ift:2026q4-admin-acid:notion-emailing` +* owner: JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain and extend the emailing features driven by Notion records and automations: endpoint-based auto-reply templates for form submissions, funnel profile emails, internal notification templates with per-template recipients, one-pager delivery, and Ghost newsletter subscription flows. +Keep template editing usable for non-engineers, keep merge fields in step with the Notion schema, and keep delivery observable through MailGun message ids and structured logs. +Ship the template and trigger changes stakeholders request during the quarter, and fix delivery failures, bounces, and mis-addressed sends. + +#### Deliverables + +- PRs for auto-reply, profile email, and internal notification template changes. +- Verified end-to-end sends from Notion automation trigger to delivered email, with failures logged and resolved. +- Updated operator notes covering how to add a template, edit copy, and connect a Notion automation. + +### Ad hoc requests + +* fully qualified name: `ift-ts:web:ift:2026q4-admin-acid:ad-hoc-requests` +* owner: Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Handle requests that reach the admin dashboard during Q4 outside the two maintenance tracks above: new dashboard views, calendar and contributor data changes, newsletter operations, access and configuration changes, and small features asked for by People Ops, Ecodev, or BD. +Capture each request as an issue, agree scope and acceptance criteria with the requester, and schedule delivery by priority and capacity. +Create a dedicated roadmap task when a request grows into a substantial project. + +#### Deliverables + +- Scoped issues with acceptance criteria for each accepted request. +- PRs and deployed changes, validated with the requester. +- Tracked list of declined or deferred requests with the reason recorded. diff --git a/content/web/index.md b/content/web/index.md index 25fbf3e4f1..e3d6dc45d3 100644 --- a/content/web/index.md +++ b/content/web/index.md @@ -22,6 +22,7 @@ The unit's work directly supports IFT's strategic objective of scaling project c ### `ift:` +* [[web/ift/2026q4-admin-acid|admin-acid]] * [[web/ift/2026q4-demos|demos]] * [[web/ift/2026q4-maintenance|maintenance]] From 78a244461a13ee75d9e58230a463d7aa846b10d4 Mon Sep 17 00:00:00 2001 From: JulesFILIOT Date: Tue, 22 Sep 2026 16:51:23 +0200 Subject: [PATCH 07/10] docs(web): add 2026 Q4 status wallet extension commitment --- content/web/index.md | 1 + .../status/2026q4-status-wallet-extension.md | 59 +++++++++++++++++++ 2 files changed, 60 insertions(+) create mode 100644 content/web/status/2026q4-status-wallet-extension.md diff --git a/content/web/index.md b/content/web/index.md index e3d6dc45d3..5aa52e049d 100644 --- a/content/web/index.md +++ b/content/web/index.md @@ -28,6 +28,7 @@ The unit's work directly supports IFT's strategic objective of scaling project c ### `status:` +* [[web/status/2026q4-status-wallet-extension|status-wallet-extension]] * [[web/status/2026q4-status-website|status-website]] ### `logos:` diff --git a/content/web/status/2026q4-status-wallet-extension.md b/content/web/status/2026q4-status-wallet-extension.md new file mode 100644 index 0000000000..26dfb680b4 --- /dev/null +++ b/content/web/status/2026q4-status-wallet-extension.md @@ -0,0 +1,59 @@ +--- +title: Status Wallet Extension +tags: + - "2026q4" + - "web" + - "status" +draft: false +description: Maintain the Status Wallet browser extension and deliver prioritized ad hoc requests during Q4. +--- + +`ift-ts:web:status:2026q4-status-wallet-extension` + +## Description + +Q4 support for the Status Wallet browser extension in the [status-im/status-web](https://github.com/status-im/status-web) monorepo, continuing from [[web/status/2026q3-status-wallet-extension|2026q3-status-wallet-extension]]. +The quarter has no fixed feature programme: it covers keeping the shipped extension healthy across releases and store publication, and delivering requests that arrive from stakeholders during the quarter. +Select concrete work with stakeholders as needs arise and record scope and acceptance criteria in linked issues. + +## Task List + +### Maintenance + +* fully qualified name: `ift-ts:web:status:2026q4-status-wallet-extension:maintenance` +* owner: Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Keep the wallet extension working as dependencies, chain and RPC providers, and browser extension platforms change. +Covers release coordination and Chrome Web Store publication, extension-specific dependencies and build configuration, transaction reliability and fee estimation, session and account recovery, dApp connection handling, and balance and price data sources. +Investigate production failures reported by users or stakeholders and ship hotfixes, coordinating shared tooling changes with the Web maintenance commitment. + +#### Deliverables + +- PRs in `status-im/status-web` for upkeep, dependency updates, and production hotfixes. +- Published extension releases on the [Chrome Web Store](https://chromewebstore.google.com/detail/status-portfolio-wallet-b/opkfeajbclhjdneghppfnfiannideafj), with release notes and coordination threads linked. +- Tracked issues for production failures, with reproduction steps and resolution notes. + +### Ad hoc requests + +* fully qualified name: `ift-ts:web:status:2026q4-status-wallet-extension:ad-hoc-requests` +* owner: Jinho/JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Implement prioritized wallet extension requests raised during Q4: new chain or asset coverage, wallet flow changes, dApp integration requirements, and design or copy updates as requirements become clear. +Capture each request as an issue, agree scope and acceptance criteria with stakeholders, and schedule delivery by priority and capacity. +Create a dedicated roadmap task when a request grows into a substantial project. + +#### Deliverables + +- Scoped issues with acceptance criteria and stakeholder requirements. +- PRs and released changes, with tests covering the affected wallet flows. +- Validation or stakeholder sign-off recorded per delivered request. From b9c94fb628d32964bf2dbc9b5c5bc1e878242436 Mon Sep 17 00:00:00 2001 From: JulesFILIOT Date: Tue, 22 Sep 2026 16:51:28 +0200 Subject: [PATCH 08/10] docs(web): split AI tooling out of 2026 Q4 maintenance Track ai-review, ai-auto-fix, and ai-docs-sync in their own commitment. --- content/web/ift/2026q4-ai-tooling.md | 80 +++++++++++++++++++++++++++ content/web/ift/2026q4-maintenance.md | 30 +--------- content/web/index.md | 1 + 3 files changed, 84 insertions(+), 27 deletions(-) create mode 100644 content/web/ift/2026q4-ai-tooling.md diff --git a/content/web/ift/2026q4-ai-tooling.md b/content/web/ift/2026q4-ai-tooling.md new file mode 100644 index 0000000000..0f17fe3d74 --- /dev/null +++ b/content/web/ift/2026q4-ai-tooling.md @@ -0,0 +1,80 @@ +--- +title: AI Tooling +tags: + - "2026q4" + - "web" + - "ift" +draft: false +description: Build and maintain the team's shared AI workflow tooling; ai-review, its ai-auto-fix companion, and ai-docs-sync. +--- + +`ift-ts:web:ift:2026q4-ai-tooling` + +## Description + +Three tools are in scope: [ai-review](https://github.com/acid-info/ai-review), already consumed by `status-im/status-web`, `logos-co/logos-web`, and `acid-info/admin-acid.logos.co`; an **ai-auto-fix** companion that turns accepted ai-review findings into a patch, not yet started; and [ai-docs-sync](https://github.com/acid-info/ai-docs-sync), in development. +All three ship as reusable GitHub workflows pinned to `@v1`, with zero npm dependencies, so a tool or model change is one edit in the shared repository rather than one per consumer. +Human approval before merge stays a hard requirement for every tool here. + +## Task List + +### ai-review maintenance and tuning + +* fully qualified name: `ift-ts:web:ift:2026q4-ai-tooling:ai-review` +* owner: JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain [acid-info/ai-review](https://github.com/acid-info/ai-review) as the shared PR reviewer for `logos-co`, `status-im`, and `acid-info` repositories. +Keep the dual-model review plus synthesis pipeline reliable as provider APIs and models change, tune per-repository context and guideline files to cut false positives, and refine diff packing, path filtering, and severity thresholds. +Keep the degraded paths honest: a single-model review when one provider is down, a local merge when synthesis fails, and a posted body that says the review was partial. +Onboard remaining Web repositories and keep the `@v1` tag stable for consumers. + +#### Deliverables + +- PRs in `acid-info/ai-review` for model updates, prompt and threshold tuning, and pipeline fixes. +- Repository-specific guideline and config files in consumer repositories. +- Additional consumer repositories onboarded via `.github/workflows/ai-review.yml`. +- A short assessment of signal versus noise, drawn from reviewed PRs, with the tuning changes it drove. + +### ai-auto-fix companion + +* fully qualified name: `ift-ts:web:ift:2026q4-ai-tooling:ai-auto-fix` +* owner: JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Build an **ai-auto-fix** companion to ai-review that takes review findings and produces a patch the author can accept, rather than leaving every finding as manual follow-up work. +Nothing exists yet, so the task starts from specification: which finding severities and categories are eligible, how a fix is requested (a comment command on the PR, or opt-in per finding), how the patch is delivered (a commit pushed to the PR branch, or a suggested-change comment), and what the tool must refuse to touch. +Reuse the ai-review pipeline's shape -- reusable workflow, zero npm dependencies, Node 22 `fetch`, pinned `@v1` -- and keep every produced change inside normal PR review with no branch-protection bypass. + +#### Deliverables + +- Written specification covering eligible findings, trigger mechanism, patch delivery, and refusal rules. +- Prototype workflow producing patches against real ai-review findings on Web repositories. +- Documented guardrails: disallowed change types, secret handling, and required human approval before merge. + +### ai-docs-sync + +* fully qualified name: `ift-ts:web:ift:2026q4-ai-tooling:ai-docs-sync` +* owner: JulesFiliot +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Finish [acid-info/ai-docs-sync](https://github.com/acid-info/ai-docs-sync), which keeps a repository's documentation in step with its code by triaging each push, rewriting affected docs with one model, checking the rewrite with a second, and running mechanical gates. + +#### Deliverables + +- Merged publishing stage: rolling branch and PR, cursor move, generated PR body, with unit tests. +- End-to-end runs on a real repository, including unmerged-edit carry-forward and collapsed-push handling. +- `v1` tag cut and the README status banner removed. +- First consumer repository onboarded via `.github/workflows/docs-sync.yml`, with the resulting docs PRs linked. diff --git a/content/web/ift/2026q4-maintenance.md b/content/web/ift/2026q4-maintenance.md index 90feada692..a538bb2b48 100644 --- a/content/web/ift/2026q4-maintenance.md +++ b/content/web/ift/2026q4-maintenance.md @@ -5,7 +5,7 @@ tags: - "web" - "ift" draft: false -description: Maintain shared Web tooling, dependencies, and deployment workflows, and improve AI-assisted development practices. +description: Maintain shared Web tooling, dependencies, and deployment workflows across the team's repositories. --- `ift-ts:web:ift:2026q4-maintenance` @@ -14,9 +14,9 @@ description: Maintain shared Web tooling, dependencies, and deployment workflows Continue recurring Web maintenance from Q3, focusing on common tooling and workflows used by the team's websites. Keep shared dependencies, CI, preview deployments, and hosting integrations reliable. -Build on Q3 AI review workflows and improve agent-assisted debugging, testing, and implementation across Web repositories. Triage incoming requests with the team and track scope, priorities, and follow-up ownership. -Record site-specific upkeep and implementation under [[web/logos/2026q4-logos-website|Logos Website]] or [[web/status/2026q4-status-website|Status Website]], with shared changes tracked here once. +Record site-specific upkeep and implementation under [[web/logos/2026q4-logos-website|Logos Website]], [[web/status/2026q4-status-website|Status Website]], [[web/status/2026q4-status-wallet-extension|Status Wallet Extension]], or [[web/ift/2026q4-admin-acid|Logos Admin]], with shared changes tracked here once. +Shared AI workflow tooling is tracked separately under [[web/ift/2026q4-ai-tooling|AI Tooling]]. ## Task List @@ -37,27 +37,3 @@ Resolve shared infrastructure or tooling failures, coordinate with Infra where n - PRs updating shared dependencies, tooling, and CI or deployment configuration. - Verified fixes for shared workflow failures and relevant operational documentation. - -### AI and agentic workflow improvements - -* fully qualified name: `ift-ts:web:ift:2026q4-maintenance:ai-agentic-improvements` -* owner: JulesFiliot -* status: not started -* start-date: 2026/10/01 -* end-date: 2026/12/31 - -#### Description - -Continue the AI and agent-assisted development work from Q3: -- Improve the existing shared AI PR review workflow, tune repository context and instructions, and reduce false positives. -- Use agents to investigate failures, reproduce bugs, and propose fixes that developers validate. -- Draft or extend unit, integration, and E2E tests with agent assistance, reviewing assertions and checking for flakiness before adoption. -- Extend agent-authored changes for scoped maintenance work, keeping normal PR review and human approval before merge. -- Document effective workflows, handling of sensitive information, and lessons from actual usage so the team can reuse successful approaches. - -#### Deliverables - -- PRs improving shared AI review automation and repository-specific agent instructions. -- Documented examples of agent-assisted debugging, test coverage, and maintenance changes, linked to reviewed PRs. -- Updated team guidance for review, debugging, testing, and agent-authored changes. -- A short assessment of time saved, review quality, false positives, and remaining limitations. diff --git a/content/web/index.md b/content/web/index.md index 5aa52e049d..486f37e58a 100644 --- a/content/web/index.md +++ b/content/web/index.md @@ -23,6 +23,7 @@ The unit's work directly supports IFT's strategic objective of scaling project c ### `ift:` * [[web/ift/2026q4-admin-acid|admin-acid]] +* [[web/ift/2026q4-ai-tooling|ai-tooling]] * [[web/ift/2026q4-demos|demos]] * [[web/ift/2026q4-maintenance|maintenance]] From 856b27f30da0b01ffa292d0a1bb5150ad3bf8883 Mon Sep 17 00:00:00 2001 From: JulesFILIOT Date: Tue, 22 Sep 2026 16:51:33 +0200 Subject: [PATCH 09/10] docs(web): remove felicio from 2026 Q4 status website owners --- content/web/status/2026q4-status-website.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/web/status/2026q4-status-website.md b/content/web/status/2026q4-status-website.md index ed782902a4..9625c8f740 100644 --- a/content/web/status/2026q4-status-website.md +++ b/content/web/status/2026q4-status-website.md @@ -21,7 +21,7 @@ Select concrete work with stakeholders as needs arise and record the scope and a ### Maintenance * fully qualified name: `ift-ts:web:status:2026q4-status-website:maintenance` -* owner: Felicio/Jinho/JulesFiliot +* owner: Jinho/JulesFiliot * status: not started * start-date: 2026/10/01 * end-date: 2026/12/31 @@ -40,7 +40,7 @@ Investigate production failures and ship necessary hotfixes, coordinating shared ### Ad hoc features * fully qualified name: `ift-ts:web:status:2026q4-status-website:ad-hoc-features` -* owner: Felicio/Jinho/JulesFiliot +* owner: Jinho/JulesFiliot * status: not started * start-date: 2026/10/01 * end-date: 2026/12/31 From edbf207bcfbd61b2192d8c0e2425d24a2963249a Mon Sep 17 00:00:00 2001 From: jinhojang6 Date: Wed, 23 Sep 2026 00:36:35 +0900 Subject: [PATCH 10/10] docs(web): mark 2026 Q3 logos media migration tasks done except redirects-infra --- content/web/logos/2026q3-logos-media-migration.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/web/logos/2026q3-logos-media-migration.md b/content/web/logos/2026q3-logos-media-migration.md index cde9321a43..a3093a6873 100644 --- a/content/web/logos/2026q3-logos-media-migration.md +++ b/content/web/logos/2026q3-logos-media-migration.md @@ -59,7 +59,7 @@ Here's the URL mapping we're aiming for: - fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:article-detail-core` - owner: Jinho -- status: in progress (75%) +- status: done - start-date: 2026/07/07 - end-date: 2026/07/31 @@ -82,7 +82,7 @@ Content is fetched from the existing Strapi CMS. Handle loading, not-found (404) - fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:article-detail-secondary` - owner: Jinho -- status: in progress (25%) +- status: done - start-date: 2026/07/07 - end-date: 2026/07/31 @@ -101,7 +101,7 @@ Port the supporting sections of the article page. That's **Discussion** (comment - fully qualified name: `ift-ts:web:logos:2026q3-logos-media-migration:podcast-detail-core` - owner: Jinho -- status: in progress (90%) +- status: done - start-date: 2026/07/07 - end-date: 2026/07/31 @@ -121,7 +121,7 @@ Build the native podcast detail route at `logos.co/media/podcasts//