feat: display title in frontmatter as heading fallback

[JounQin]

Summary

Related Issue

close #1440

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for aquamarine-blini-95325f ready!

Name	Link
🔨 Latest commit	32abcfe
🔍 Latest deploy log	https://app.netlify.com/sites/aquamarine-blini-95325f/deploys/6760e33faa3f9500089fdbdc
😎 Deploy Preview	https://deploy-preview-1556--aquamarine-blini-95325f.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 91 (🟢 up 9 from production) Accessibility: 97 (no change from production) Best Practices: 92 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Timeless0911]

Thanks, I think this should be an opt-in feature with documented.

[chenjiahan]

@Timeless0911 This feature should be the default behavior as it does not introduce breaking changes. Do you have any concerns?

[Timeless0911]

@Timeless0911 This feature should be the default behavior as it does not introduce breaking changes. Do you have any concerns?

The behavior of automatically adding titles should be made optional with exclude options. Users may insert relevant titles by themselves through other slots or scripts, and we also need some ways to disable this behavior on some pages such as overview page.

[chenjiahan]

Users may insert relevant titles by themselves through other slots or scripts,

This doesn't seem to be common. It's relatively rare for the page title to be different from the h1 heading. I prefer providing an option to opt-out rather than opt-in.

[Timeless0911]

This doesn't seem to be common. It's relatively rare for the page title to be different from the h1 heading. I prefer providing an option to opt-out rather than opt-in.

Agreed. Providing an options is needed, and the default value can be true though.📌

[JounQin]

I added an fallbackHeadingTitle themeConfig option.

[Timeless0911]

LGTM

[Timeless0911]

I remember that in overview component, we deal title in a specific way, can you compatible with this case?

rspress/packages/theme-default/src/components/Overview/index.tsx

Lines 277 to 292 in c626c66

	const overviewTitle = title || 'Overview';
	return (
	<div className="overview-index mx-auto px-8">
	<div className="flex flex-col sm:flex-row items-start sm:items-center justify-between mb-10">
	<h1 className="text-3xl leading-10 tracking-tight">{overviewTitle}</h1>
	{/* Added search input */}
	<SearchInput
	query={query}
	setQuery={setQuery}
	searchRef={searchRef}
	filterNameText={filterNameText}
	filterPlaceholderText={filterPlaceholderText}
	/>
	</div>
	{content}

[JounQin]

I remember that in overview component, we deal title in a specific way, can you compatible with this case?

The title already reads frontmatter.title. I'm not sure what you expect to render.

Current:

---
overview: true
title: API Overview
---

# xxxx

---
overview: true
---

# xxxx

[Timeless0911]

In this case, I think we should avoid to render two H1 in content?

And what will be rendered if we write like below that without H1 xxxx

---
overview: true
title: API Overview
---

[JounQin]

In this case, I think we should avoid to render two H1 in content?

I believe this is out of scope of this PR, the behavior doesn't change between it, so maybe a new PR for it is more suitable.

And what will be rendered if we write like below that without H1 xxxx

It doesn't change:

[Timeless0911]

Oh I forget that Overview do not use docContent to render.

I think this PR is good enough to merge, thank you!