ansible / ansible/docsite

Possible broken redirects some some docs

Open
#85 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
HTML
Stars
24
Forks
15
PR merge metrics
No merged PRs in 30d

Description

From https://search.google.com/search-console/index/drilldown?resource_id=sc-domain%3Aansible.com&item_key=CAMYHyAE

1. http://docs.ansible.com/ansible/win_copy_module.html
2. http://docs.ansible.com/ansible/vmware_vswitch_module.html
3. http://docs.ansible.com/ansible/file_module.html
4. http://docs.ansible.com/ansible/ec2_vpc_route_table_module.html
5. http://docs.ansible.com/ansible/win_service_module.html
6. http://docs.ansible.com/ansible/pause_module.html
7. http://docs.ansible.com/ansible/rax_scaling_group_module.html
8. http://docs.ansible.com/ansible/YAMLSyntax.html
9. http://docs.ansible.com/ansible/playbooks.html
10. http://docs.ansible.com/ansible/intro.html
11. http://docs.ansible.com/ansible/wait_for_module.html
12. http://docs.ansible.com/ansible/intro_installation.html
13. http://docs.ansible.com/ansible/playbooks_roles.html
14. http://docs.ansible.com/ansible/playbooks_filters.html
15. http://docs.ansible.com/ansible/intro_configuration.html
16. http://docs.ansible.com/ansible/iam_module.html
17. http://docs.ansible.com/ansible/playbooks_lookups.html
18. http://docs.ansible.com/ansible/playbooks_loops.html
19. http://docs.ansible.com/ansible/template_module.html
20. http://docs.ansible.com/ansible/intro_inventory.html

Once fixed (and live) we should click `VALIDATE FIX` on https://search.google.com/search-console/index/drilldown?resource_id=sc-domain%3Aansible.com&item_key=CAMYHyAE

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 checking the 20 listed legacy documentation URLs and the repository's static HTML and assets to identify which redirects are broken. Confirm each URL reaches the intended current documentation page, deploy the fixes, and use Google Search Console's VALIDATE FIX action once the changes are live.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.