Not only that, but both expert users, as well as new users who are learning how to customize their World Anvil projects, will be much better supported in their endeavors. In the end, assuming this is possible and fulfilled, by having an automatically updated repo of article HTML/Twig templates, any new changes and implementations that are made to any of the standard article templates will automatically be picked up by the repo - preventing the need to update them manually. What are other uses for this feature request? This comes with the assumption that the current native HTML/Twig templates that are used by World Anvil are stored in another repo somewhere such that they can be retrieved by the repo that hosts the templates for users looking to customize their world.My idea/approach is to have the GitHub repo that hosts these HTML/Twig templates automatically pull/fetch the most version of them. The solution I have in mind is simple in theory (I hope), but like any implementation, it will incur some degree of a change in the development process/workflow. How does this feature request address the current situation? Alongside that, the twig "dump" command also causes the page to crash when it is used, so it's not possible to gather variables through that method either. Unfortunately though, this doesn't pull any of the internal variables that are associated with the sections of an article, such as variables like "article.age" (in the case of an character/person article. That said, if there was a way to dynamically pull all of an article's twig variables from within an article's twig, such as like this, then that would be great: Which, ultimately, impacts the custom article creation process very negatively due to the fact that any attempts to manipulate or customize current article variables is almost solely dependent on tribal knowledge. However, aside from the fact that these HTML/Twig templates will continue to grow more incongruent with concurrent functionality the longer they go without being updated, there is the even larger issue that users are left to scavange for unaccoutned for variables through trial-and-error. For example, the character/person template is missing a large amount of twig variables that the current default character/person articles have (which isn't too surprising as they have experienced a lot of updates since the GitHub repo was last updated). The problem with these templates is that they haven't been updated in over 2 years and are considerably outdated. When creating a custom article template, the Studio provides access to the following GitHub repo that contains a list of HTML/Twig templates. What functionality is missing? What is unsatisfying with the current situation?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |