Public output

[raquelalegre]

Needs more requirements refinement on how this should look like and what it contains. How is it built and by whom?
Might need category public/private for each object field.

Estimate assumes the following mechanism:

• Each object assigned an editable draft / published status
• Admin contains a switch to make all published items public (or not)

[raquelalegre]

Since we are probably doing vincula, and italic and bold using CSS to display non-standard characters correctly, we will need to have a mechanism to generate the final project's output that also can use a similar way to display the text correctly based on HTML and CSS.

We will have to produce a version of the pages that History want us to render with inline styles (e.g. each tag has its own style). We can then render this using this Django module that renders HTML with inline styles:

https://github.com/roverdotcom/django-inlinecss

They have mentioned they want an output PDF file, as well as the TEI-XML version. Peter has found this tool we could use for the PDF so it shows the text as it shows in the browser:

https://wkhtmltopdf.org/

We need to ask History to think about how they'd like the output to look like so Peter can work on it before end of January.

[jonc125]

How does this relate to #90?

[apitta0188]

Essential, but not for now

[raquelalegre]

The editorial has a digital department with software developers who can talk to us and agree what's the best way to get the data from our database into the published edition. So, we don't need to worry about exporting the content of the database into a PDF or printable format.