Adapt title page for article layout (Smart Docs, TRD and SBP)

[ghost]

What we want...

• on the title page
  • title
  • subtitle
  • product(s)
  • abstract
  • series title ("SUSE Best Practices")
  • SUSE logo
  • optionally: doc team logo
• on the second page:
  • TOC

[chabowski]

Hey there, also here just checking where we are :-). On title page, we also need the author's details.

[ghost]

Hm... Yes, you are right, will see if I get to it this week.

[chabowski]

And there is a next request: for SBP's we write together with business partners, we need an option to add a second logo /business partner logo

[chabowski]

So sorry - but here comes the next request: Currently, the license information is immediately following after the final sentence of a best practices paper. Would it be possible to just add it starting on a new page? Thanks a ton !!

[ghost]

Aah, I think not, unfortunately. I'll try to see if we can force it though. However, there is the issue that the original DocBook styles do not allow changing page style at that point. For example, we already wanted to use a two-column layout for the license and could not. (In books, we can.)

However, do you actually need the Best Practices to have a license document? I thought we sorta-kinda agreed upon using a CC-* license, where it would be enough to link to the license text.

[tomschr]

Summary: Titlepage contains the SUSE geeko head (in light colors as a water mark) and the SUSE logo on the bottom right corner. Other logos appear on the left side of SUSE's logo.

[janajaeger]

Requirements as of July 2022:

• [x] SUSE logo to the top left
• [x] Series name either to the top right corner or right on top of the title
• [x] ~Series icon?~
• [x] Title
• [ ] two subtitles (actually one subtitle and one element/meta tag describing a category (for TRDs), docinfo file!)
• [x] unlimited number of authors (docinfo file?)
• [x] up to five logos at the bottom page to include partner logos etc. Make sure each and every single one of them is treated equally (docinfo file)
• [x] use some sort of colored element to mark the series (different shade of green or some other SUSE color entirely)
• [ ] clearer distinction between executive summary and disclaimer (maybe use two or three abstracts, add titles and role/condition to add distinctive styling. What about AsciiDoc?)
• [x] actual publication date (done manually!)
• [x] ~Git version info?~
• [ ] Page break for TOC
• [ ] Include second level entries in TOC (tread with care. Has potential to mess things up big time. One type of TOC for all article types, please!) - processing instruction maybe? MUST for TRD, nice to have for SBP, probably not needed for Smart Docs

[janajaeger]

@chabowski any requirements beyond that? Mockups are in the works.

[chabowski]

Requirements as of July 2022:

• [x] SUSE logo to the top left
• [ ] Series name either to the top right corner or right on top of the title
• [x] ~Series icon?~
• [ ] Title
• [ ] two subtitles (actually one subtitle and one element/meta tag describing a category (for TRDs), docinfo file!)
• [ ] unlimited number of authors (docinfo file?)
• [ ] up to five logos at the bottom page to include partner logos etc. Make sure each and every single one of them is treated equally (docinfo file)
• [ ] use some sort of colored element to mark the series (different shade of green or some other SUSE color entirely)
• [ ] clearer distinction between executive summary and disclaimer (maybe use two or three abstracts, add titles and role/condition to add distinctive styling. What about AsciiDoc?)
• [ ] actual publication date (done manually!)
• [x] ~Git version info?~
• [ ] Page break for TOC
• [ ] Include second level entries in TOC (tread with care. Has potential to mess things up big time. One type of TOC for all article types, please!) - processing instruction maybe? MUST for TRD, nice to have for SBP, probably not needed for Smart Docs

Some comments:

• I would prefer the series title to be placed on the top right corner, not on top of the title. The area where the title is placed will become quite "overloaded" at least for some of the SBPs, because some of them have long titles.
• Some parameters for AsciiDoc documents are also defined via attributes in the DC file (e.g. the date of the document, which needs to be updated / added manually), not just in the docinfo file meta data. DC files for TRDs look quite interesting.
• Need to check if logos can be added to AsciiDoc documents via docinfo file and the elements.
• Color-coding for the different series' would be amazing ...

[janajaeger]

These two are the favorites so far. Let's discuss whether we can implement similar things and how to distinguish between SBP and TRD realm.

Title page with light bulb icon:

Title page with tools icon:

[tomschr]

Seems a duplicate of #215

[chabowski]

This one is mainly capturing the notes from the TRD discussions in the "requirements" section above from July 2022. So, it is NOT superfluous or unneeded, but contains a lot of valuable and important details from the discussions with Terry and Bryan. We could "merge" the two issues and add the missing comments to #215 if you prefer to have only one issue open? Thanks!