wagtail / wagtail/guide

Update content based on keywords research

Open
#215 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content
Dominant language
Python
Stars
36
Forks
39
Avg merge
2d 5h
Merged PRs (30d)
3

Description

From #90 – we have keywords research we can use to inform documentation changes:

In terms of content. I have done a keyword research (attached). The search volumes are global as I know that we are aiming at a global market. Even still there aren't a huge number of keywords there, simply because search interest is relatively low.

Hopefully a copywriter or content editor could look at these and create some content based on these. I think the best opportunities are the 'vs' keywords, and the long tails where users are asking specific questions.

Wagtail Editor - Keyword research.xlsx


For additional keywords, I have pulled all of the queries from Google Search Console.

These are the real-world queries that users have used to find the site. There are a lot of not very relevant keywords in there that are very broad and don't directly relate to Wagtail. But I have left them in for someone to sense check, as I don't have all the context. There might be something useful in there.

I have added a column at the end that you can use to filter the view to look at just Wagtail-specific keywords.

Wagtail editor - GSC keywords.xlsx

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.

Research direction

Start by reviewing the two attached keyword spreadsheets and comparing their queries with the guide's existing content. The issue names no target pages, files, or acceptance criteria, so define the content scope and what published updates would count as done before making changes.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.