Open ghost opened 8 years ago
I guess, the best way is to have stylesheets which allow easier customizations through parameters. This would usually be the preferred way. I'm not sure if there is an "easier" solution like the above.
From a technical point of view, this is stable and already documented.
That question is, what is considered to be "easy"? Setting parameters is probably very easy, writing customization layers probably not.
However, there will always be something that can't be tackled with parameters. You can't avoid customizations if you need something that is out of scope.
Maybe we should solve that from two side: create stylesheets that are easier to customize (or extend the existing ones) plus improve our (non-existing) DAPS Developer Guide.
I suggest a completely different approach:
A config file could look like this:
##############################
# TITLEPAGE #
##############################
# background image og title page
# Default value: /usr/share/xml/stylesheets/docbook/foo/static/images/logo.png
#
TP_BG_IMAGE="/usr/share/xml/stylesheets/docbook/foo/static/images/logo.png"
# Title page headline font
# Default value: sans whatever
#
TP_HEADLINE_FONT="sans whatever"
##############################
# CHAPTER #
##############################
...
It would be nice to have some way to easily replace colors, images, logos, and maybe fonts that appear in documents. This would be akin to Publican's "brands".
Alternatively, if this is already possible, we should probably document, how.