11 explainer page titles are longer than 65 characters (up to 99) and get cut in search results
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Start with scripts/build_explainers.py, assets/explainers-data.json, and tests/test_build_explainers.py, as named in the issue. Check how title is used for generated <title> and og:title, then add coverage for the optional seo_title and the 65-character build limit. Done means all explainer titles fit, an overlong title fails the build, and card titles stay unchanged.
Written by the indexing model from the issue text.
Description
Where: scripts/build_explainers.py (<title> and og:title), assets/explainers-data.json (title), tests/test_build_explainers.py.
Current gap: the generated <title> is the JSON title followed by · Fair Code. Eleven pages are over 65 characters, the point where search results start cutting: counterfactual-explanation (99), multiple-comparisons (99), equal-opportunity (79), bootstrap-confidence-intervals (77), differential-privacy (73), mitigation-strategies (73), obermeyer-cost-proxy (73), false-positives-vs-false-negatives (70), medical-imaging-representation-gaps (70), subgroup-fairness (68) and distributionally-robust-optimization (67). The part cut is the site name and often the distinguishing words.
Suggested approach: add an optional seo_title (at most 60 characters before the site suffix) to the JSON entries for those eleven, used for <title> and og:title only, and have the build fail when any title is longer than 65 characters.
Done when: no explainer <title> is over 65 characters, a longer one fails the build, and the card titles on the site are unchanged.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 4m
- Merged PRs (30d)
- 83
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/Fair-Code
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Numeric column headers keep their type in Python (the integer 2020) and are text in the web enginePossibly taken @snehal1931 claimed this 5 days ago. Openbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yakew7/Fair-Code#1045 · 2 comments ·
Maintainers usually reply within 1 day
-
JSON string cells "NA" and "" are missing in the web engine and ordinary values in PythonPossibly taken @snehal1931 claimed this 5 days ago. Openbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yakew7/Fair-Code#1036 · 2 comments ·
Maintainers usually reply within 1 day
-
check_issue_refs fails a pull request that says it closes an issue the pull request itself closesOpenenhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
DepressionCenter/agentprise#50 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure-Samples/azure-search-openai-demo#3249 ·
Maintainers usually reply within 1 day
-
PubMed _expand_time_window regex never matches (unescaped [pdat]), so adaptive search skips intermediate windowsPossibly taken @jackiectl2 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
LearningCircuit/local-deep-research#7783 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PathOfBuildingCommunity/PathOfBuilding#10395 ·
Maintainers usually reply within 1 day
-
yandex engine: parsing error from a russian IP, yandex.com redirects to yandex.ruPossibly taken @evgeniylebedev claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day