Feature Requests

Part-Level Hotpoint Link Management
Overview: Currently, hotpoint links can only be configured at the page-part level when interacting with a BOM on a part page. While this works functionally, it requires repetitive manual setup when the same part appears across multiple pages, assemblies, or manuals. Current Limitation: When a part number appears in multiple locations, hotpoint links must be created individually for each page instance. If the linked page changes due to a revision, each hotpoint link must be manually updated. This results in significant administrative effort and increases the risk of inconsistent or outdated links. Proposed Enhancement: Add the ability to define hotpoint links at the part level rather than only at the page-part level. With this enhancement: •A hotpoint link would be associated directly with the part number •That link would automatically appear anywhere the part number is used •The link would function as a master link for that part Example Use Case: A part number is used across multiple assemblies and manuals. A single hotpoint link is configured at the part level pointing to a specific instruction or detail page. Wherever that part number appears, the hotpoint link is automatically available. If the linked page is revised or changes, the link only needs to be updated once at the part level and will apply everywhere the part is referenced. Benefits: •Significant reduction in manual setup and maintenance •Consistent hotpoint behavior across all documents •Simplified revision management •Reduced risk of broken or outdated links •Improved scalability as documentation grows Summary: Part-level hotpoint links would allow teams to manage links once and apply them everywhere a part is used. This would greatly improve efficiency, consistency, and long-term maintainability of documentation.
2
·
Feedback Forum
Native SVG Support for Exploded Diagrams / Parts Pages
Native SVG support was originally on the Documoto roadmap but was later bumped off, and I’d like to advocate for bringing this feature back. Our company relies heavily on SVG-based technical illustrations, especially for exploded diagrams, and the current workflow creates several limitations. Right now, when we upload an SVG to Documoto, the system rasterizes it into a static image. This removes many of the advantages that make SVG the preferred format for technical content: •No true scalability — images become blurry when users zoom in •Loss of clarity for detailed assemblies and small parts •Larger file sizes compared to vectors •Inconsistent quality across different screen resolutions Exploded diagrams benefit significantly from vector rendering, since users frequently zoom in to identify small fasteners, hidden components, or narrow callouts. Rasterization directly impacts accuracy and usability. •Native SVG rendering would provide: •Perfect clarity at any zoom level •Better user experience for parts identification •Better performance due to smaller file sizes •Preservation of authoring quality (no more raster conversion) •Alignment with modern documentation and publishing standards Given that this was previously planned, our company would like to express strong interest in having native SVG support reinstated on the development roadmap. This enhancement would significantly improve the quality and usability of our parts pages and support more precise, scalable technical content moving forward. Looking forward to hearing whether this can be reconsidered for future development.
2
·
Feedback Forum
Load More