Autocomplete: Problem exploration and recommendations

Objective

Understand the current developer experience when using Pajamas in development environments, validate whether improvements are needed, and provide recommendations for potential solutions.

Open questions

Current State Analysis

How does (or doesn't) it work now to use Pajamas while coding?

  • Document the current experience of working with Pajamas components in common IDEs or other locations
  • Identify existing pain points or gaps in the developer workflow
  • Where should autocomplete functionality exist? (IDE and other potential locations)
  • What types of information should be autocompleted? (component names, props, values, patterns, etc.)

User Needs Validation

What expectations do our users have for autocompletion or similar functionality?

  • Gather input from frontend developers
  • Review relevant findings from the Pajamas sentiment survey
  • Synthesize common themes and priorities from developer feedback

Competitive Analysis

What are other design systems doing for this?

  • Research how established design systems handle surfacing their libraries to developers
  • Identify common best practices
  • Document approaches that could be applicable to Pajamas

Deliverables

  1. Problem Validation Summary: Clear statement of whether there is a genuine need for improved autocomplete, code suggestions or other similar functionality
  2. Current State Documentation: Description of how Pajamas currently works (or doesn't work) in common development environments
  3. Competitive Analysis Report: Quick summary of approaches taken by other design systems, with relevant examples
  4. Recommendations: Proposed solution(s) with rationale for why they would address the identified needs
  5. Feasibility Assessment:
    • Evaluation of whether recommended solutions are feasible for Pajamas
    • High-level effort estimate (small/medium/large)
    • Rough breakdown of implementation steps and potential timeline

Out of Scope for this issue

  • Actual implementation of any solutions
  • Detailed technical specifications
  • Creation of prototypes or proof-of-concepts

Target Milestone

18.6

Edited by Paul Wright