4

Kagi Changelog is overall very pleasant to use. I wrote this suggestion to improve a couple of things about it.

Viewing the images in larger size

  • Currently clicking an image navigates you to its direct path in the same tab. While this sometimes has a use, it is quite annoying for the user to navigate back to continue reading the changelog.
  • Instead a lightbox/modal image viewer (I am not 100% sure about the term but I mean something similar to what is used on the feedback forum) could be used. This would allow for a smoother user experience.

The location of the changelog images

  • Currently the images seem to be hosted in the feedback forum assests, e.g.
    https://kagifeedback.org/assets/files/2024-03-26/1711457673-662718-image.png
  • This usage should be changed and a proper location for the images should be chosen internally.
    6 days later

    laiz

    Could you expand on the second point?
    We write our release notes on KagiFeedback, so the uploaded images are just wherever Flarum puts them when a user submits them on a normal post and not something we do 'intentionally'.

    • laiz replied to this.

        pixel
        For some reason I assumed the changelog was primarily on kagi.com/changelog and secondarily on the feedback forum. In that case it makes sense that the images are hosted on kagifeedback.org.

        The way I approached this issue was by applying the guidelines from writing documentation, i.e. no documentation images should be hosted on kagifeedback.org even though there are quite a few currently being hosted here.

        In the rare scenario that something were to happen to the feedback forum1, it would make sense that the images are hosted elsewhere so they wouldn't be wiped. Overall the first point was the primary purpose of this suggestion but the second one would be nice to have, if someone can be bothered to move all future changelog images to kagi.com/assets/ or something similar.

        1 Flarum upgrade going horribly wrong, someone deciding that we need a fresh start and wiping all old suggestions and reports is the way forward — this idea has been mentioned a few times on orionfeedback but search engine and browser bugs are obviously two very distinct items

            laiz

            Gotcha, alright. That makes sense.
            Yeah, the kagi.com/changelog page is actually just... an rss reader for this site 😛

                Moving something does not make it more durable.

                  9 days later
                  No one is typing