Skip to content

Restructure README - #26

Open
strzibny wants to merge 2 commits into
serpapi:masterfrom
strzibny:update-readme-structure
Open

Restructure README#26
strzibny wants to merge 2 commits into
serpapi:masterfrom
strzibny:update-readme-structure

Conversation

@strzibny

@strzibny strzibny commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

This PR updates our READMEs to a new structure we discussed internally as part of improving our website integration pages.

What changed

I tried to limit this change to the structure changes, but there a couple other minor changes too. Here's what I am changing:

  • Restructured README.md and README.md.erb around Installation, Quickstart, Features, Configuration, Examples, Documentation, Performance, and Contributing.
  • Replaced “wrapper” terminology with “official Ruby SDK.”
  • Added options table
  • Preserved the recently landed Examples section and original Performance sections.
  • Added the 2026 copyright.
  • Used a local ./CONTRIBUTING.md link in README.md and the full GitHub URL in README.md.erb.

I specifically didn't really touch the language or individual sections much to keep this simpler to review.

Note: Tests are failing because I am submitting from a fork.

@strzibny
strzibny requested a review from trusche August 13, 2026 12:31

@trusche trusche left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks @strzibny, LGTM in principle, I like the new structure. Just one suggestion on async documentation

Comment thread README.md
* [API health status](https://serpapi.com/status)

## Advanced search API usage
### Search Asynchronous

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think we should keep a dedicated section explaining async searches in the main README. It can be less verbose and link to the demo code ford details.

@strzibny

Copy link
Copy Markdown
Contributor Author

@trusche I restored it as-is (for now) inside configuration as I feel it's better to keep the Features section light and punchy and explain the details as part of the configuration just after the table with all the options. Wdyt?

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.

2 participants