Two practical design innovations to enhance user-experience and productivity #110250
Replies: 2 comments 2 replies
-
Do proper URI encoding. https://github.com/b9Joker108/a.fable.of.the.scriptkiddie.scriptoria/raw/main/A%20Fable%20of%20the%20Scriptkiddie%20Scriptoria%20(GitHub%20test).md And avoid using scheme that relied on syntax highlighting / post-rendering: poor general interoperability. Might be of use: https://github.com/microsoft/vscode/issues/206902#issue-2169741980 ---- Summary: |
Beta Was this translation helpful? Give feedback.
-
I just recategorised this thread, from discussion to general. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Dear GitHub and to whomever else it may concern
I have a practical design enhancement and user-based innovation suggestion, that significantly impacts upon practical usefulness and usability, in document preparation on GitHub. I know this isn't the primary function of GitHub, but it holds much import for the medium and forum, as documentation is key to community and community capacity building, innovation, and global discourse in general.
I am writing a document in GitHub Flavoured Markdown, with associated code, in the GitHub repository environment, that has become quite large, namely:
https://github.com/b9Joker108/a.fable.of.the.scriptkiddie.scriptoria/blob/main/A_Fable_of_the_Scriptkiddie_Scriptoria_(GitHub_test).md
It was a design choice, at this initial stage, to use a singular page design in Markdown, rather than a multi-node reticulum, forded through a multi-paged wiki, or a traditional HTML archive, connected by metatext/hyperlinks/hypertext. (Well, in truth, it is less a design choice, and more the stuff of happenstance, and that is just the way I draft best. The work is still very much a draft.)
I just noticed the chains icons, at the left of the various Markdown heading levels. I have been editing this document for some time. Well, in truth quite briefly, but only just noticed them and explored their functionality. Now, I do note and know, that I am blinkered when I write, as I am an impassioned writer and researcher. That said, I feel it unlikely that I haven't noticed these for the quite a few weeks or the very few months I have had an active GitHub account, and repositories: quite unlikely, though possible. If indeed, they are a newly implemented design enhancement, or otherwise, I humbly petition for two more.
Now in the chain icons, that provide various functionalities, such as an intra-linkage specificity, for example:
https://github.com/b9Joker108/a.fable.of.the.scriptkiddie.scriptoria/blob/main/A_Fable_of_the_Scriptkiddie_Scriptoria_(GitHub_test).md#fizsh-a-zsh-shell-extension-subsuming-fish-like-features-and-experience
May we usefully piggyback in the chain icon dropdown options, the new functionality to jump to editing at that particular section at-once or with immediacy, rather than selecting editing mode globally, and then trawling or scrolling through the document for the relevant section to be edited. As the document has become large, this is now cumbersome and problematic, and an inexact science, as well as manifestly inefficient. I take inspiration from the Wikimedia Projects section editing functionality. I feel this would usefully enhance the GitHub Flavoured Markdown document writing process, experience, and subsequent efficiency. I do note that there is the wiki functionality as an option in repositories, and that, though I haven't done so, I intuit that migration from GitHub Flavoured Markdown to the GitHub Wiki forum, may usefully provide both the functions that I entreat. Though, I haven't yet explored them.
In addition, may we please have a document or page search field, to find items, such as words or phrases, for example, within GitHub Flavoured Markdown and associated document file extensions, and to cycle through such items?
These two design implementations would greatly enhance usability and functionality. I humbly petition for their inclusion.
Thank you so much for the GitHub forum and medium.
Thanking you in anticipation
Beauford
P. S.
I just copied and paste this Markdown document intra-linkage:
https://github.com/b9Joker108/a.fable.of.the.scriptkiddie.scriptoria/blob/main/A Fable of the Scriptkiddie Scriptoria (GitHub test).md#fizsh-a-zsh-shell-extension-subsuming-fish-like-features-and-experience
And note, that though when I place it in the URL of an Internet browser it is directly discoverable, it functions as a broken link when pasting wholesale in this document, for your knowledge. I note, that it is possibly due to my ignorance that it is probably not working. I tried to repair the above linkages, and placed underscores where there are spaces, and though the linkage is now visually unbroken, it is still practically.
Beta Was this translation helpful? Give feedback.
All reactions