You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While looking into porting the proxito error pages, I'm finding the complexity in these templates could be reduced a good deal and perhaps this is even a case for moving some of the functionality into addons instead.
The current error pages do the following:
Show the reader a search input that leads to the dashboard search
Give some tips for project maintainers about custom domain configuration, adding redirects, etc
<li>{% trans "Use your own custom 404 page:" %} <ahref="https://docs.readthedocs.io/en/stable/reference/404-not-found.html">{% trans "Read more" %} »</a></li>
If you control this domain and believe this is in error,
Have some specific prose content for "this translation is missing" and "this versions is missing".
Deciding how to port this over though, it feels like what we want out of error pages is:
A search input that triggers the addons embedded, in-doc search modal, not the dashboard search
Content that focuses on readers users, not maintainers. Remove tips on custom domain configuration and adding redirects.
Should we be surfacing the reason for the 404 error through addons too? This would give custom error pages a chance to use the same descriptive prose. Is this important?
I'm feeling like it's not clear what is important to port over now that we are surfacing features through addons.
The text was updated successfully, but these errors were encountered:
While looking into porting the proxito error pages, I'm finding the complexity in these templates could be reduced a good deal and perhaps this is even a case for moving some of the functionality into addons instead.
The current error pages do the following:
readthedocs.org/readthedocs/templates/errors/404/include_tips.html
Line 8 in bf02353
readthedocs.org/readthedocs/templates/errors/404/dns.html
Line 12 in bf02353
Deciding how to port this over though, it feels like what we want out of error pages is:
I'm feeling like it's not clear what is important to port over now that we are surfacing features through addons.
The text was updated successfully, but these errors were encountered: