jamespandClaude Opus 5
873dcc1892
WordPress expands shortcodes at render time via do_shortcode(), so the raw post_content the export reads still contains them literally. All ten [caption] instances were being written straight into the Markdown and rendered as visible markup -- the Hosting page led with [caption id="attachment_205" align="aligncenter" width="300"]. They now become the same div.wp-caption / p.wp-caption-text structure WordPress produces, which the ported theme CSS already styles. The shortcode is swapped for a placeholder before the HTML->Markdown pass and rebuilt after, so the image inside stays Markdown and still goes through Astro's image pipeline rather than being frozen as raw HTML pointing into src/assets, which would not resolve at runtime. [caption] is the only shortcode in use -- no gallery/embed/video/audio. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Astro Starter Kit: Minimal
npm create astro@latest -- --template minimal
🧑🚀 Seasoned astronaut? Delete this file. Have fun!
🚀 Project Structure
Inside of your Astro project, you'll see the following folders and files:
/
├── public/
├── src/
│ └── pages/
│ └── index.astro
└── package.json
Astro looks for .astro or .md files in the src/pages/ directory. Each page is exposed as a route based on its file name.
There's nothing special about src/components/, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.
Any static assets, like images, can be placed in the public/ directory.
🧞 Commands
All commands are run from the root of the project, from a terminal:
| Command | Action |
|---|---|
npm install |
Installs dependencies |
npm run dev |
Starts local dev server at localhost:4321 |
npm run build |
Build your production site to ./dist/ |
npm run preview |
Preview your build locally, before deploying |
npm run astro ... |
Run CLI commands like astro add, astro check |
npm run astro -- --help |
Get help using the Astro CLI |
👀 Want to learn more?
Feel free to check our documentation or jump into our Discord server.