Skip to content

Restructure README with table of contents, benchmarks table, and expanded documentation#1935

Closed
nityatimalsina wants to merge 1 commit intomainfrom
docs/update-readme-and-summary
Closed

Restructure README with table of contents, benchmarks table, and expanded documentation#1935
nityatimalsina wants to merge 1 commit intomainfrom
docs/update-readme-and-summary

Conversation

@nityatimalsina
Copy link
Copy Markdown

Add table of contents, convert benchmark data to table format, expand use cases section with AI agents/scraping/testing examples, add architecture diagram reference, reorganize build/test sections with collapsible details, and include FAQ section. Improve formatting throughout with horizontal rules and better section hierarchy.

…nded documentation

Add comprehensive table of contents, convert benchmark data to table format, expand use cases section with AI agents/scraping/testing examples, add architecture diagram reference, reorganize build/test sections with collapsible details, and include FAQ section. Improve formatting throughout with horizontal rules and better section hierarchy.
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 20, 2026

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@nityatimalsina
Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

Comment thread README.md
./lightpanda fetch --obey_robots --log_format pretty --log_level info https://demo-browser.lightpanda.io/campfire-commerce/
```

<details>
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.

I know this isn't your edit, but the above command needs a --dump flag.

Comment thread README.md

## Architecture

![Architecture Diagram](architecture-diagram-highres.png)
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 diagram is not correct. There's no libdom, there's no zig-js-runtimes. "computed style sheet" is a huge stretch. Is "Lightpanda Server" referencing a hosted option / layer? Not a term I've heard before.

Copy link
Copy Markdown

@Nicolas0315 Nicolas0315 left a comment

Choose a reason for hiding this comment

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

Coordination note from PR #1954

Hey @nityatimalsina — great work on the README restructure! I've got a related PR (#1954) that adds docs/cdp-serve-guide.md and docs/ai-agent-integration.md to a new docs/ directory.

A few thoughts on how these could work together:

What this PR does well

  • The TOC is a big improvement — the current README is hard to navigate
  • Collapsible build/test sections keep the README scannable
  • FAQ section is useful for newcomers

Suggestions to avoid overlap

  1. Link to docs/ from the README — If #1954 lands, the README's "AI Agent Integration" and "Advanced Configuration" sections could link to the detailed docs rather than duplicating content. This keeps the README as an overview and docs/ as the deep dive.

  2. Benchmarks table format — Your table format is cleaner than the current bullet list. One addition: memory usage per concurrent page count would be very useful for AI agent users (the #1 question we see). We have real measurements in docs/ai-agent-integration.md:

    Pages Lightpanda Chrome Ratio
    1 ~7 MB ~280 MB 40x
    10 ~70 MB ~2.8 GB 40x
    100 ~696 MB ~4.2 GB 6x
  3. Architecture diagram — You reference an architecture diagram. We could collaborate on this — our docs/ai-agent-integration.md has an ASCII architecture diagram showing the CDP integration pattern that could be a starting point.

Happy to coordinate so we don't step on each other's toes. 🤝

@krichprollsch krichprollsch mentioned this pull request Apr 9, 2026
@krichprollsch
Copy link
Copy Markdown
Member

closed in favor of #2114 2114

@github-actions github-actions Bot locked and limited conversation to collaborators Apr 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants