Kitsuly 1.43.98 focused on something that becomes more important as a platform grows: documentation that feels like part of the product rather than a pile of files somewhere else. The build introduced a native guide-library experience designed for Kitsuly’s own documentation site, with visual covers, clear titles and in-page PDF viewing.

What changed

The documentation library moved from a basic file-list idea to a visual grid that could present the complete guide set as a coherent collection. The layout was designed around four cards across on larger screens, then reduced responsively for tablet and mobile so the library remained easy to browse without turning each guide into an oversized banner.

Each guide card opened the associated PDF inside a focused modal iframe. That kept readers on the page, preserved their place in the guide library and still offered an explicit option to open the document in a new browser tab when a larger reading surface was preferred.

The implementation also separated the document experience from ordinary customer installations. The native guide library was intended for the Kitsuly owner site, using same-origin files already stored in WordPress uploads. That kept the feature useful for Kitsuly documentation without turning every customer store into a remote-document client.

Build 1.43.98 changelog

• Added a native documentation-library component for Kitsuly’s own documentation site.
• Presented guides in a four-column desktop grid with responsive tablet and mobile layouts.
• Added modal iframe viewing so PDFs can be read without leaving the document page.
• Retained an Open in new tab action for users who prefer the browser’s full PDF viewer.
• Kept the owner-site documentation component separated from normal third-party store installations.

Documentation is easy to treat as an afterthought when the product is changing quickly. In practice, it becomes part of the product experience. A powerful feature that nobody can find or understand creates support work and slows adoption. Build 1.43.98 treated the guide library as an interface problem: make the available knowledge visible, recognisable and easy to open.

Why this build mattered

The visual-card approach matters because a documentation page has the same usability problems as a catalogue. A long vertical list becomes difficult to scan, especially when titles are similar. Covers, consistent card geometry and grouped presentation let the reader recognise a guide quickly. The grid is not decoration; it reduces the work required to choose the right document.

Keeping the PDF inside an iframe also reduces context switching. A reader can open a guide, check a process, close the viewer and return to the library without accumulating tabs. At the same time, forcing everyone into the modal would be unnecessarily restrictive, so the new-tab action remains available for longer reading sessions.

What the release meant in day-to-day use

For day-to-day support, the native library creates a cleaner hand-off. A support response can point a user toward a named guide that looks the same in the library as it does in screenshots or training material. For the Kitsuly team, replacing a PDF does not require redesigning the page because the display logic and the document files are separated.

The responsive behaviour is equally important. Documentation is often opened while someone is actively working on another device. A merchant may read a guide on a tablet beside a desktop store editor, or open instructions on a phone while checking a live storefront. The grid and viewer therefore need to remain usable outside the ideal desktop scenario.

How it fits into the wider Kitsuly release path

Build 1.43.98 sits between customer-facing feature work and platform polish. It did not change how a customer checks out, but it changed how the product explains itself. That becomes increasingly important as Kitsuly adds memberships, marketing, themes, integrations and Builder tools that can no longer be summarised in a single getting-started page.

The release also reinforced a broader design principle: operational tools deserve the same attention as storefront features. Documentation, diagnostics and support surfaces may not appear in a sales screenshot, but they influence whether a merchant can confidently keep using the system after launch.

What to take forward

The documentation work also created a clearer maintenance path. A guide can be replaced in the uploads area without rebuilding the visual library, while the card structure remains consistent. That separation is useful because documentation changes at a different pace from the interface around it. The library can remain stable while individual manuals are revised as Kitsuly changes.

For a product moving quickly, that matters. Documentation is never truly finished, so the system needs to make updates cheap enough that they actually happen. Build 1.43.98 was therefore as much about maintainability as presentation: give the guides a dependable home, make them easy to open and avoid turning every documentation update into another page-design task.

The guide library also creates a better foundation for future help content beyond PDFs. Once the site has a recognisable documentation surface, videos, quick-start cards, release notes or contextual links can be added without forcing users to learn a new navigation pattern each time. The immediate release focused on the existing guide set, but the structural value is broader: documentation now has a defined place in the Kitsuly experience rather than being treated as a collection of unrelated downloads.