Add namespaces to code examples in docs

Open
#67 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, yaml
Domain
documentation

Research direction

The issue does not name specific files or tests. Start by inventorying code examples throughout the documentation, then identify which examples use Silverstripe namespaces and which formats, such as YAML or GraphQL, have different namespace requirements. Done means every applicable example clearly shows namespaces without adding them where the format does not require them.

Written by the indexing model from the issue text.

Description

complexity/low impact/medium type/docs

Currently most of the code examples in the docs do not include namespaces. This is a holdover from the SS3 days, and can in some cases result in a lack of clarity over whether namespaces should be included (e.g. most yaml config needs it but graphql for example doesn't always need namespaces).

We should add namespaces to all of the code examples so that it's clear how namespaces fit in with Silverstripe code.

Dominant language
No language data
Stars
7
Forks
74
Avg merge
1d 14m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from silverstripe/developer-docs

All issues in silverstripe/developer-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.