Properly use a page as a panel tab

The CMS Questions
1

Hi,
I’m building a website that uses tabs in the back-office.
For now my site.yml looks like that:

title: Site

tabs:
  table: pages/table
  projects: pages/projects
  about: pages/about
  seo: seo/site

in the about page I would like the user to be able to fill some text fields, so once again, so far my pages/about.yml looks like that:

label: About
icon: question

sections:
  introduction:
    type: fields
    fields:
      address:
        type: text
        width: 1/4
        label: Studio address

But as soon as I fill these fields, they are directly linked to the site.txt which is not what I would like, plus, when I navigate the panel and end end being on
panel/pages/about and not panel/site?tab=about the content is blank (because located in site.txt

What would be the best way to avoid this?
Thanks.

2

Fields in a blueprint always are tied to the content of the current page (or also site, as in this example).

What

tabs:
  table: pages/table

only does is to extend your table tab with the whole content of the pages/table.yml blueprint file. However, it still behaves as if those fields section etc. were directly defined in your site.yml - which if why all fields on the site blueprint view in the Panel will read and write to the site.txt. Only because you extend your tab in the site blueprint from another blueprint, doesn’t mean that it would take the context of another page.

Instead of tabs, add a pages section to your site blueprint, so you can navigate to the subpages to fill in the fields there. Then it will actually eb stored to the respective page as you want.

3

That I understand and know. I’m not using a page section because it would add one click for my user to get inside the only page instead of being able to edit it directly from the tabs section.
I’m probably going to use the sidebar.