Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Time

Item

Presenter

Notes

Standard Page Layouts

Epic:

Jira Legacy
serverSystem JIRA
serverId13fd1930-5608-3aac-a5dd-21b934d3a4b4
keyPAR-396

Add to Paragon Figma library:

Jira Legacy
serverSystem JIRA
serverId13fd1930-5608-3aac-a5dd-21b934d3a4b4
keyPAR-404

Develop the component:

Jira Legacy
serverSystem JIRA
serverId13fd1930-5608-3aac-a5dd-21b934d3a4b4
keyPAR-403


Notes

  • Responsive layouts are a recurring pain point.

    • Communication between design + engineers.

    • Having responsive functionality

  • Ben: Envisions something like a menu

    • Different ways to organize content

    • For design to look at predefined rules

      • This would be preferred.

    • For engineering, to pick existing Paragon component based on the above rules.

    • Communication

      • Training

      • Spacing (e.g., margins, padding).

      • Extra annotations by designers?

      • Extra info in the Figma library?

      • Content layout stuff might help with this.

  • Next steps

    • Move forward with PAR-404

BenW

  • Where is the (communication) line between external vs. internal for giving feedback + having collaborative discussions?

    • Should there be a line?

    • “Should we be wasting people’s time?”




Tech Lead’s capacity between Paragon and Enterprise.

  • My primary focus is on Enterprise work and supporting the Enterprise Engineering teams.

  • Not enough time Time constrained to create a more fleshed out technical roadmap for Paragon; most .

    • Most of the existing, prioritized technical tasks in the backlog are in progress or have been shipped.

    • When Raccoon Gang needs additional work and there’s not much ready to go from a design POV, I’m largely thinking of new, technical tasks in an ad hoc, as-needed manner.

    • Without a more constant stream of work coming from design → engineering, I don’t currently have the bandwidth to brainstorm and plan impactful technical contributions to populate the technical backlog for when there isn’t as much work ready for engineering (i.

    Not enough
    • e, Raccoon Gang).

  • Limited in time to think strategically about Paragon and do things like the Engineering from technical perspective.

    • Survey what other design systems are doing.

    • Conducting engineering 1:1s with staff.

  • Ideas:

    • Work in 2-week sprints, with design + engineering collaborating in creating a backlog for Raccoon Gang design+engineering.

    • Supplement other folks that could help Adam, e.g. code reviews?

Marco

Product Pulse / Open edX update re: recent Paragon work

  • considering when this would make sense to author / pull together makes sense, don't have to commit to any specific timeline

...