Skip to content

[Menu item] Reading guide #59

@rianrietveld

Description

@rianrietveld

Note: This content will be written when there is sufficient content to point to.
A system of labeling the topic in the documenation could be useful?

Target groups, with an intro and links to which content is important for them, ideas:

Target groups in random order:

  • Developers in general
  • WP core developers (Admin UX/accessibility)
  • Theme builders
  • Plugin builders
  • Designers
  • Writers (content team)
  • WP theme and plugin clickers (small businesses without technical knowledge). Find a better name for this group
  • Page builders users
  • Project managers
  • Marketing bureaus
  • Project owners etc
  • DIY website owners
  • QA testers

We need to find a way to automate this in a logical way.
Maybe with somthing like labelling, categories, tags?

Possible (to discuss) way for the etup:
Dutch website: https://niekderksen.nl/kennisbank/

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions