Tidy up documentation for print

[alikstimix]

Having a "print view layout" page separate from the "overview" page looks like overkill.

I recommend merging the first two paragraphs and the overlay section into the "overview" page, then deleting the "print view layout" page.

[paperdigits]

That would make printing different from the rest of the structure of the manual. I am not sure that is desirable.

On July 17, 2024 2:16:37 AM PDT, Aliks @.***> wrote:

Having a "print view layout" page separate from the "overview" page looks like overkill.

I recommend merging the first two paragraphs and the overlay section into the "overview" page, then deleting the "print view layout" page.

-- Reply to this email directly or view it on GitHub: https://github.com/darktable-org/dtdocs/issues/665 You are receiving this because you are subscribed to this thread.

Message ID: @.***>

[alikstimix]

Well I was going to come on to that! The idea of a common structure seems to have lapsed a bit, and some tidying up in each section could restore a common structure with general information at the top level, detailed information at the bottom.

Each of the 6 views has a top level with no text, just a bulleted list of sections starting with "overview" and ".. view layout"

The overview sections differ wildly in content: Lighttable just has another bulleted list of shortcuts Darkroom has nothing much in the overview Tethering has a bulleted list of shortcuts Maps describes how to use the maps view Slideshow just has some boilerplate text Print has some two sentences of basic howto then 2 paragraphs of technical discussion

The view layout sections do follow a standard format (apart from slideshow) listing all the modules that can be accessed, with a short description and a link to their page of detailed info

So taking your point onboard, it seems like the content of the overview section needs to be reallocated with a sentence of general description going upward, and the rest merging downward as a navigation section of the ..view_layout page

If the common structure is clear, then it should be easier to relocate some of the detailed material that is currently scattered across the patch.

[github-actions[bot]]

This issue has not had any activity in the past 60 days and will be closed in 365 days if not updated.

[github-actions[bot]]

This issue has not had any activity in the past year and has therefore been closed.