Skip to content

CTs notes on multi-format editing content #1

@ChristinaTromp

Description

@ChristinaTromp
  • In this section under point 4, I think 'easier collaboration' and 'proper version-control' aren't 'tools', they're abilities or improvements. The tool would be git, as an example. Could rephrase to 'When we plug our work into the Internet, our new tools give us: easier collaboration and proper version-control.'

  • in this section I don't think the conclusion 'One master version of all content.' is sufficiently argued for, but maybe you want to do that elsewhere?

  • In this section , the following paragraphs don't really make sense to me:

'First we have to decide which links need to appear in print. Links are ugly in print, and since not all links are important we can choose which ones to show in print. So we either:

  • make all links just clickable text, and choose which ones to show as full URLs in print, or
  • include all full URLs, and choose which ones to hide on screen.

Since your publication will appear on more screens you don’t control than on printed pages you don’t control, option 1 is best.'

  • The capitalisation section could mention something about file naming, or maybe it should be put somewhere else.

  • In the images section you could mention something about tables.

  • in this section in 'When choosing or developing your production workflow and software, investigate whether they allow for automating these kinds of choices.' I'm not sure 'choices' is the right word, maybe the sentence should be rephrased.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions