-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Information within the documentation #83
Labels
Type: Documentation
This is documentation
Comments
The FAQ has some of these points already covered, so that would be a good place to base that on. |
Indeed, but it is hardly "snappy" and, to be frank, I don't expect most
people who learn about the application/stumble across it will necessarily
look inside the deep FAQ until they are suitably curious about the
application to install it and learn more about it/fix issues.
So some snappier text in the project's home page on the lines that I
outlined may be beneficial, I humbly submit.
…On Mon, 31 May 2021 at 11:17, Roxedus ***@***.***> wrote:
The FAQ <https://wiki.servarr.com/Prowlarr_FAQ> has some of these points
already covered, so that would be a good place to base that on.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV5MACMGPU24MJTKOVTAATTQNAX5ANCNFSM452MWJTQ>
.
|
Qstick
added
Type: Documentation
This is documentation
and removed
Type: Feature Request
Issue is a feature request.
labels
May 31, 2021
To @Roxedus point we could likely pull some of that language or points from the FAQ to use in a more upfront way on the page. We do have plans to expand on the current page and documentation, just not a top priority. That being said we’d welcome a PR with some recommendations should you feel up to it. |
As things become a little more fixed and ready that could be a possibility.
…On Mon, 31 May 2021 at 23:12, Qstick ***@***.***> wrote:
To @Roxedus <https://github.com/Roxedus> point we could likely pull some
of that language or points from the FAQ to use in a more upfront way on the
page. We do have plans to expand on the current page and documentation,
just not a top priority. That being said we’d welcome a PR with some
recommendations should you feel up to it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV5MAAOOVKSXNJBAQMFKJTTQPUR7ANCNFSM452MWJTQ>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be good if you could explain (within the project's documentation) how this application may be similar/comparable to Jackett and, of course, highlight the existing and planned differences that will make the application stand out. Jackett is already well-established and by doing the foregoing it may help the project gain additional traction and usage.
The text was updated successfully, but these errors were encountered: