Are individual yml files needed for each component param option?












1















As an example, I'll use a generic content Block component. This component, among other params, would have a columnSpan param. As far as I can tell, the only way to predefine options for that param is to create individual content entries like so:



enter image description here



...and use that directory as the source of the params like so:



{
...
source: 'dataSource=sitecore/content/BlockColumnSpanOptions'
...
}


So, multiply that by X number of components and X number of params, this content directory is quickly going to become nightmarish.



Is there a better/other way to provide param options in a more flattened/simplified manner?



Thanks in advance for any help provided.










share|improve this question







New contributor




Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    1















    As an example, I'll use a generic content Block component. This component, among other params, would have a columnSpan param. As far as I can tell, the only way to predefine options for that param is to create individual content entries like so:



    enter image description here



    ...and use that directory as the source of the params like so:



    {
    ...
    source: 'dataSource=sitecore/content/BlockColumnSpanOptions'
    ...
    }


    So, multiply that by X number of components and X number of params, this content directory is quickly going to become nightmarish.



    Is there a better/other way to provide param options in a more flattened/simplified manner?



    Thanks in advance for any help provided.










    share|improve this question







    New contributor




    Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      1












      1








      1








      As an example, I'll use a generic content Block component. This component, among other params, would have a columnSpan param. As far as I can tell, the only way to predefine options for that param is to create individual content entries like so:



      enter image description here



      ...and use that directory as the source of the params like so:



      {
      ...
      source: 'dataSource=sitecore/content/BlockColumnSpanOptions'
      ...
      }


      So, multiply that by X number of components and X number of params, this content directory is quickly going to become nightmarish.



      Is there a better/other way to provide param options in a more flattened/simplified manner?



      Thanks in advance for any help provided.










      share|improve this question







      New contributor




      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      As an example, I'll use a generic content Block component. This component, among other params, would have a columnSpan param. As far as I can tell, the only way to predefine options for that param is to create individual content entries like so:



      enter image description here



      ...and use that directory as the source of the params like so:



      {
      ...
      source: 'dataSource=sitecore/content/BlockColumnSpanOptions'
      ...
      }


      So, multiply that by X number of components and X number of params, this content directory is quickly going to become nightmarish.



      Is there a better/other way to provide param options in a more flattened/simplified manner?



      Thanks in advance for any help provided.







      jss datasource components






      share|improve this question







      New contributor




      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 11 hours ago









      JbirdJbird

      1082




      1082




      New contributor




      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Jbird is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          3














          The manifest API is a JavaScript API; we just provide a default input via YAML. You can modify the handling in /sitecore/definitions/*.sitecore.js to source content from whatever you like, including multiple items in one JS file.



          Example here, note that the manifest contains TypeScript typings to make constructing objects easier.






          share|improve this answer
























          • Very helpful. Thank you, @KamFigy

            – Jbird
            10 hours ago











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "664"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Jbird is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f17420%2fare-individual-yml-files-needed-for-each-component-param-option%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          The manifest API is a JavaScript API; we just provide a default input via YAML. You can modify the handling in /sitecore/definitions/*.sitecore.js to source content from whatever you like, including multiple items in one JS file.



          Example here, note that the manifest contains TypeScript typings to make constructing objects easier.






          share|improve this answer
























          • Very helpful. Thank you, @KamFigy

            – Jbird
            10 hours ago
















          3














          The manifest API is a JavaScript API; we just provide a default input via YAML. You can modify the handling in /sitecore/definitions/*.sitecore.js to source content from whatever you like, including multiple items in one JS file.



          Example here, note that the manifest contains TypeScript typings to make constructing objects easier.






          share|improve this answer
























          • Very helpful. Thank you, @KamFigy

            – Jbird
            10 hours ago














          3












          3








          3







          The manifest API is a JavaScript API; we just provide a default input via YAML. You can modify the handling in /sitecore/definitions/*.sitecore.js to source content from whatever you like, including multiple items in one JS file.



          Example here, note that the manifest contains TypeScript typings to make constructing objects easier.






          share|improve this answer













          The manifest API is a JavaScript API; we just provide a default input via YAML. You can modify the handling in /sitecore/definitions/*.sitecore.js to source content from whatever you like, including multiple items in one JS file.



          Example here, note that the manifest contains TypeScript typings to make constructing objects easier.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 11 hours ago









          Kam FigyKam Figy

          3,403621




          3,403621













          • Very helpful. Thank you, @KamFigy

            – Jbird
            10 hours ago



















          • Very helpful. Thank you, @KamFigy

            – Jbird
            10 hours ago

















          Very helpful. Thank you, @KamFigy

          – Jbird
          10 hours ago





          Very helpful. Thank you, @KamFigy

          – Jbird
          10 hours ago










          Jbird is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Jbird is a new contributor. Be nice, and check out our Code of Conduct.













          Jbird is a new contributor. Be nice, and check out our Code of Conduct.












          Jbird is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Sitecore Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f17420%2fare-individual-yml-files-needed-for-each-component-param-option%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          GameSpot

          日野市

          Tu-95轟炸機