Automattic / Automattic/simplenote-android
Inquiry About Exporting Internal Links in JSON for ASCII-Doc Conversionr '[Type] Enhancement'
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 318
- Avg merge
- 15h 23m
- Merged PRs (30d)
- 5
Description
Hallo, My name is Joshua, and as an enthusiastic user of your SimpleNotes app, I would like to express my gratitude. As a blind user, I particularly appreciate the ability to use your app for the Zettelkasten method – a feature that is inaccessible to me in other applications due to my visual impairment.
I have developed a script that converts the SimpleNotes export (in JSON format) into ASCII-Doc. This is based on a project for converting JSON to Markdown for Obsidian. This is crucial for me, as my university work relies heavily on the ASCII-Doc format.
My specific concern is about the export functionality, especially the ability to export internal links. These links are essential for maintaining the structure of my projects. Without the ability to export these links, the separation of projects and the structured presentation of my knowledge would be compromised, significantly reducing the usefulness of the information. This is particularly relevant to my learning process following the Zettelkasten principle.
Therefore, I kindly request information on how internal links are created and represented in the JSON file. My goal is to gain a better understanding of how to represent and convert these links in my own project.
I thank you in advance for your time and effort in assisting me with this matter.
Kind regards,
Joshua
---
### What
### Why
### How
[Type] Enhancement
Contributor guide
Research direction
No file, test, or entry point is named. Start by locating the Android export implementation and inspecting a sample JSON export for internal-link data; done would require a clarified scope for either documenting the existing representation or changing the export format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100