morningman opened a new pull request, #4104:
URL: https://github.com/apache/doris-website/pull/4104
## Versions
- [ ] dev
- [ ] 4.x
- [ ] 3.x
- [ ] 2.1 or older (not covered by version/language sync gate)
## Languages
- [ ] Chinese
- [x] English
- [ ] Japanese candidate translation needed
## Docs Checklist
- [x] Checked by AI
- [ ] Test Cases Built
- [x] Updated required version and language counterparts, or explained why
not
- [x] If only one language changed, confirmed whether source/translation
counterparts need sync
---
Blog-only change. The site blog is English-only, so there is no localized or
versioned counterpart to update.
### 1. `dbt-for-apache-doris 1.1.0` blog
Adds the post and a follow-up wording pass over its summary and body.
### 2. Eight new blog entries (2026-07-10 → 2026-08-27)
Added as external-link entries, following the pattern of #3996, with cover
images under `static/images/blogs/`.
| Date | Title | Tag |
| --- | --- | --- |
| 2026-07-10 | Databricks RT and LTAP are here. How does it fit into OLTP,
OLAP, real-time OLAP, and HTAP | Tech Sharing |
| 2026-07-17 | Apache Doris Gets Rust-Native Streaming Ingestion with Apache
Iggy | Tech Sharing |
| 2026-07-24 | Search in Apache Doris 4.1: Unifying Full-Text Log Search and
Real-Time SQL Analytics | Tech Sharing |
| 2026-07-31 | How Meituan Consolidated Its Analytics Stack on Apache Doris
| Best Practice |
| 2026-08-06 | Apache Doris Python UDF: Calling the Python Ecosystem from
SQL for Agent-Era | Tech Sharing |
| 2026-08-12 | From Spark to Apache Doris: How Kwai Made A/B Testing Metrics
145x Faster at Scale | Best Practice |
| 2026-08-21 | PostgreSQL CDC to Apache Doris: Real-Time Sync with One SQL
Statement | Tech Sharing |
| 2026-08-27 | Dynamic JSON in Agent Workloads: Apache Doris vs ClickHouse,
Elasticsearch, and OpenSearch | Tech Sharing |
The Blog header selection (`picked`/`order`) moves onto the four newest of
these, and `src/components/recent-blogs/recent-blogs.data.ts` and
`src/constant/newsletter.data.ts` are refreshed to match.
Titles and summaries are kept vendor-neutral: the Iggy post is titled
"Apache Doris Gets Rust-Native Streaming Ingestion with Apache Iggy", and the
Search 4.1 summary reads "Apache Doris 4.1 uses `search()` …". Authors follow
the original posts and the existing `Company · Name` convention.
### 3. Render the remaining external-link stubs as MDX
28 external-link stubs were still `.md`. `markdown.format` is `detect`, so
those files were parsed as CommonMark: their two `import` lines rendered as
literal body text on the post page, and the `see more` link never rendered at
all. Renaming them to `.mdx` fixes both.
Before / after, on
`/blog/how-stepfun-built-agent-observability-platform-with-apache-doris`:
```
import { BlogLink } from '../src/components/blogs/components/blog-link';
import { SeeMore } from '../src/components/blogs/components/see-more';
StepFun built StepTrace, a PB-scale agent observability platform ...
<- no link
```
```
StepFun built StepTrace, a PB-scale agent observability platform ...see more
-> velodb.io/blog/...
```
The file extension is not part of the slug, so every URL is unchanged.
Full-content `.md` posts that merely carry an `externalLink` render correctly
as CommonMark and are left alone; converting them would risk MDX compile
failures on their raw HTML.
### Validation
Local dev server (`SKIP_DOCS=true SKIP_COMMUNITY=true SKIP_RELEASES=true
SKIP_COURSE=true SKIP_SEARCH=true yarn start`):
- compiles with no errors or warnings;
- all 76 external-link stub pages render without literal `import` text and
with a working outbound link;
- `/blog` shows `Total 200 items`, no broken images, no console errors;
- 207 blog routes generated, unchanged by the renames.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01K1oeAcA8WQ3XKYeNxLDKbW
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
