search

finos / a11y-theme-builder

DesignOps toolchain theme builder for accessibility inclusion using Atomic Design.
Apache License 2.0
46 stars 69 forks source link

[GHC] Workshop 1 Feeback - Sneha Alluru #1041

Open SnehaAllur opened 1 month ago

SnehaAllur commented 1 month ago

Session 1

Problems

  1. Theme Builder does not offer a clear solution for users with existing coded components

Select one problem above to work on this session. Delete the two problems that you won't focus on

How Might empower users that have existing code or want to use AI generated code import that and integrate that within theme builder? BYOC (bring your own code)

The facilitator will prompt you to convert the problem that was chosen to opportunities using the How Might We (HMW) method

  1. How might we show a preview of what has been imported?
  2. How might we integrate with anima?
  3. How might we expose code snippets within team builder to be edited? 4. How might we let the user select their code base?
  4. How might we let the user categorize their code into atomic categories?
  5. How might we report errors in the package?
  6. How might we auto-render figma components from code?
  7. How might we deal with security/ privacy issues around code that has been imported?
  8. How might we autoselect the code language?

After you have at least 10 HMWs, select the one that you believe has the most potential to generate impact

Make bold the HMW that you selected.

Brainstorm

Bring your HMW and post it here: "4. How might we let the user select their code base?"

Brainstorm on possible solutions for the selected HMW and post one solution per numbered list item.

Scratch pad

All ideas are good ideas!

  1. Solution 1: Theme builder can integrate with several coding platforms 2. Solution 2: Theme builder can allow users to select their code base by auto-generating from pre-existing code bases that the user has (based on the user's history)
  2. Solution 3: Set up an API to easily merge your existing code with the Theme Builder.
  3. Solution 4: Use a tool that converts different code formats into something the Theme Builder can use.
  4. Solution 5: Offer training materials and documentation to help users easily integrate and use their coded components in the Theme Builder 6. Solution 6: Add a code editor within the Theme Builder that supports various programming languages and frameworks
  5. Solution 7: Add a preview feature so users can see how their coded components will look and function in the Theme Builder before committing
  6. Solution 8: Create an import bot to walk users through the process of integrating their coded components step-by-step
  7. Solution 9: Enable integration with popular version control systems like Git, allowing users to manage and sync their code bases with the Theme Builder 10. Solution 10: Introduce a modular framework where users can select and plug in different code bases as modules to ensure compatibility and flexibility

Before you go, make bold your top three solutions.

CONGRATS! You have become an Accessibility Theme Builder contributor.

Join our Slack: https://github.com/finos/a11y-theme-builder/wiki/Communication#communication-channels

Join our weekly calls: https://github.com/finos/a11y-theme-builder/wiki/Communication#meetings

Contribute: Reach out to a maintainer and get started today!