Docs.krita.org has been switched to sphinx!

Scott Petrovic scottpetrovic at gmail.com
Mon May 28 03:44:32 UTC 2018


There is quite a bit discussion going on here and I can't quite follow
everything. The two points I can make are the following

1. 404 page -- We will probably need a custom 404 page made in sphinx that
will have to be pointed to from a web server. It might need some custom
logic to determine what language needs to be shown and redirect as needed.
WordPress can handle it because it has routing built in. That means it can
handle 404 pages since all URLs get analyzed by WordPress to figure out
where they go. I don't think Sphinx has that type of intelligence built in
since they are pretty simple html pages.

2. Epubs on krita.org. The new download page has a "post-download" page
that has extra stuff. https://dev.krita.org/en/post-download/   We might be
able to add a link on that page...but I am not sure how useful that would
be. Directing people to the online documentation would be a better
experience while they are waiting for Krita to finish downloading.
Otherwise they are just downloading another file while they are in the
middle of downloading the application. I would probably opt for trying to
find a good place on docs.krita.org to put the epub link/button so people
know they can download the whole documentation site in epub format. we can
have custom URLs for each language, so that shouldn't be too difficult. I
am sure some languages won't have a link to the documentation site since
there is none.



On Sun, May 27, 2018 at 8:19 PM, Iván Yossi <ghevan at gmail.com> wrote:

> So a deprecated section. That'd be a page with a glob table of
>
> contents pointed at a 'deprecated' folder. However, say we deprecate
>
> the fill tool for whatever reason. It is currently at
>
> https://docs.krita.org/en/reference_manual/tools/fill.html, if we move
>
> it to a deprecated section it'd become
>
> https://docs.krita.org/en/deprecated/fill.html, meaning the link would
>
> break. Might it then be better to have a page with reference links
>
> towards the deprecated pages and that we don't move them physically in
>
> the manual until we remove the page?
>
>
>
> If the URLs are kept in a logical way and you can modify the apache rules,
> you could add a RedirectMatch for all cases pages not found to be lookfor
> in the deprecated folder, and if not found, then managed by the 404.
> However It’s been a while since I did that so Im not sure about the details.
>
> Iván Yossi
> <ghevan at gmail.com>
> IRC: ivanyossi
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20180527/7c26289b/attachment.html>


More information about the kimageshop mailing list