How to work in SD with a multi-page...
Juan Elias
Registered User
115 posts
For a website of 5-10 pages, you can simply copy the main page and change it, edit it by making a second, third, etc. But when there are, say, 50 pages, then you are already faced with moments when some pages have in common only a menu and a footer, everything else has a different design and structure, including a css grid. What do you recommend in this case? As far as I understand, I have a typical newbie problem. Which way should you go? Is it possible to make a couple of templates and use them to create pages that stand out from the overall design and structure of the site? In a word, I lack experience working with SD. Can anyone recommend any options?
Reba
Guest
1 post
For a multi page site, start by creating a design system with consistent colors, fonts and reusable components. Use 2 3 flexible templates for different types of pages (e.g., blog, product, landing). Frameworks like Bootstrap or Tailwind can help manage layouts efficiently.
Frank Cook
Registered User
1,567 posts
I would probably do it as follows.
1. I would create a page which contained just the menu and the footer (but see also item 3 below), and set each of those two items as a Symbol. That would mean that, when the page was duplicated, the menu and the footer could still be edited on one of the pages, and that editing would be automatically applied to all the pages.
2. Sometimes one may want an item (e.g. a container including a Heading 2, a paragraph and a picture all laid out in a particular way) which is to appear on a number of pages, but which is to be edited on each page differently (e.g. different words in the Heading and paragraph, and a different picture). For that I would create such a container and set it as a Component. It can then be added to, and edited in, whatever pages one wants.
3. It is my practice to have for each page a whole-page container with the min-height set to 100vh. Into that container I put all the contents of the page. Sometimes one may wish to use a particular page in another project file, and that becomes easy with having such a whole-page container. One can simply make the whole-page container into a Component and save it in the Component library, and the Component will, of course, then be available in other projects.
4. One can, of course, use the technique of item 3 above to make component whole-page containers for "pages that stand out from the overall design and structure of the site". I have avoided the use of the word 'Template', as that is used in SD in relation to project files rather than in relation to pages for insertion into a project.
Others will probably have better ideas, and I hope that they will add them to this forum thread.
Frank
1. I would create a page which contained just the menu and the footer (but see also item 3 below), and set each of those two items as a Symbol. That would mean that, when the page was duplicated, the menu and the footer could still be edited on one of the pages, and that editing would be automatically applied to all the pages.
2. Sometimes one may want an item (e.g. a container including a Heading 2, a paragraph and a picture all laid out in a particular way) which is to appear on a number of pages, but which is to be edited on each page differently (e.g. different words in the Heading and paragraph, and a different picture). For that I would create such a container and set it as a Component. It can then be added to, and edited in, whatever pages one wants.
3. It is my practice to have for each page a whole-page container with the min-height set to 100vh. Into that container I put all the contents of the page. Sometimes one may wish to use a particular page in another project file, and that becomes easy with having such a whole-page container. One can simply make the whole-page container into a Component and save it in the Component library, and the Component will, of course, then be available in other projects.
4. One can, of course, use the technique of item 3 above to make component whole-page containers for "pages that stand out from the overall design and structure of the site". I have avoided the use of the word 'Template', as that is used in SD in relation to project files rather than in relation to pages for insertion into a project.
Others will probably have better ideas, and I hope that they will add them to this forum thread.
Frank
Juan Elias
Registered User
115 posts
Frank Cook wrote:
I would probably do it as follows.
1. I would create a page which contained just the menu and the footer (but see also item 3 below), and set each of those two items as a Symbol. That would mean that, when the page was duplicated, the menu and the footer could still be edited on one of the pages, and that editing would be automatically applied to all the pages.
2. Sometimes one may want an item (e.g. a container including a Heading 2, a paragraph and a picture all laid out in a particular way) which is to appear on a number of pages, but which is to be edited on each page differently (e.g. different words in the Heading and paragraph, and a different picture). For that I would create such a container and set it as a Component. It can then be added to, and edited in, whatever pages one wants.
3. It is my practice to have for each page a whole-page container with the min-height set to 100vh. Into that container I put all the contents of the page. Sometimes one may wish to use a particular page in another project file, and that becomes easy with having such a whole-page container. One can simply make the whole-page container into a Component and save it in the Component library, and the Component will, of course, then be available in other projects.
4. One can, of course, use the technique of item 3 above to make component whole-page containers for "pages that stand out from the overall design and structure of the site". I have avoided the use of the word 'Template', as that is used in SD in relation to project files rather than in relation to pages for insertion into a project.
Others will probably have better ideas, and I hope that they will add them to this forum thread.
Frank
I would probably do it as follows.
1. I would create a page which contained just the menu and the footer (but see also item 3 below), and set each of those two items as a Symbol. That would mean that, when the page was duplicated, the menu and the footer could still be edited on one of the pages, and that editing would be automatically applied to all the pages.
2. Sometimes one may want an item (e.g. a container including a Heading 2, a paragraph and a picture all laid out in a particular way) which is to appear on a number of pages, but which is to be edited on each page differently (e.g. different words in the Heading and paragraph, and a different picture). For that I would create such a container and set it as a Component. It can then be added to, and edited in, whatever pages one wants.
3. It is my practice to have for each page a whole-page container with the min-height set to 100vh. Into that container I put all the contents of the page. Sometimes one may wish to use a particular page in another project file, and that becomes easy with having such a whole-page container. One can simply make the whole-page container into a Component and save it in the Component library, and the Component will, of course, then be available in other projects.
4. One can, of course, use the technique of item 3 above to make component whole-page containers for "pages that stand out from the overall design and structure of the site". I have avoided the use of the word 'Template', as that is used in SD in relation to project files rather than in relation to pages for insertion into a project.
Others will probably have better ideas, and I hope that they will add them to this forum thread.
Frank
Hello Frank! I understand you and you are right, we need not a template, but a component. Your point 2 is an absolutely brilliant idea! This is exactly what I will do. Due to rigidity of thinking, I am used to perceiving the word template as a template
And you are absolutely right in the SD meaning of the word template is largely fulfilled by the component. Thanks Frank! I'll use your instructions as a guide
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.
