lbryio / lbryio/lbry.com

Remove Odysee references from FAQ

Open
#1,472 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
262
Forks
226
PR merge metrics
No merged PRs in 30d

Description

  • Search non-archived FAQ content for occurrences of the word Odysee and remove them (https://github.com/lbryio/lbry.com/tree/master/content/faq).
  • Remove or replace pictures of odysee.com with the equivalent picture from LBRY desktop.
  • If an article is basically entirely about Odysee, work with @tzarebczan to upload it to https://odysee.com/@odyseehelp instead. Add a redirect for these articles to their new home.
  • If removing a reference to Odysee would make a FAQ confusing for legacy users (most FAQ readers are Odysee users), add a frontmatter tag (odyseelegacy: true).
  • When rendering a FAQ tagged odyseelegacy, add an element (a notice?) at the top of the FAQ that says something like "This article refers to LBRY Desktop or the LBRY network. Go to the [Odysee Help] page to learn about this subject on Odysee."
  • If an article should be on both odysee.com and lbry.com, discuss with me how to approach this.

Contributor guide

No contributing guide indexed for this repository

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 searching the non-archived FAQ content under content/faq for Odysee references and reviewing the related images. Resolve each article according to the requested legacy tagging, notice, redirect, and Odysee Help decisions, coordinating with @tzarebczan where required; done means the FAQ references and pictures are updated and applicable redirects or legacy notices are in place.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.