langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 04:15:25 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #2697] docs: add HWP/HWPX document loader integration page #2805

New Issue
Open
opened 2026-06-05 18:20:01 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:20:01 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/2697
Author: @jaypakdevkr
Created: 2/18/2026
Status: 🔄 Open

Base: main ← Head: feat/hwp-hwpx-loader-docs

📝 Commits (2)

  • c1e31ae docs: add HWP/HWPX document loader integration page
  • 0957b3a Merge branch 'main' into feat/hwp-hwpx-loader-docs

📊 Changes

2 files changed (+68 additions, -0 deletions)

View changed files

➕ src/oss/python/integrations/document_loaders/hwp_hwpx.mdx (+66 -0)
📝 src/oss/python/integrations/document_loaders/index.mdx (+2 -0)

📄 Description

Overview

This PR adds a new Python document loader integration page for HWP/HWPX files.

What was added

  • New guide page:
    • /src/oss/python/integrations/document_loaders/hwp_hwpx.mdx
  • Index updates:
    • Added HwpHwpxLoader in the Common file types table
    • Added HWP/HWPX card in All document loaders

Why

HWP/HWPX is still commonly used in Korean public-sector and enterprise document workflows.
Industry estimates suggest Hancom Office accounts for roughly 30% of the office-suite market in Korea (source included in the new doc page).

Type of change

Type: New documentation page

Related issues/PRs

  • GitHub issue: closes #2696
  • Feature PR: N/A
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

Additional notes

  • Local build check passed with make build.
  • AI assistance disclosure: This PR was drafted with help from an AI coding assistant, and I reviewed and validated the final changes manually.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/2697 **Author:** [@jaypakdevkr](https://github.com/jaypakdevkr) **Created:** 2/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/hwp-hwpx-loader-docs` --- ### 📝 Commits (2) - [`c1e31ae`](https://github.com/langchain-ai/docs/commit/c1e31ae9f69cee5aab954022fd91bbb6bc5c4d5b) docs: add HWP/HWPX document loader integration page - [`0957b3a`](https://github.com/langchain-ai/docs/commit/0957b3a8fb3142bf3c33d76e1ab0b94a3f3ebd93) Merge branch 'main' into feat/hwp-hwpx-loader-docs ### 📊 Changes **2 files changed** (+68 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `src/oss/python/integrations/document_loaders/hwp_hwpx.mdx` (+66 -0) 📝 `src/oss/python/integrations/document_loaders/index.mdx` (+2 -0) </details> ### 📄 Description ## Overview This PR adds a new Python document loader integration page for HWP/HWPX files. ### What was added - New guide page: - `/src/oss/python/integrations/document_loaders/hwp_hwpx.mdx` - Index updates: - Added `HwpHwpxLoader` in the **Common file types** table - Added `HWP/HWPX` card in **All document loaders** ### Why HWP/HWPX is still commonly used in Korean public-sector and enterprise document workflows. Industry estimates suggest Hancom Office accounts for roughly 30% of the office-suite market in Korea (source included in the new doc page). ## Type of change **Type:** New documentation page ## Related issues/PRs - GitHub issue: closes #2696 - Feature PR: N/A - Linear issue: - Slack thread: ## Checklist - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed ## Additional notes - Local build check passed with `make build`. - AI assistance disclosure: This PR was drafted with help from an AI coding assistant, and I reviewed and validated the final changes manually. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:20:01 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#2805
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?