Light Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Split each section in the documentation to its own separate page #1903

mevitar started this conversation in Ideas and feedback
Split each section in the documentation to its own separate page #1903
Oct 8, 2025 * 0 comments
Return to top
Discussion options

mevitar
Oct 8, 2025

Description

Currently, documentation is divided into 5 sctions: New / Enhanced Logics, Fixed / Improved Logics, AI Scripting and Mapping, User Interface, Miscellanous. This worked fine when there were less features, but as the documentation grows, the amount of pictures and gifs used increases, which also dramatically increases load times. This is especially true for the New / Enhanced Logics section, and it will become even worse.

I suggest splitting at least first two sections into smaller ones. Keep current subsections, but give each of them a separate page.

INI code

No response

Additional context

This should decrease the amount of pictures loaded each time a page in the documentation is opened, and thus, decrease load times (and bandwith used, as i suspect the usage on the server is significant).

Checklist

  • The suggestion is NOT related to functionality of Ares, HAres, Kratos or any other YR engine extension.
  • The suggested feature / enhancement is NOT implemented in Ares/Phobos yet and the existing possibilites are not viable or good enough to achieve the wanted result.
  • I agree to elaborate the details if requested and provide thorough testing if the feature is implemented.
  • I added a very descriptive title to this topic.
  • I used the GitHub search and read the topic list to find a similar topic and didn't find it.
  • I thought out how the feature / enhancement should work and described it in the most detailed and clear way.
You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant