7-30 follow up sdk

Stakeholders & Participants

  • Core team on call: Jen, Rosa, Devin, Kelly, Jonathan, Gary
  • Product-line contacts mentioned
    • MSP (incl. Jen’s single missed meeting)
    • Wireless connectivity team
    • Processors team
    • Ian Clark (primary dev resource; retiring; presently on solar re-architecture)
    • Hetel + technical group (owning discovery research + POC build)
    • Terry Wang, Doug, Sarah Baxter, Juan Vargas (names surfaced when recalling dev resources)

Current State of the STK-Style Diagram

  • Multiple resolved STK diagrams already exist; MST variant still “in progress.”
  • Design shape is locked: pocket with words + description on the side.
  • No intent to redesign component for processors or other groups.
  • Goal now = populate with actual content to prove feasibility.

Content Requirements & Proof of Concept (POC)

  • Hetel requested multiple examples (≥ 2) rather than a single instance to validate POC.
  • Draft content acceptable; does not need to be “final-final.”
    • Devin can pre-fill activity forms as draft.
  • Two pipelines for sample content
    1. Wireless (already have draft)
    2. MSP (believed finishable by August; weekly check-ins)
  • Activity form completion: Devin volunteers to fill for teams if format is clear.

Design Considerations & User Journey

  • Diagram may live in multiple contexts:
    • Design & Development page (web)
    • Individual software folders (OBN)
  • Call-to-Action (CTA) varies by context
    • E.g., “Download the SDK” button behaves differently on overview vs. folder page.
  • Need a robust, “future-proof” diagram: build full capability even if not used immediately.
  • Template updates for Design & Development pages must anticipate TI Developer’s Zone changes.

Clickable Links Debate

  • Original idea: make every link in diagram clickable.
  • Decision trend: NOT clickable to avoid user confusion; diagram is not a comprehensive index.
    • Intention is to drive traffic toward directories & T-Reps instead.
  • Cleaning up directories/T-Reps becomes a parallel motivation.

Rebranding of DP Studio

  • DP Studio → new brand (umbrella for design tools)
    • Impacts Connectivity, MSP, ASM, other MCU lines
    • Processors likely not impacted.
  • Rebrand affects:
    • CTA labels
    • Design & Development templates
    • TI Developer’s Zone landing page (may need interactive graphic)

Timeline & Deadlines (All 2024)

  • Week of Aug 14 (Wed) – use MSP weekly meeting as target “wrap” for MSP content.
  • Aug 6–10 – schedule second Wireless/Connectivity touch-point.
  • Week of Aug 18 – deliver solid, final content (≥ 2 examples) to dev team.
  • Drafts could arrive earlier but development cannot start until content is locked.
  • Sprint dependency: missing lock-date burns the scheduled sprint.

Development & Sprint Planning

  • Dev organization works in sprints; need confirmed content before they commit.
  • Primary dev contact: Ian Clark; transition risk as he approaches retirement.
  • Question: which sprint can this POC land in? Depends on content ready-date and Ian’s bandwidth.
  • Authoring approach
    • Ideal: auto-populate from database/software BOM (future, next year).
    • Practical now: manual authoring; likely via AEM Content Fragments.

Next Steps & Action Items

  1. Jen → create summary slides (“golden