microsoft / microsoft/AdaptiveCards

[Designer] Needs to be more flexible and intuitive

Open
#3,934 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Designer Request
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

  • It has some great basic features, but I would like to see a lot more flexibility and a wider selection of css design elements. I always end up using JSfiddle to debug the json code, due to a more user friendly experience especially when it comes to counting columns/ character positioning.

  • Colour picker

  • Microsoft icons (that can be used to signify what the card is relating to, rather than adding an image), or even just the ability to create predefined icons (by uploading image to inbuilt converter that makes it base64)

  • Ability to collapse, expand, and hide lines in Card Payload Editor.

  • Copy and paste

  • The SharePoint image issue needs to be fixed asap please. I can only store my images and attachments in SharePoint, and I use the Teams flow bot for all my adaptive cards.

  • Highlighting the code in the Card Payload Editor when an element on the card is clicked, the same way the element name is highlighted in the Card Structure.

  • Additional settings that override those in the end-client. E.g. I would like to remove the footer text when the card shows up in Teams, but there isn't a setting for this in Teams, so making changes in the designer that are then carried over would be great.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points and combines several designer, editor, icon, SharePoint, and Teams requests. Start by splitting the requested changes into separately scoped issues and identifying the relevant designer entry points; each resulting issue should define one behavior and its completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.