Add Inkiostro to the tool directory - #289
Open
mi0772 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a directory entry for Inkiostro, a native Markdown editor for macOS, iPadOS, and iOS, with a separate Android version.
_tools/inkiostro.md— the entry and its syntax support tableassets/images/tool-icons/inkiostro.png— 256×256, to match the other iconsassets/images/tools/inkiostro-editor.png— screenshot of the editor and the live previewI'm the developer of the application. Following the contribution notes I've kept the description to what it does, listed the elements it doesn't support, and included a quirk users run into.
On the support table: the preview is rendered with markdown-it 14.1.0 — CommonMark plus tables, strikethrough, footnotes, task lists, and heading anchors — so I filled the table from the renderer's actual configuration, then verified the ambiguous rows by running test input through the exact bundle the application ships rather than going from memory. Two are worth flagging:
{#custom-id}syntax isn't supported: it stays in the heading as literal text. It's mentioned in the prose as well.Happy to reword anything that reads as promotional, or to cut the two subsections at the end if they're more detail than the directory wants.