faq editor isn't writing guides with `layout: qna`

[nonowazu]

It's in the config, but I don't know why it isn't writing. It could be because there's the old guides and new. We might need to manually edit these in the feat/getting-glam-orous branch just to make soft launch happen.

[OHaiDanny]

Hey @nonowazu.

I followed the instructions you given me to replicate and reproduce the issue. I did in the local admin to create some q/a content in netlify and I did notice it was not populating in the WAR's qna page.

I noticed that the WAR's qna page looked different from the SCH's qna page. After investigation it looked like the WAR's qna page was using single.html template to generate its data instead of the supposed qna.html.

I checked that there was no issue in the config.yoml file.

I noticed after investigating the template logic that the WAR's faq.md is missing the layout:qna parameter and value.

Once I've added this and refreshed WAR's qna page, it loaded the contents into this template and I was able to see the "testing" content I created using the local admin CMS.

[OHaiDanny]

[nonowazu]

Yes, layout: $item is how we can select alternative guide layouts (other than just single.html) ; we also use another layout for the bis items.

My operating theory is (if you look here) is that we used to have an old way of writing markdown files, and the "new" way (seen here) isn't being respected.

My theory for reproduction is:

1. Use "old" way to write some faq entries
2. edit using "new" way
3. breakage

[OHaiDanny]

Hmmmm I see... Ok let me take another look but this time i'll use the balance-static repo to take a look. I was testing all this in the glam repo earlier.

[OHaiDanny]

Interesting... In the line - {label: "Layout", name: "layout", widget: "hidden", default: "qna"} the default is not working. I'm looking in Google to see what's going on and it looks like other people have reported this issue as well...

[OHaiDanny]

it looks like default only works on folder structures. Online example below:

[nonowazu]

Oh boy, that considerably changes things. I'm curious how we made it work with the exampleSite content, to be honest.

[OHaiDanny]

This is my first time working with Netlify CMS haha, I'm pretty much learning as I go. but in examplePage under the SCH faq.md in the glam repo you do see there is layout: qna. I believe that existed there before I joined in the project.

[OHaiDanny]

I'm wondering about what quick solution can we propose to do.... Here is an idea:

1. We turn all these layout widget:hidden fields into widget:string and remove the default. Then, we manually add the layout into all existing content pages that need it.
2. Because we set the layout into a field visible for the content creators that are using the CMS, we communicate to the content creators to add the identifier value qna, bis, changes when they create any of these new pages.

What do you think? Thoughts? Let me also ping Roxas and Scrubby to provide additional thoughts too.

[lailleo]

What precisely would 2 require from our side? Cause I've got to admit that I've not got the slightest idea how we'd do that and I doubt the others do either.

[OHaiDanny]

The idea for point number 2 is this shown in this example screenshot. There will be a layout field in the CMS and the content creators will just have to populate this layout field. We will give you the text to add in there depending on if you are creating a qna page, or a best in slot page, or changes page, etc.

[OHaiDanny]

Let me look at netlify-cms github in the time being...... it seems like there are conversations about this issue.

[OHaiDanny]

decaporg/decap-cms#2294 - ugh, doesn't sound too promising

[lailleo]

The idea for point number 2 is this shown in this example screenshot. There will be a layout field in the CMS and the content creators will just have to populate this layout field. We will give you the text to add in there depending on if you are creating a qna page, or a best in slot page, or changes page, etc.

Would it be possible to make that a default value and that field to only populate on the FAQ template? If so, I'm sure we can manage.

[OHaiDanny]

Would it be possible to make that a default value and that field to only populate on the FAQ template? If so, I'm sure we can manage.

The issue is setting that default value. That feature is somehow not working :(