Skip to content

Content Reuse #58

@jmatsushita

Description

@jmatsushita

The advice from @alnermcgunn on this is that there are many dimension to content that are as many obstacles to reuse:

  • Editorial Style
  • Format (mobile, web, print)
  • Audiences
  • Purpose (informational, educational,...)
  • Granularity (course/lesson, how-to, tool,...)

Other obstacles would be making the packaging, "client" use and upstream contribution workflows seamless.

Finding an practical example of a content package that could be a good candidate for reuse would be a good first step to explore this idea. Maybe a module on "Using PGP"...

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