Developing with tei-publisher
Just started to evaluate the feasibility of using tei-publisher for a project I am working with, I have a few questions regarding the current code.
Since the project will be deployed in Japan, but the target domain also includes Chinese users. It seems currently, the switching of languages is done by using the language code as an index to the i18n collection. For a user facing application, this is not ideal and I would like to use the clear name for the language in the interface. As I understand the code, I would have to modify the $myapp/modules/lib/pages.xql, but this in turn references the component pb-lang.html from the tei-publisher application (not that I fully understand that code yet). So what is the recommended way of making such a modification? I guess in this case a PR might be possible, since this should be of general interest, but I imagine there will be other situations, where this is not feasible.
Should one start collecting such modified pb-* elements locally to the app? Is there a way to reference them in preference to the ones from tei-publisher? What is the recommended way to do this?
Another issue is that the code at the moment seems to be quite repetitive, e.g. there is no page template that pulls out common boilerplate for header, footer, menu etc. This results in code that is difficult to maintain. Is the app developer supposed to come up with such a cascading templating or is this something on the road map? If not, is there a reason not to do this?
These questions might show my ignorance, but I think it is important to address them somewhere. Also, I know that the 4.0 is a moving target, but I hope my comments contribute to better code in the long run.