惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Recent Announcements
Recent Announcements
Martin Fowler
Martin Fowler
MongoDB | Blog
MongoDB | Blog
Engineering at Meta
Engineering at Meta
Stack Overflow Blog
Stack Overflow Blog
Google DeepMind News
Google DeepMind News
Microsoft Security Blog
Microsoft Security Blog
aimingoo的专栏
aimingoo的专栏
I
InfoQ
B
Blog
WordPress大学
WordPress大学
Jina AI
Jina AI
小众软件
小众软件
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园_首页
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
酷 壳 – CoolShell
酷 壳 – CoolShell
阮一峰的网络日志
阮一峰的网络日志
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
G
Google Developers Blog
C
Check Point Blog
月光博客
月光博客
L
LangChain Blog
GbyAI
GbyAI

CloudCannon Blog

Building with AI: Git-based vs headless vs traditional CMS CloudCannon + Astro: performance meets powerful content management Introducing the Astro Component Starter Introducing Jetstream — built on the Astro Component Starter Why we switched to the system font stack Redesigning CloudCannon’s docs with Diátaxis, Lume, and Pagefind Make content editing more visual: upgraded Editable Regions How Configuration Mode makes building editing interfaces easy Your hosting just got an upgrade (and a price cut) Custom testing domains for professional branding Keep your content consistent with input validation Managing multilingual content in CloudCannon Simplify team publishing with conflict resolution and domain tools Open Beta: Publishing Conflict Resolution Getting started with CloudCannon and Astro: Bookshop, components, and live editing Welcome to the CloudCannon Community! Omnichannel delivery is just marketing spin from API-based CMS companies Getting started with CloudCannon and Astro: Snippets and Collections Managing digital assets in CloudCannon: a guide to smart asset storage Understanding CloudCannon's branching workflows and Projects: a complete guide What is a static website? CloudCannon’s 2024 wrapped Getting started with CloudCannon and Astro: WYSIWYG blogging Jamstack vs. WordPress: reasons to make the change The top five static site generators for 2025 (and when to use them!) Free Jekyll themes for 2025: ten great community options Eleventy (11ty) vs. Hugo How to set up WYSIWYG editing with MkDocs Material The rise of static-first websites: why major brands are making the switch Watching your Core Web Vitals on Jamstack
Introducing Subpaths
2019-09-30 · via CloudCannon Blog

Subdomains are a great way to separate different sections of your site. You might have your blog at blog.example.com, your docs at docs.example.com while keeping your main marketing site at example.com. Many companies use subdomains this way and it's easy to set up in CloudCannon.

Subdomains however, are not your only option. The alternative is mounting the sites on subpaths. So blog.example.com becomes example.com/blog/ and docs.example.com becomes example.com/docs/. SEO is the main benefit of doing this as your content is not split between multiple logical sites. Moz are thought leaders in the SEO space and have a great video outlining subdomains vs subpaths.

To achieve this you could create a monolithic Jekyll site that has your blog, docs and marketing site. If you have a small amount of content this works fine, however if you have a large amount of content your build times, content structure and site complexity will soon get out of control. It also means that each individual site can no longer have their own editors and publishing schedule.

Ideally you could build each site individually and mount them at the desired paths on build. The would give search engines and visitors the illusion of a single site when under the hood it's multiple sites. With CloudCannon subpaths you can do exactly this!

How do I use subpaths? Direct link to this section

First set up a site using the primary domain, in the above situation this would be example.com. This site will serve the root and any routes that don't have a subpath.

subpaths dashboard

Once the primary domain is configured we can set the subpath for other sites.

subpaths dashboard

Now anything beginning with the path /blog/ is handled by the second site, everything else is handled by the first.

CloudCannon doesn't rewrite you generate so all links on the second site needs to be prepended with /blog/ (or whatever your subpath is) using Jekyll's baseurl or some other method.

Wrapping up Direct link to this section

Subpaths allow you to split large sites into smaller, more manageable chunks. We hope this helps you create more complex sites on CloudCannon.