Figma lets you nest components within components. This means you can structure them in all sorts of modular ways. Here are a few different ways t use nested components.
Often I will create a “building block” component, and use that as the basis for another component. For example, in these buttons, I have created a basic rounded rectangle for the button shape and turned it into a component. This component does not get published to my team library, instances of it just get used in other components that I build, like the actual button components (which do get published).
The advantage to this method, is that all of my buttons and button states make use of this base component (with style overrides applied) which maintains a link back to that base “building block” component. Should I need to make a globalized change, such as changing the button shape, I can simply go back and edit the original component and the change affects all of the components which are based off of it.
Each button nests the building block component within it, and applies style overrides to the base component to create the different states.
Another advantage to nesting components is that you can swap/replace them out for other components. For example in the tile header below, I just have to build one component for the tile header, and simply swap out the nested component for a different one. If you are familiar with Sketch, you are probably already familiar with this concept, however, the interaction In Figma to swap out components is different (drag & drop).
Shortcuts: To swap out a component — Hold option when dragging. Top swap out a nested component (within another component, frame or group) — Hold ⌘ + option when dragging.
Create a component, and configure the constraints within it—while holding ⌘, drag the frame of your component to crop the contents, or adjust the dimensions in the properties panel. The contents of your component may shift if you haven’t setup the constraints, so make sure you do that first. This is great for creating a “repeat grid” of rows/columns, or setting up tabular data. You can create more rows than you need, and use this method to show only the number of items that you want. Couple this technique with constraints, and you can even setup components which will hide or reveal content as their parent component expands and contracts. Make sure “Clip Content” is checked in your properties panel to see the cropped result.
Once you start setting up these grids, the possibilities are endless. Overriding text, symbols, and adding images are a breeze!
Redesign is a correction of mistakes and its distinctive features are:
This question cannot be answered without a complete analysis of the current site structure. We can conclude which of the options will be cheaper and easier to imply only after the analysis.
This question is more related to SEO optimization. In order not to lower the current place of your site on a search engine query, you should ask a SEO specialist about the correct way to use the tag cloud.
In order not to make the structure too complicated for perception in a situation when the amount of content is regularly updated, one should correctly catalog the content (upper level of the site structure). If you work out the principles of content organization correctly, you will not have any difficulties in adding new content and distributing the already existing one without messing up the structure with similar elements.