December 19th Release

With this update, we’re introducing markdown formatting support for parameter descriptions in the API Management widget and the Object Example widget.

• Why It Matters: Markdown allows users to format their descriptions with hyperlinks, bullet points, bold or italic text, and more, making documentation clearer and easier to understand.
• How It Helps: You can now create detailed, well-structured parameter descriptions to better convey important information to your audience.

A brand-new widget has been added to the editor: the Accordion Widget.

• Custom Titles: Add concise and descriptive titles to each accordion section for better organization.
• Content Versatility: Include any of the existing widgets inside accordion sections, along with full support for content styling.
• Use Case: This widget is perfect for presenting FAQs, step-by-step instructions, or collapsible content blocks for cleaner layouts.

We’ve introduced a project status feature that allows users to mark projects as “Draft.”

• What It Does:
• Projects marked as “Draft” are automatically unpublished and become inaccessible to external users.
• Applies to both public and private projects, ensuring greater control over content visibility during development or review phases.
• Why You’ll Love It: This feature ensures that unfinished or internal projects can be safely managed without risk of public exposure.

• Improved Efficiency: A new copy button is now available in the response widget within the API Explorer.
• Quick and Easy: This feature allows users to instantly copy response code for reuse in their workflows or debugging processes, saving time and effort.

We’ve added a much-requested customization option to the custom menu links:

• Flexible Navigation: Users can now choose whether links in the custom menu open in the same tab or a new one.
• Enhanced Control: This improves navigation and allows for diverse use cases, such as linking to external documentation or related resources.

• Streamlined Navigation: We’ve resolved longstanding issues with the side menu’s behavior, especially for sections containing subsections.
• Previously, navigating through these sections caused the menu to open and close inconsistently, creating confusion.
• The menu’s performance has been optimized to provide a smoother, more predictable experience.
• User Impact: Navigating complex documentation structures is now intuitive and frustration-free.

We’ve developed a fully branded, customer-friendly sign-in experience for enterprise clients:

• Custom Branding: Enterprise customers can now access private projects via a dedicated, branded sign-in page that aligns with their organization’s identity rather than Theneo’s default branding.
• Seamless Access: Customers can request access, sign in, and view private projects they’ve been granted access to, all from a single, polished interface.
• Business Benefits: This feature enhances professionalism and user trust, making it ideal for enterprise-grade workflows.

We’ve enhanced the flexibility of enum value fields in the API Explorer:

• Editable Fields: Users can now choose values from the dropdown or enter their own custom values directly.
• Why It’s Useful: This update caters to dynamic use cases where predefined options might not cover all possible inputs, offering greater adaptability.

• Enhanced Readability: Dropdown options with long names are now displayed on two lines instead of being truncated into a single line.
• User Experience: This change makes it easier to identify and select options with lengthy names, ensuring clarity in navigation.

We fixed an issue where deleted object example widgets continued to display in both preview and published views. With this fix, the editor now properly reflects deletions.

Resolved Inconsistencies: Nested objects within arrays are now correctly displayed in the generated code examples, ensuring parity between the form view and the displayed code.

We’ve addressed an issue that prevented users from deleting request body elements via the delete icon. This functionality now works as intended.

Attributes marked as required within child objects of arrays were previously not indicated as such. This fix ensures all required attributes are clearly marked in the API Explorer.

Consistency Restored: Required attributes are now correctly exported when using the CLI, ensuring no loss of critical data during project migration.