Unable to disable sidebar with Gemini

[JOduMonT]

I saw #3421 and @ivan-nginx kindly respond to my question here
but I still going through the issue

Expected

Having a single column page with Gemini Scheme when my header have : sidebar: false

---
layout: page
title: Title of this Page
sidebar: false
---

Current result

I still have a 2column page even I declare sidebar: false in the header of my page

---

1. Do Gemini Scheme support sidebar: false ?
2. What I'm missing ?

[stevenjoezhang]

Nope, sidebar option in front matter is not supported

[ivan-nginx]

@stevenjoezhang #93
@JOduMonT i think it's because layout: page. Only for posts maybe this option support for now.

[JOduMonT]

Non of these works ;(

---
layout: page
title: Title of this Page
sidebar: false
---

---
layout: post
title: Title of this Post
sidebar: false
---

---
title: Title of this Post
sidebar: false
---

It's might simply not my day

[ivan-nginx]

Oh, actually this option not for show or hide sidebar. It's for Muse/Mist shemes to produce automatically slide-in/slide-out sidebar when post will opened. Detailed description here: #93 (comment)
It's for this setting:

hexo-theme-next/_config.yml

Lines 247 to 252 in 6128602

	# Sidebar Display, available values (only for Muse | Mist):
	# - post expand on posts automatically. Default.
	# - always expand for all pages automatically.
	# - hide expand only when click on the sidebar toggle icon.
	# - remove totally remove sidebar including sidebar toggle.
	display: post

But i think we can add just show/hide sidebar on Pisces/Gemini shemes with same option.

---

I only don't understand why u want not to show sidebar on specified page?

[JOduMonT]

oh, to make kind of landing page
since the concept of landing page is to minimize the distraction and to bring the user to make a specific action, the sidebar act as a distraction

[stevenjoezhang]

@JOduMonT Add this to your markdown file:

<style>.sidebar-inner { display: none !important; }</style>

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.