How to use Codex to import LinkedIn articles
Stefan C. used Codex to import 17 LinkedIn articles into an Eleventy blog, preserving his site's identity and publishing static pages through Cloudflare Pages.
stefs.site
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Import [article catalogue] into [existing static-site repository]. Preserve [branding], normalize formatting and metadata, and integrate the posts with [site generator]. Show representative imported pages and any conversion problems for my review before publishing.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Stefan C.
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- All 17 existing LinkedIn articles migrated into the author's site.
- Human involvement
- Author steered design before implementation and owns/reviews result.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Gave existing repository, branding, static-site and accessibility requirements.
- Codex created local article content, normalized formatting and integrated posts.
- Eleventy/Nunjucks build deployed from Git to Cloudflare Pages.
Stefan C. wanted the writing he had already published on LinkedIn to live on his own website. His existing site was lightweight, but adding a blog also meant migrating an article catalogue instead of merely choosing a layout.
He gave Codex the real project context and requirements: retain the purple visual identity, support dark mode, keep the site static, integrate the blog with the existing homepage and consider accessibility, SEO and performance. He also wanted design decisions discussed before implementation progressed too far.
Codex imported all 17 LinkedIn articles into the site's local content structure. The account describes normalization, file creation and integration with the rest of the blog as the repetitive work the agent handled. The resulting content uses Markdown with metadata, rendered by Eleventy and Nunjucks templates. Cloudflare Pages runs the project's build command and publishes the generated files from Git.
Stefan says he still owns and reviews the result. His reported zero-cost hosting refers to the blog workload, excluding the domain and AI tooling.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Blog · Stefan C.
Frequently asked questions
What content was migrated?
The author reports that all 17 existing LinkedIn articles became local static blog content in his own website repository.
What generates the published pages?
Eleventy reads Markdown articles and Nunjucks templates. Cloudflare Pages builds the repository and publishes the generated static output.
Was this an entirely unattended migration?
The author supplied requirements, steered design decisions before implementation and says he still owns and reviews the result.
More details
About this account
Codex imported and normalized a multi-file article catalogue and integrated it into the existing static-site project.
Primary first-person account opened and checked on 2026-10-14. Hosting cost claim excludes domain and AI tooling; migration is author's report. Outcomes and test claims are attributed to the source and were not independently reproduced. Prompt is suggested by Agents In Use, not the author's quoted prompt.
Credit: Stefan C. on Blog
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · Eleventy · Nunjucks · GitHub · Cloudflare Pages
Article migration · Eleventy · Static publishing
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.