# Server-side development reduces JavaScript complexity A server-rendered content component can avoid a custom JavaScript editing application when the editor only needs controlled content slots inside a fixed structure. ## Scope & conditions - This applies to WordPress components whose structure is stable and whose editing needs fit existing blocks. - It does not apply when users need freeform structural editing or client-side interaction. - Server rendering reduces front-end and build complexity; it does not remove the need for semantic markup, sanitization, or editor-state testing. <!-- atomicity: 1 idea ✓ --> ## Links - [[3. Resources/Permanent Notes/Editable Slots Separate Content Rights From Structural Rights]] — applies-in: locked inner blocks provide a concrete way to keep a server-defined shell while exposing selected content. - [[3. Resources/Permanent Notes/The CMS Decision Turns on How a Site Is Edited Not What It Contains]] — extends: implementation choices should follow the editing workflow rather than the content category. - [[DevRel MOC]] — belongs-in: developers need clear guidance on when a server-rendered composition is enough and when a custom block is warranted. ## Source - [This Week in WordPress #367](<../Readwise/Articles/This Week in WordPress %23367.md>)