Developer forum

Forum » Swift » A few more possible optimizations for Swift

A few more possible optimizations for Swift

E-mail notifications
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply
Posted on 25/01/2023 18:29:43

Hi guys,

I have spent some time discussing with my colleagues around frequent issues raised during Swift implementations and I have collected a few that could be useful to have into considerations (apart from the ones I have already posted a while ago):

1. Related products lists should reuse Product list components. Very useful if you want to have a consistent look and feel of the product lists wherever they are displayed, without customizing templates

2. Extending the components for other areas where implementation would require adding multiple paragraphs in the same column. The first thing that comes to mind is the header and footer.

3. Ability to limit the templates used for a specific ItemType. This can give more control to the admin user to choose the proper templates for an existing paragraph. I know that new scenarios are not encouraging messing around with template selections but it still can be a good addition

4. Ability to define the default template to be applied to an ItemType. For cases where we want, for example, to have a different default template for a Swift ItemType

 

I hope this helps.

Thank you,

Adrian


Replies

 
Jonathan Pascoe
Posted on 26/01/2023 09:03:50
Reply

I would also like to see these surgestions. No. 2 especially. I have also been trying to figure out how to use the comonents in other ways. It would be great addition to the Swift product:)

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Posted on 26/01/2023 10:19:15
Reply

Hi guys,

 

If you look at v1.17.0's release, a Product Component Slider was added. This can be used to do the Related Products.

 

BR,

Nuno

 
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Posted on 26/01/2023 10:55:05
Reply

Hi Nuno,

I have not tested it yet becuase I have just updated our standard solution to the latest version.

It's good to know that this has been implemented already. One less issue on the list :)

Thank you,

Adrian

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Posted on 26/01/2023 10:57:15
Reply

Hi Adrian

Good points - thank you for sharing.

@4: You can do that already on website settings - changing the default item type template. Swift uses the concept of picking up a template that shares name with the itemtype it self - in below screen you can overrule that by choosing your custom template.

 

Can you ellaborate on @2? I am not sure I understand it.

 
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Posted on 26/01/2023 11:13:50
Reply

Hi Nicolai,

Right. I have not used that feature in a while and completely forgot about it :)

Here are some insights about #2. I have often seen situation where in Footer, for example, I have 4 columns. The first column would contain a logo and an address, the second and third columns will have list of links and the 4th column would have Newsletter subscription and social links.

The 4 columns design can be handled with a standard row, the second and third columsn can be handled with standard Navigation but the first and fourth columns would require mixing multiple columns in the same column. And the components are supposed to be doing just that. In my mind, we can have a footer component that is basically a way to combine multiple rows and columns. Does it make sense? 

Thank you,
Adrian

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Posted on 26/01/2023 11:15:26
Reply

Understood. - thank you for clarifying

 

You must be logged in to post in the forum