Blog index page title reads "Open Data Capture - Open Data Capture"
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Read apps/outreach/src/pages/[locale]/blog/index.astro and the title entry in apps/outreach/src/i18n/translations/blog.json. Update the title composition to use the localized blog heading with the site name, then build apps/outreach as described in its AGENTS.md. Confirm dist/en/blog/index.html and dist/fr/blog/index.html contain the expected localized titles.
Written by the indexing model from the issue text.
Description
The blog index's <title> reads "Open Data Capture - Open Data Capture" in both languages. The page builds its title from t('meta.title') twice instead of pairing the blog heading with the site name. The browser tab, bookmarks, search results and the og:title share card all show the duplicated site name and never say that the page is the blog.
Where
apps/outreach/src/pages/[locale]/blog/index.astro:28:
<Page bilingual meta={{ title: `${t('meta.title')} - ${t('meta.title')}` }}>
apps/outreach/src/i18n/translations/blog.json already has the key for the first half:
"title": {
"en": "Blog",
"fr": "Blogue"
}
Reproduce
- Open https://opendatacapture.org/en/blog/ (or
/fr/blog/). - Read the browser tab title, or the page's
<title>andog:titlein the source.
Actual: "Open Data Capture - Open Data Capture".
Expected: "Blog - Open Data Capture" in English and "Blogue - Open Data Capture" in French.
Tests
apps/outreach has no unit or Playwright suite, by decision (apps/outreach/AGENTS.md). Verify through the build: dist/en/blog/index.html and dist/fr/blog/index.html contain the localized blog title.
Suggested fix
Use `${t('blog.title')} - ${t('meta.title')}`.
- Dominant language
- TypeScript
- Stars
- 119
- Forks
- 19
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 44
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 DouglasNeuroInformatics/OpenDataCapture
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
DouglasNeuroInformatics/OpenDataCapture#1813 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DouglasNeuroInformatics/OpenDataCapture#1812 ·
Maintainers usually reply within 1 day
-
Area: Playground Bug Difficulty: Low Good First Issue Priority: Low
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
DouglasNeuroInformatics/OpenDataCapture#1805 ·
Maintainers usually reply within 1 day
-
Area: Instruments Bug Difficulty: Low Priority: Low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
DouglasNeuroInformatics/OpenDataCapture#1801 ·
Maintainers usually reply within 1 day
-
Area: Instruments Bug Difficulty: Low Good First Issue Priority: Low
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
DouglasNeuroInformatics/OpenDataCapture#1800 ·
Maintainers usually reply within 1 day
All issues in DouglasNeuroInformatics/OpenDataCapture
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melgarafael/DeskcommCRM#3000 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
aws/agentcore-cli#2606 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 7 days
-
ai-driven-qa bug Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day