Skip to content

Suggestion: [Feature] Add customizable “Back to Top” links and multi-language support in README template #158

@ayu-yishu13

Description

@ayu-yishu13

Summary

It would be great to enhance the existing README template with two valuable features:

  1. "Back to Top" links — Easy navigation for longer READMEs.
  2. Multi-language support placeholders — Allow maintainers to scaffold translated sections (e.g., Chinese, Spanish) in README markdown.

Motivation & Benefits

  • Better navigation: "Back to Top" links improve usability by reducing scrolling, especially in templates with extensive documentation.
  • Internationalization readiness: Placeholder sections for translations help open-source projects reach a broader, global contributor base without manual structure changes per language.

Proposed Enhancements

1. Add "Back to Top" Links

Enrich sections like:

Roadmap

✅ Roadmap for Enhancements

Phase 1: Navigation Improvements

  • Add "Back to Top" links at the end of each major section (e.g., Installation, Usage, Roadmap, Contributing, License).
  • Ensure the Table of Contents supports smooth anchor navigation.

Phase 2: Multi-Language Support

  • Create a Translations section in the main README with placeholders for:
    • English (default)
    • Español
    • 中文
    • Français
  • Add guidelines in CONTRIBUTING.md for adding translations.

Phase 3: Optional Enhancements

  • Add a README Template Localization Folder (/i18n) to store translated versions of the README.
  • Include a language switch badge (using Shields.io) for quick navigation between languages.

Phase 4: Pull Request

  • Submit a PR with:
    • Updated README with Back to Top links.
    • Placeholder for translations.
    • Contribution guidelines for translations

Back to Top

###Motivations

I’ve observed several README templates in the ecosystem support both "Back to Top" nav links and translation readiness — they significantly aid in accessibility and global collaboration. I think adding these small yet impactful features would elevate the usability and adoption of this template.

Would love feedback or suggestions on how best to integrate these. I’m open to submitting a PR if this aligns with the project’s direction!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions