Skip to main content

Idea pipeline

Filter by idea status

Filter by product

1870 Ideas

Hailey Hullinger
Hailey HullingerLucid product team

How do you want to edit and use Mermaid diagrams in Lucid?Seeking Feedback

Hi everyone,I'm Hailey, a product manager on the team working on Mermaid support in Lucid. Thank you to everyone who shared their thoughts in some earlier Mermaid threads. A lot of what you told us is shaping what we are building now, and I would love to keep the conversation going.Where things stand today: you can paste Mermaid code into Lucid and get a diagram on the canvas. For flowcharts, we generate native Lucid shapes you can select and edit. Other Mermaid diagram types go through a static image generator. We are close to launching two-way syncing, so that basic changes you make on the canvas (editing text, adding or removing shapes and lines) update your Mermaid code.We are working out what to do next, and we want your input before we decide. This post covers two things: what you want to do with a Mermaid diagram once it is on the canvas, and which diagram types matter most to you.What we are hoping to learnHow much you want to edit Mermaid diagrams on the canvas, and what kinds of edits Which diagram types you use most, and how well the current experience works for them Where the current experience gets in your wayPart 1: Editing on the canvasWhere does your Mermaid code come from (written by hand, generated by an AI tool, pulled from a repo or docs)? After your diagram is in Lucid, what do you usually want to change? For example: text, adding or removing shapes, rearranging layout, colors and styling, changing shape types, rerouting lines. Do basic edits (text, shapes, lines) cover what you need, or do you want to do more complex edits and styling from the canvas? If so, what is the first thing you would want to do? When you make changes on the canvas, how important is it that your Mermaid code stays up to date? What do you do with that code afterward (store it in a repo, paste it into docs, give it back to an AI tool)?Part 2: Diagram typesWhich Mermaid diagram types do you use most? (Flowchart, sequence, class, state, ERD, Gantt, something else?) Flowcharts currently come in as editable Lucid shapes. If your diagram type is not a flowchart, how does the current experience work for you? What is missing or frustrating? If sequence diagrams (or another type you use) came in as editable Lucid shapes the way flowcharts do, how would that change how you use Lucid with Mermaid? What would you do with them that you can't today?Fill in the blank (optional)The one thing I wish I could change on a Mermaid diagram in Lucid is ________. I would use Mermaid in Lucid much more if ________ diagrams were supported as editable shapes.Any detail helps, including your role, the tools you use alongside Lucid, and how often you work with Mermaid. Screenshots or example code are welcome if you are able to share them.Thank you for taking the time. We read every reply, and your answers directly shape what we prioritize.

Hailey Hullinger
Hailey HullingerLucid product team

How would you want to export Lucid diagrams as text (Mermaid, JSON and more)?Seeking Feedback

Hi everyone,I'm Hailey, a product manager on the team working on Mermaid and diagram-as-code in Lucid. Many of you have told us you want to get diagrams out of Lucid and into text form, and we want to make sure we build the right thing.Today, you can export a Lucid diagram as JSON and a few other image formats. We do not currently export to Mermaid or to other text formats that AI tools tend to work with most. Before we decide what to build, we would like to understand how you would use a text version of a diagram and which formats matter to you.What we are hoping to learnWhat you want to do with a text version of a diagram Which formats you would choose, and why What a good export needs to look like for your workflowQuestionsWhat would you use a text version of your diagram for? For example: storing it in a repo next to code, giving context to an AI tool or coding assistant, embedding it in documentation or a README, version control and review, or something else. Which formats would you want? Mermaid, JSON, YAML, PlantUML, D2, Graphviz DOT, XML, Markdown description, plain-language summary, or something else? If you have more than one, which comes first? Which tools or destinations would the exported text go into (GitHub, GitLab, Confluence, Jira, Notion, an AI assistant, an IDE)? How faithful does the export need to be? Is it enough to capture the structure (shapes, connections, labels), or do you need styling, layout, and other details to survive too? If your diagram contains something the format can't express, what would you want to happen? For example: skip it, simplify it, or get a warning. How do you do this today, and what is the most painful part of that workflow?Fill in the blank (optional)I would export my diagrams as ________ so that I can ________. The reason I cannot do this today is ________.Examples are very helpful, so feel free to share a sample of the output you would want, or a screenshot of the workflow you use now.Thank you in advance. Your answers will help us decide which formats to invest in first. 

jimmy
jimmyLucid product team

How are you using Grid Layout? (formerly known as Assisted Layout)Seeking Feedback

Hello Lucid community members! I am the product manager for the teams who developed our recent grid layout (formerly known as assisted layout) feature.  Grid layout makes it quick and easy to keep your canvas content organized. We do this by aligning shapes and automatically routing lines in a simplified grid-based layout: This feature is available through the ‘Grid Layout’ button shown in the bottom right corner of all Lucid container.  You can also activate grid layout by:The contextual menu in Lucidspark The properties panel in LucidchartThis feature also powers the ‘Tidy Up’ button you may have seen when making bulk selections on the canvas: We would love to hear how you are using grid layout as part of your workflow, and the ways it can improve. GoalsUnderstand what tasks and jobs grid layout has the greatest impact Learn when people choose to use grid layout in their workflows Collect feedback on where grid layout can improve to better meet your needs Some discussion starters Where grid layout shines 🌎 I find grid layout most helpful for [specific task] because..." [fill in the specific diagramming or brainstorming task you do most, and how this feature simplifies it] 🌎  "I usually switch to grid layout at [this stage] of my workflow to…." [describe when in your process you move from messy ideas to organized structure, and why] 🌎 “I prefer using grid layout over manual alignment specifically when I am working on..." [mention a specific activity where auto-alignment provides more value than manual tweaking] 🌎 Grid layout has saved me the most time doing [tasks] because… [fill in which tasks this feature streamlines and why it’s valuable for you] 🌎  "The moment I realized grid layout was a game-changer was when I had to [action] and..." [share a specific 'aha' moment where the tool changed how you approach working] 🌎  "Grid layout makes [task] so much easier by..." [explain the specific feature capability that improves your work.  Example: line routing, spacing, dropzones] 🌎 “As a [job title] I use grid layout all the time to…” [describe how the tool supports your specific professional role and responsibilities] Where grid layout can improve 🌎 "I find myself turning grid layout off when I need to [action] because..." [identify the specific action or situation that the grid layout struggles to handle] 🌎 "I struggle to use this feature with [types of content or tasks] because….” [mention specific shapes or jobs types that don't seem to fit well within the current grid logic] 🌎 "It is difficult to find the grid layout tool because [reasons]."[provide feedback on the UI placement or the onboarding experience] 🌎 "I was confused when I tried to [task] and realized grid layout didn't support..." [outline any missing capabilities, like cell spanning or nesting, that you expected to see] 🌎 "I tried using the tool for [use case], but the organization didn't look right because..." [explain how grid layout failed to meet your aesthetic needs] 🌎 "I would use grid layout more often if...." [suggest any high-priority changes or requests that would make the tool more essential for you] 🌎 "I wish the layout engine was smarter about [feature] so I wouldn't have to manually..." [describe a specific adjustment you still have to make by hand after the tool runs]