Answers.Body: <p><a href="https://meta.stackexchange.com/questions/263661/does-stack-exchange-allow-for-answers-which-question-the-validity-or-stance-of-t">Frame Challenge</a> – The question implies that you're allowing admin changes in production and/or are giving your editors / non-technical-collaborators admin privileges to create new sections, which is a recipe for disaster.</p>
  <p>Creating new sections should be done by a developer in a development environment. This includes adjusting the section settings, defining the field layout, writing / assigning the template to use, testing the changes and finally commiting the updated <a href="https://craftcms.com/docs/3.x/project-config.html" rel="nofollow noreferrer">project config</a> to version control. From there it can be propagated to the production environment.</p>
  <p>If you are <a href="https://craftcms.com/docs/3.x/config/config-settings.html#allowadminchanges" rel="nofollow noreferrer">allowing admin changes</a> and creating new singles (or any other section) in production, you lose the ability to test and commit changes using a proper development workflow, because applying the project config from your development environment would override any changes made in production.</p>
  <p>If you find that your editors often need to create singles with identical fields, you're probably misuing singles. Singles are meant for pages that you really only need one of – like an index page for a news feed/blog, a site-wide search or the homepage. If you need a bunch of &quot;single&quot; pages with similar fields, you should instead use a <a href="https://craftcms.com/docs/3.x/entries.html#section-types" rel="nofollow noreferrer">channel or structure</a>. If you create a structure with a set of fields, your editors will be able to create new pages for that structure in production without having to touch the configuration and without any room for errors regarding the field layout.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-10-14T13:10:16.967Z
Answers.Text: Thank you so much for the thoughtful feedback. This was key and brought the point home:  _If you find that your editors often need to create singles with identical fields, you're probably misuing singles. Singles are meant for pages that you really only need one of – like an index page for a news feed/blog, a site-wide search or the homepage. If you need a bunch of "single" pages with similar fields, you should instead use a channel or structure._ It makes perfect sense. Need to calibrate the approach.
Answers.UserDisplayName: mauricio
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-10-14T12:54:29.627Z
Answers.LastActivityDate: 2021-10-14T12:54:29.627Z
Answers.UserDisplayName: MoritzLost
Body: <p>Not sure if I'm asking this question well, but I'll try... is there a way to have a field appear by default in all my single page?</p>
  <p>Currently whenever I create a new single page I have to manually add a required matrix field (I got to settings &gt; Sections &gt; Edit entry type &gt; etc.) I have no problem doing that, but I worry that less technical users will find this frustrating, make errors, and just give up.</p>
  <p>Thank you so much  for any pointers!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-10-14T07:39:43.240Z
Comments.Text: What is the workflow / scenario here? Why are your 'less technical users' able to create _new sections_ at all? This implies you are [allowing admin changes in production](https://craftcms.com/docs/3.x/config/config-settings.html#allowadminchanges), which is … troubling :) That said, you could probably hook into the section creation to add a couple of fields automatically, but it would be pretty involved and fragile for a very small quality of life improvement.
Comments.UserDisplayName: MoritzLost
Tags: <field><singles>
Title: Default field on any single pages
ThreadText: # Default field on any single pages
  
  (Asked by: username_0 on 2021-10-13)
  
  Not sure if I'm asking this question well, but I'll try... is there a way to have a field appear by default in all my single page?
  
  Currently whenever I create a new single page I have to manually add a required matrix field (I got to settings > Sections > Edit entry type > etc.) I have no problem doing that, but I worry that less technical users will find this frustrating, make errors, and just give up.
  
  Thank you so much for any pointers!
  
  **Tags:** field, singles
  
  > **Comments:**
  > **username_1**: What is the workflow / scenario here? Why are your 'less technical users' able to create _new sections_ at all? This implies you are [allowing admin changes in production](https://craftcms.com/docs/3.x/config/config-settings.html#allowadminchanges), which is … troubling :) That said, you could probably hook into the section creation to add a couple of fields automatically, but it would be pretty involved and fragile for a very small quality of life improvement.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-10-14. Score: 1 | Accepted answer
  
  [Frame Challenge](https://meta.stackexchange.com/questions/263661/does-stack-exchange-allow-for-answers-which-question-the-validity-or-stance-of-t) – The question implies that you're allowing admin changes in production and/or are giving your editors / non-technical-collaborators admin privileges to create new sections, which is a recipe for disaster.
  
  Creating new sections should be done by a developer in a development environment. This includes adjusting the section settings, defining the field layout, writing / assigning the template to use, testing the changes and finally commiting the updated [project config](https://craftcms.com/docs/3.x/project-config.html) to version control. From there it can be propagated to the production environment.
  
  If you are [allowing admin changes](https://craftcms.com/docs/3.x/config/config-settings.html#allowadminchanges) and creating new singles (or any other section) in production, you lose the ability to test and commit changes using a proper development workflow, because applying the project config from your development environment would override any changes made in production.
  
  If you find that your editors often need to create singles with identical fields, you're probably misuing singles. Singles are meant for pages that you really only need one of – like an index page for a news feed/blog, a site-wide search or the homepage. If you need a bunch of "single" pages with similar fields, you should instead use a [channel or structure](https://craftcms.com/docs/3.x/entries.html#section-types). If you create a structure with a set of fields, your editors will be able to create new pages for that structure in production without having to touch the configuration and without any room for errors regarding the field layout.
  
  > **Comments:**
  > **username_0**: Thank you so much for the thoughtful feedback. This was key and brought the point home:  _If you find that your editors often need to create singles with identical fields, you're probably misuing singles. Singles are meant for pages that you really only need one of – like an index page for a news feed/blog, a site-wide search or the homepage. If you need a bunch of "single" pages with similar fields, you should instead use a channel or structure._ It makes perfect sense. Need to calibrate the approach.  
  
  ---
  
  