Skip to content

Improve README onboarding section - #489

Open
HussainAther wants to merge 1 commit into
OpenwaterHealth:mainfrom
HussainAther:issue-461-readme-onboarding
Open

Improve README onboarding section#489
HussainAther wants to merge 1 commit into
OpenwaterHealth:mainfrom
HussainAther:issue-461-readme-onboarding

Conversation

@HussainAther

Copy link
Copy Markdown

Closes #461

Summary

This PR improves the onboarding section at the top of the README to help first-time visitors quickly understand the project before reaching the installation instructions.

The new introduction:

  • explains what Open-LIFU is in plain language
  • identifies the primary audiences (developers, researchers, and clinicians)
  • clarifies the current project status, including the ongoing MATLAB → Python migration
  • includes a short research-use-only/FDA disclaimer
  • adds links to the Community Hub, Discord, and Good First Issues

The existing installation instructions and technical setup documentation below the onboarding section are left unchanged.

Motivation

The README is the first entry point for many potential users and contributors. This update provides context about the project, its intended audiences, its current development status, and where new contributors can get involved before diving into installation and technical documentation.

Testing

  • Verified all README links and Markdown formatting.
  • Confirmed that only the onboarding section above the installation instructions was modified.

Comment thread README.md Outdated
@@ -1,18 +1,28 @@
# openlifu
# Open-LIFU

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The python library is called openlifu

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated the wording to consistently refer to the openlifu Python library while keeping the project name as Open-LIFU where appropriate.

Comment thread README.md
Comment on lines -3 to -9
[![Actions Status](https://github.com/OpenwaterHealth/OpenLIFU-python/workflows/CI/badge.svg)](https://github.com/OpenwaterHealth/OpenLIFU-python/actions)
[![Documentation Status](https://readthedocs.org/projects/openlifu/badge/?version=latest)](https://openlifu.readthedocs.io/en/latest/?badge=latest)
Open-LIFU is an open-source Python platform for planning, simulating, and controlling low-intensity focused ultrasound (LIFU) experiments. It helps researchers and developers build reproducible focused ultrasound workflows for planning, medical imaging, acoustic simulation, hardware communication, and experimental research while continuing the capabilities of the original MATLAB open-TFUS toolbox.

[![PyPI version](https://img.shields.io/pypi/v/openlifu)](https://pypi.org/project/openlifu/)
[![PyPI platforms](https://img.shields.io/pypi/pyversions/openlifu)](https://pypi.org/project/openlifu/)
## Who is Open-LIFU for?

[![GitHub Discussion](https://img.shields.io/static/v1?label=Discussions&message=Ask&color=blue&logo=github)](https://github.com/OpenwaterHealth/OpenLIFU-python/discussions)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove badges?

Comment thread README.md
[![GitHub Discussion](https://img.shields.io/static/v1?label=Discussions&message=Ask&color=blue&logo=github)](https://github.com/OpenwaterHealth/OpenLIFU-python/discussions)
**Developers** can contribute to an actively evolving scientific software platform for focused ultrasound research, medical imaging, and hardware integration.

<!-- SPHINX-START -->

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This tells the documentation's home page where to start: https://openlifu.readthedocs.io/en/latest/includeme.html

@HussainAther

Copy link
Copy Markdown
Author

ty for catching these.

restored the openlifu heading, all existing badges, and the SPHINX-START marker, and moved the new onboarding content below them.

@ebrahimebrahim ebrahimebrahim left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing! Added more comments

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
@HussainAther

Copy link
Copy Markdown
Author

Thanks for the suggestions. I updated the onboarding links to prioritize the Quickstart guide, API documentation, Community Hub, and Good First Issues. I left GitHub Discussions/Discord out of the new onboarding until there's broader consensus on which communication channels should be promoted.

@ebrahimebrahim ebrahimebrahim left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, it looks great!

I think just the commit message and formatting needs to be fixed now for the CI to pass.

The commit message can reference #338

@HussainAther
HussainAther force-pushed the issue-461-readme-onboarding branch from 860c452 to 66cd8fd Compare July 28, 2026 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve the Open-LIFU README onboarding section

2 participants