Developer forum

Forum » CMS - Standard features » Is using RenderParagraphContent bad practise?

Is using RenderParagraphContent bad practise?

Hans Ravnsfjall
Hans Ravnsfjall
Reply

We often use @RenderParagraphContent([paragraphid]) for global elements that we want to be editable, such as footers etc. Reason being that we don´t want to send the editor to the website settings to edit.

 

But does using RenderParagraphContent effect performance in a negative way? Is there any other/better way of handling global content, if we don´t want to give editor access to website settings?

/Hans


Replies

 
Nicolai Pedersen
Reply
This post has been marked as an answer

RenderParagraphContent comes with an insignificant performance hit - depending on what you have on that paragraph. Often we see newsletter signups or product lists etc. in the footer and those can have a performance impact.

There are currently no better way - in Swift we use RenderGrid instead - more or less the same thing, just rendering rows instead of only paragraphs.

Votes for this answer: 1
 
Hans Ravnsfjall
Hans Ravnsfjall
Reply

Ok, thank you 👍🏻

 

You must be logged in to post in the forum