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
Assistant for push messages in GUI #166
Comments
|
We already have the API documentation included in the binary. Doing so would require baking documentations into the binary as well. @jmattheis What do you think about this? I think a link to the official documentation in the WebUI should be enough. |
|
Indeed, let's keep the code base light. |
|
Yeah, we can include a link to the documentation. How about adding the following links under the list of applications in the left navigation
|
|
I would prefer a page footer that include links to the documentation. The left navigation should be reserved only for selecting applications. |
|
Don´t add links to "admin dokumentation" to "user webpages" ;-) |
|
I actually discovered https://gotify.net/docs/more-pushmsg just now. That's exactly the kind of example I was looking for when opening this case. Can we merge https://gotify.net/docs/pushmsg and https://gotify.net/docs/more-pushmsg ? I can take care of it. |
|
@sebw I did the separation because there are many programming languages for which examples could be added. I'd say a link (which exists) to the more pushmsg page is enough. Maybe we can highlight this link a little more. |
|
@jmattheis yup, makes sense. Renaming to Library and putting it right after pushmsg would probably be a bit clearer? |
|
Renaming is okay, I don't think it fits into getting started, as it is a more advanced usage of the gotify/server api. |


I like how Simplepush presents a couple of different ways to generate push messages on their website:
https://simplepush.io/#libraries
How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg
The text was updated successfully, but these errors were encountered: