Tips and Tricks draft. #849
Conversation
|
@candry7731 Including you here since I'm pointing out your new Voice Search feature. |
|
This looks like something that would be a great fit for our docs website :-) |
For some reason I thought the doc guide was all server side stuff. Didn't realize there was a client section. However, I'm now seeing if this is worthy of building in to the client itself. |
|
This pull request has been inactive for 21 days and will be automatically closed in 7 days if there is no further activity. |
|
@jimdogx Based on the shift to using the client documentation. Shall we close this PR? |
|
I still think we need a user facing help section....
Even my wife didn't know she could use the voice seach on the guide and I
built the damn thing.....
…On Wed, Dec 21, 2022, 7:31 AM 1hitsong ***@***.***> wrote:
@jimdogx <https://github.com/jimdogx> Based on the shift to using the
client documentation. Shall we close this PR?
—
Reply to this email directly, view it on GitHub
<#849 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT6PDREUO7ZTBT7GUMXF55DWOMBDPANCNFSM6AAAAAAR6R63VM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
With the advent of PR #916 and also the idea of just updating the Jellyfin client docs, I'm going to go ahead and close this PR. |
Initial cut at a draft of a Tips and Tricks page. Not quite a User Guide, but more of a FAQ?
Changes
Adds a new markdown page with Tips and Tricks. Also adds a new folder for any images needed for the Tips and Tricks page.
Is this something we even want??? Is someone that is better at writing guides interested in taking a stab at it?
Edit
Looking to make this an embedded help guide instead. The markdown file could go on the official doc website (if we want one there and we clean it up).