Hi,
Here's some thoughts and examples for you, although I wouldn't recommend this if you had another option.
What CSS does Confluence PDF Export support?
The PDF export is based on an older version of Flying Saucer PDF exporter and it also supports some elements of CSS 3 such as @page, for example.
Themes affect the CSS that displays on the Confluence wiki.
An idea for creating semi-dynamic CSS on Confluence pages
Disclaimer: this is not standard practice and I am not recommending it. It is merely an untested idea of one way you could possibly achieve what you were asking about!
As I said before, I don't know about adding CSS to the stylesheet with PHP, but if you get an admin to add a user macro for you, then you might be able to use velocity if-statements to set up some semi-dynamic conditions and select sections of CSS from your macro to add to a specific page. This would apply to all pages exported together because CSS in Confluence pages gets added to the end of the other CSS in the document that you are exporting.
Here's a simple example of an old-style macro that should output wiki markup depending on parameters set for the macro in the page and using velocity if-statements:
{warning:title=Deprecated Feature}
This feature was deprecated in version *${paramversion}*
#if($parampage)
See [${parampage}] for details of the replacement feature.
#end
{warning}
You'd need to add the parameter definitions to your macro for new versions of Confluence. Then you could make decisions based on the values entered in the macro browser for these parameters.
Here's a simple example of CSS that you can add to a Confluence macro that outputs HTML. If you added this to a Confluence page and exported that page or a group of pages to PDF, it would print without any headers or footers on standard pages and without page breaks before headers, so someone can cut and paste the text only from the PDF, for example.
<style type="text/css">
@page
{
@bottom-left {}
@bottom-center {}
@bottom-right {}
@top-left {}
@top-center{}
@top-right {}
}
@media print
{
h1, h2, h3, h4
{
page-break-before: avoid;
}
}
</style>
So perhaps you could combine these two ideas and create macros with parameters that add different sections of CSS to the page, depending on the macro parameters.
This is assuming that your admins are incredibly friendly and helpful, and you are working on a restricted set of pages that wouldn't harm anyone else's work. Then maybe you could create a macro that had different CSS settings for draft documents, final customer documents, internal documents, etc. and with different parameters that you would enter before you exported to PDF.
Mary-Jane
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.