[DOC] Downloadable PDF Developer Guides

[aryasoni98]

Description

This PR implements automated PDF generation for OpenSearch documentation guides, addressing user requests for downloadable PDF versions of developer guides and other documentation sections.

Key Features:

• Automated PDF Generation: Uses Puppeteer to convert HTML documentation pages to PDF format
• Collection-Based Organization: Generates separate PDFs for major documentation sections (Developer Guide, Getting Started, API Reference, etc.)
• CI/CD Integration: Separate GitHub Actions workflow that runs weekly and can be triggered manually, without impacting main build time
• Optimized Implementation: Reads directly from built _site/ directory using file:// protocol (no server required)
• Configurable: Easy to add/remove collections via pdf-config.json

Implementation Details:

• Added generate-pdfs.js script (root level, following existing script patterns)
• Added package.json with Puppeteer dependency
• Added pdf-config.json configuration file
• Created .github/workflows/generate-pdfs.yml CI workflow
• Updated DEVELOPER_GUIDE.md with PDF generation documentation
• Updated .gitignore to exclude generated PDFs and node_modules

Benefits:

1. User-Friendly Search: Users can download complete guides and search across all content using Ctrl+F in a single document
2. AI Integration: PDFs can be uploaded to AI tools (ChatGPT, NotebookLLM, etc.) for knowledge summarization and question-answering
3. Offline Access: Complete documentation available for offline use
4. Non-Blocking: PDF generation runs separately from main build, ensuring no impact on documentation deployment time

Issues Resolved

Closes #11192

Version

all

Frontend features

N/A - This is a backend/infrastructure change for PDF generation. No frontend UI changes are included in this PR.

Checklist

• By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developer's Certificate of Origin.

For more information on following the Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged.

Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer.

When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review.

[kolchfa-aws]

@peterzhuamazon Could you review this PR?

[kolchfa-aws]

@aryasoni98 Thanks for this addition! Looks like you've picked up some extraneous commits - could you rebase against main so this PR contains only the relevant commits?