920 results found

1. I am unable to export text-to-speech audio from Captivate. This was a problem for us in Captivate 12 and continues to be a problem with 13

   I am unable to export text-to-speech audio from Captivate. This was a problem for us in Captivate 12 and continues to be a problem with 13. I attended the Adobe Learning Summit and spoke to the developers about it, but have not received a resolution.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   NeedMoreInfo  ·  1 comment  ·  Text to Speech  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Crashing during AI Avatar

   I have had a couple of attempts to create an AI Avatar for an imported PowerPoint. I was recording for YouTube at the time, submitted the crash using the crash report but thought it might be beneficial to see what I was doing at the time.
   https://youtu.be/GwG8bphGb1o

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   NeedMoreInfo  ·  2 comments  ·  Audio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. [Bug] `textProps.fontWeight` is ignored during rendering

   Version: 13.0

   Problem:
   textProps values such as fontWeight set in designOption.json are displayed correctly in the Captivate UI, but are ignored in the final rendering and overridden by inline styles (e.g., font-weight: normal;). Other textProps (like textAlign) work as expected.

   {
     "tag": "slide-item-subtitle",
     "preset": "text-body-6",
     "customStyles": {
         "all": {}
     },
     "customProperties": {
         "alignmentAndSpacing": {},
         "textProps": {
             "fontWeight": "600",
             "textAlign": "center"
         }
     }
   },
   

   In the rendered output, inline styles appear such as:

   font-weight: normal;
   

   Impact:
   - Inconsistent results between editor preview and actual output
   - Paragraph styles cannot be reliably overridden
   - UI feedback is misleading (shows correct formatting, but renders incorrectly)

   Expected behavior:
   textProps should be respected during rendering and should not be overridden by generated inline styles.

   Version: 13.0

   Problem:
   textProps values such as fontWeight set in designOption.json are displayed correctly in the Captivate UI, but are ignored in the final rendering and overridden by inline styles (e.g., font-weight: normal;). Other textProps (like textAlign) work as expected.

   {
     "tag": "slide-item-subtitle",
     "preset": "text-body-6",
     "customStyles": {
         "all": {}
     },
     "customProperties": {
         "alignmentAndSpacing": {},
         "textProps": {
             "fontWeight": "600",
             "textAlign": "center"
         }
     }
   },
   

   In the rendered output, inline styles appear such as:

   font-weight: normal;
   

   Impact:
   - Inconsistent results between editor preview and actual output
   - Paragraph styles cannot be reliably overridden
   - UI feedback is misleading (shows correct… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Design Options   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. [Feature] Grid and Visible Borders for Design Options

   Version: 13.0

   Problem:
   When working in Captivate, visual aids such as grids, borders, or width and height indicators are missing. Apart from the highlight shown when directly clicking a Design Option or on slide overflow, the positioning of elements is difficult to control – especially for complex layouts.

   Suggestion:
   - Visible borders for Design Options and their sub-elements, optionally toggleable.
   - Fully customizable background grid, similar to Adobe XD or Figma, for better layout orientation.
   - Display of width and height measurements for placed elements.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Application   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. [Bug] Design Option “Image” does not respond correctly to grid styling

   Version: 12.6

   Problem:
   The “Image” design option partially fails to respond to grid styling defined in the designOption.json. The element container-image-text does not occupy the designated grid-area because it is not a direct child of the container-image-card element where the grid is applied.

   In Chrome DevTools, it is visible that the instruction

   grid-area: 1 / 1 / span 1 / span 1;
   

   has no effect because the target element does not participate in the grid context.
   See screenshot: design-options_image-01.png

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Image   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. [Feature] Support for Character Styles for Inline Text

   Version: 13.0

   Problem:
   Currently, Captivate only supports paragraph-level formatting (Paragraph Styles). There is no way to define reusable character styles for quick and consistent inline emphasis. The existing “Highlight” inline element is too limited (no padding, margin, border, border-radius, etc.), leading to inconsistent workarounds and unnecessary manual inline formatting.

   Use Cases:
   - Highlighting key terms
   - Inline quotes / badges
   - Keyboard shortcuts / keycaps
   - Code snippets
   - Labels / status indicators

   Suggestion:
   Introduce freely definable character styles supporting:
   - color, background-color
   - font properties
   - padding, margin
   - border, border-radius

   Configurable in:
   - GUI (Theme-Editor)
   - theme.json

   Benefits:
   - consistent corporate branding via global styling
   - improved readability and learner orientation
   - reduced manual inline formatting
   - clearer emphasis of instructional key terms

   Version: 13.0

   Problem:
   Currently, Captivate only supports paragraph-level formatting (Paragraph Styles). There is no way to define reusable character styles for quick and consistent inline emphasis. The existing “Highlight” inline element is too limited (no padding, margin, border, border-radius, etc.), leading to inconsistent workarounds and unnecessary manual inline formatting.

   Use Cases:
   - Highlighting key terms
   - Inline quotes / badges
   - Keyboard shortcuts / keycaps
   - Code snippets
   - Labels / status indicators

   Suggestion:
   Introduce freely definable character styles supporting:
   - color, background-color
   - font properties
   - padding, margin
   - border, border-radius

   Configurable in:
   - GUI (Theme-Editor)
   - theme.json

   Benefits:… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Text  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. [Feature] Option for image container to grow with text in the “Image” Design Option

   Version: 12.6

   Problem:
   Currently, the image in the "Image" Design Option does not grow when the text block container-image-text increases in height. There is no setting in either the Captivate GUI or the designOption.json to scale the image vertically along with its content.
   In responsive layouts (e.g., hero sections, split layouts), this leads to unbalanced designs, awkward proportions, and unnecessary whitespace.
   See screenshots design-options_image-02.png and design-options_image-03.png.

   Suggestion:
   Add an optional setting that allows the image to:
   - grow vertically with the text container
   - maintain its aspect ratio (e.g., via object-fit)
   - adapt responsively to varying content heights
   - optionally use a min-height to prevent layout collapse

   These options should be configurable both in the GUI and in the designOption.json.

   Note:
   The behavior should remain optional. In some layouts, a fixed height is still desired — ideally configurable separately for each device (Desktop, Tablet, Mobile).
   See screenshot design-options_image-04.png

   Version: 12.6

   Problem:
   Currently, the image in the "Image" Design Option does not grow when the text block container-image-text increases in height. There is no setting in either the Captivate GUI or the designOption.json to scale the image vertically along with its content.
   In responsive layouts (e.g., hero sections, split layouts), this leads to unbalanced designs, awkward proportions, and unnecessary whitespace.
   See screenshots design-options_image-02.png and design-options_image-03.png.

   Suggestion:
   Add an optional setting that allows the image to:
   - grow vertically with the text container
   - maintain its aspect ratio (e.g., via object-fit)
   - adapt responsively to varying content heights… more

   •  

   •  

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Image   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. [Feature] Custom layout slides with freely configurable Design Options

   Problem:
   New content slides can currently only be created based on predefined layout categories (e.g., Comparison, Meet the Team). Each layout only allows importing a fixed set of Design Options defined in its associated designOption.json. Additional components cannot be added, which makes layouts unnecessarily rigid and difficult to adapt to custom design requirements or corporate branding.

   Example:
   Meet the Team only allows paragraph and image-grid. Adding an additional paragraph beneath the grid is not possible.

   {
     "type": "Meet the Team",
     "name": "$$name",
     "description": "$$description",
     "designOptionId": "LAYOUTS_MEET_THE_TEAM",
     "isDefault": false,
     "version": "1.0",
     "thumbnail": "thumbnail.png",
     "styles": [
        {
         "tag": "paragraph",
         "designOptionId": "MTT_PARAGRAPH_OPTION_1"
       },
       {
         "tag": "image-grid",
         "designOptionId": "IMAGE_GRID_MTT_OPTION_1"
       }
     ]
   }
   

   Suggestion:
   Enable support for custom layout slides, where the corresponding designOption.json can contain any components the author needs. This would allow instructional designers to create rich, reusable layout templates for both slide-based content and longpages.

   Problem:
   New content slides can currently only be created based on predefined layout categories (e.g., Comparison, Meet the Team). Each layout only allows importing a fixed set of Design Options defined in its associated designOption.json. Additional components cannot be added, which makes layouts unnecessarily rigid and difficult to adapt to custom design requirements or corporate branding.

   Example:
   Meet the Team only allows paragraph and image-grid. Adding an additional paragraph beneath the grid is not possible.

   {
     "type": "Meet the Team",
     "name": "$$name",
     "description": "$$description",
     "designOptionId": "LAYOUTS_MEET_THE_TEAM",
     "isDefault": false,
     "version": "1.0",
     "thumbnail": "thumbnail.png",
     "styles": [
        {
         "tag": "paragraph",
         "designOptionId":

   … more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Layout slides    ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Allow content creators to import .doc or .pdf text to populate a template.

   If there were tags that could be placed into a word document that could call for a slide option in a project template, then the program could auto-populate text and images into predetermined slide options. This would allow for a rapid conversion to Captivate files when receiving only text, image and link content from authors.

   Many of our authors are accustomed to a particular set of procedures for content development. We need a simple method to take the content provided and convert it to a Captivate project.

   If there were <tag>s of some sort that could identify sections of text and their associated images and links to videos or other online content and then populate an appropriate slide template, that would be ideal. Tags could identify other design options as well, for example font style or shape colors or corner radius for buttons. Have a simple library of available tags. Then content creators who do not use Captivate can put in tags that would reduce the amount of time needed for the Captivate content team to fine tune the imported project.

   Ideally, they would also be able to tag specific variables and object names as well. Some of our LMS integration is dependent on button object names and custom variables. These variables could mostly be handled by a custom template though, if that were an option, which it absolutely should be. Then it would just be making sure that the doc or pdf had the appropriate tag for the custom slide template with the appropriate custom variable options.

   If there were tags that could be placed into a word document that could call for a slide option in a project template, then the program could auto-populate text and images into predetermined slide options. This would allow for a rapid conversion to Captivate files when receiving only text, image and link content from authors.

   Many of our authors are accustomed to a particular set of procedures for content development. We need a simple method to take the content provided and convert it to a Captivate project.

   If there were <tag>s of some sort that could identify sections of text… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Import/Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Variables and Design Options

    We all understand that Captivate 12 is "built around a template-based authoring approach, designed to streamline project creation with minimal effort." that's just great. And we all want a simple user interface for our content creators who are less technically savvy, which Captivate provides. That does not mean that the content administrators don't still need the ability to have custom templates with variables to integrate properly with their LMS (and in our case LRS). We have government mandated variable time requirements for slide dwell time and total lesson duration. We also have varying pass percentage requirements.

    There are a large number of exchanges that have to happen to make sure that a given user / registration is launched with the appropriate injected values. That means that the variable must be accurate. Those variable should not have to be recreated ever, they should be selectable, custom variables that are options for any new project if they are in the options folder.

    Currently, you have to copy a slide from a 'template project' somewhere on your computer. When you do that, with no apparent specific reason, Captivate creates a new variable. This, of course, breaks the logic and you must go through every slide with variables and make sure that a numerical suffix has not been added when pasting. There is no way to turn this off. Further, you cannot delete these ghost variables that end up being sometimes 50-100 randomly generated variables. You try to delete them, and even though those variables are used NOWHERE in the project, Captivate does not allow you to delete them. It is genuinely frustrating.

    The entire variable and design option architecture is pretty broken. It is 'clunky' at best. I dont even want to think about how many hours I have had to waste fixing logic errors in a program that is supposed to be "designed to streamline project creation with minimal effort."

    In our case, it has been anything but 'streamlined'

    Our dev team is throttled by the Captivate teams decision making process, it is not good.

    We want the simple interface and template, yes.

    We MUST have the ability to create our own custom templates complete with custom variables that do not create a 1000 ghosts.

    We all understand that Captivate 12 is "built around a template-based authoring approach, designed to streamline project creation with minimal effort." that's just great. And we all want a simple user interface for our content creators who are less technically savvy, which Captivate provides. That does not mean that the content administrators don't still need the ability to have custom templates with variables to integrate properly with their LMS (and in our case LRS). We have government mandated variable time requirements for slide dwell time and total lesson duration. We also have varying pass percentage requirements.

    There are a large… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Variables  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. [Feature] Option for automatic display of timeline events (without click)

    Problem:
    In the current Timeline widget, each event must be clicked manually for its associated content (text/image) to appear.
    This interaction pattern is not ideal for all learning scenarios — especially in linear or narrative timelines, repeated clicking can be distracting and offers little didactic value.

    Suggestion:
    Add an option in the Captivate GUI and in the designOption.json to control the behavior:
    - Manual (current behavior): The user clicks each event to reveal its content.
    - Automatic: The content is always visible.
    - For better user experience: The content appears with a smooth fade-in or motion animation when the event enters the viewport.

    Problem:
    In the current Timeline widget, each event must be clicked manually for its associated content (text/image) to appear.
    This interaction pattern is not ideal for all learning scenarios — especially in linear or narrative timelines, repeated clicking can be distracting and offers little didactic value.

    Suggestion:
    Add an option in the Captivate GUI and in the designOption.json to control the behavior:
    - Manual (current behavior): The user clicks each event to reveal its content.
    - Automatic: The content is always visible.
    - For better user experience: The content appears with a smooth fade-in or motion animation when the event… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Timeline Widget  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. [Feature] New Widget for Expandable Single Sections (Disclosure / Details)

    Background:
    On longpages or compact content layouts, there is often a need for expandable single sections for supplementary content such as transcripts, glossaries, or additional information. An accordion widget is overkill for this purpose, as it requires multiple tabs and semantically implies a group behavior.

    Problem:
    - The Accordion widget cannot currently be reduced to a single tab.
    - Using a "pseudo-accordion" with only one panel is semantically incorrect and may negatively impact accessibility and user orientation.
    - There is no dedicated widget to toggle individual content sections, making implementation cumbersome.

    Suggestion:
    A dedicated widget based on the established HTML5 <details>/<summary> pattern or a disclosure element. It should:
    - Toggle a single content block open/closed
    - Optionally scroll automatically
    - Optionally support state persistence
    - Clearly indicate visual states
    - Be configurable via GUI and designOption.json

    Background:
    On longpages or compact content layouts, there is often a need for expandable single sections for supplementary content such as transcripts, glossaries, or additional information. An accordion widget is overkill for this purpose, as it requires multiple tabs and semantically implies a group behavior.

    Problem:
    - The Accordion widget cannot currently be reduced to a single tab.
    - Using a "pseudo-accordion" with only one panel is semantically incorrect and may negatively impact accessibility and user orientation.
    - There is no dedicated widget to toggle individual content sections, making implementation cumbersome.

    Suggestion:
    A dedicated widget based on the established HTML5 … more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Interaction  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. allow the addition of custom assets in template info.json

    info.json ("C:\Users\Public\Documents\Adobe\eLearning Assets\12.0\content\Templates\info.json") elements populate the project template assets menu. There is an internal updating mechanism that prevents any additions from persisting in this .json. Further, the "id" seems to lead to another asset that populates the slide choice menu when you select a project from the project template assets menu. We need our templates to be configured to populate this menu so that our content developers can select our standard templates from the assets menu. This is critical. Pulling slides and configuring slides from a 'template project' that is open in a different window is clunky, prone to variable errors, and very time consuming. It is very tedious. We must reduce tedium. The project menu shown will work for a single time. Captivate updates the info.json file each time you open Captivate, so you have to resave with the added option to see it in the menu. You can change the "id" and those slides will show up when you select your project. I just need to be able to save my slides in the same way, and have an associated "id' so that I can select my template slides. I can make whatever changes need to be made to the project to ready it for conversion to a template asset.

    info.json ("C:\Users\Public\Documents\Adobe\eLearning Assets\12.0\content\Templates\info.json") elements populate the project template assets menu. There is an internal updating mechanism that prevents any additions from persisting in this .json. Further, the "id" seems to lead to another asset that populates the slide choice menu when you select a project from the project template assets menu. We need our templates to be configured to populate this menu so that our content developers can select our standard templates from the assets menu. This is critical. Pulling slides and configuring slides from a 'template project' that is open in a different window is clunky, prone to variable… more

    •  

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Assets Panel   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. ragesh.c@gds.ey.com

    The new Adobe Captivate version does not allow placing objects in a custom order. It only supports drag-and-drop using predefined templates. For example, if we need to position titles, images, icons, or buttons freely on the slide, this flexibility is missing. Currently, all custom design options are limited, forcing us to use only what Captivate provides.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Add checkboxes with Select All or Deselect All when editing Table of Contents

    When creating courses in Captivate, we often have over 100 slides, but we only want our users to have access to maybe 10 in the Table of Contents. In Captivate 12.6, I have to deselect each slide which is obnoxiously time consuming. The "eye" icon action should be replaced with check boxes with "Select All" or "Deselect All" options at the top.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  TOC/Playbar   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Bug- Mac Users Have Different Text

    When I create trainings, they work just as expected on Windows but if someone on a Mac opens it the text turns into a different font and is not matching my company branding as I designed it to.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  2 comments  ·  Application   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Text Drag and Drop

    I don't use the drag and drop because currently it is only for pictures. Would be nice to have the ability to have learners drag and drop text to other text.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Feature_In_Backlog  ·  1 comment  ·  Drag and Drop Widget  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. [Feature/Bug] Cards Widget: Perspective and mouseover overlay customization

    Problem:
    - The .flip-card-container in the global stylesheet uses the perspective property. This value cannot be adjusted via the GUI or the designOption.json.
    - If no image is set on the front side, a gray mouseover overlay appears. Its color and visibility cannot currently be changed in the GUI or the designOption.json.

    Suggestion:
    - Make the perspective value adjustable in both the GUI and the designOption.json.
    - Allow configuring the color and behavior (show/hide) of the mouseover overlay in the GUI and designOption.json.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Cards Widget  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. [Bug] Quote Widget ignores styling and lacks clear component references

    Problem:
    The Quote Widget does not fully respond to styles defined in designOption.json.

    Details:
    - The containers container-quotes-text, slide-item-quotes-icon-container-1, and slide-item-quotes-icon-container-2 ignore custom style definitions and seem to have structural inconsistencies.
    - In container-quotes-card, there are no documented or discoverable component names (e.g., quoteText, quoteIcon1, quoteIcon2), making it impossible to target, enable, or disable these elements within designOption.json.
    - Several layout properties in the global stylesheet cannot be overridden locally within designOption.json.

    Suggestion:
    Document all component names and ensure that each element of the Quote Widget can be fully styled and controlled directly from designOption.json.

    The internal structure could follow the example of the SVG widget, which allows flexible layout control using either flex or grid, depending on the design intent.

    Problem:
    The Quote Widget does not fully respond to styles defined in designOption.json.

    Details:
    - The containers container-quotes-text, slide-item-quotes-icon-container-1, and slide-item-quotes-icon-container-2 ignore custom style definitions and seem to have structural inconsistencies.
    - In container-quotes-card, there are no documented or discoverable component names (e.g., quoteText, quoteIcon1, quoteIcon2), making it impossible to target, enable, or disable these elements within designOption.json.
    - Several layout properties in the global stylesheet cannot be overridden locally within designOption.json.

    Suggestion:
    Document all component names and ensure that each element of the Quote Widget can be fully styled and… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Quotes    ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. [Feature] Custom CSS as a first step toward an open widget architecture

    Problem:
    Widget styles can currently only be customized via designOptions.json. Many widget structure elements cannot be targeted or modified globally.

    Suggestion:
    Add the ability to include a custom CSS file at the project or theme level. This stylesheet should allow global adjustments and overrides of Captivate’s core CSS.

    In the long term, Captivate could – similar to the Adapt Framework – offer an open widget system, where custom or modified widgets are possible. Custom CSS would be a useful, practical intermediate step that provides immediate benefits and paves the way toward a fully modular architecture.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating