There are many things that can help with confusion as a developer and as a content author. One of the biggest confusions I’ve come across has been duplicate item names, fields, and placeholders. Sitecore will render whatever the first instance of that name is. So, if you have an item with the same name as another, it will render the one higher up in the tree. The same idea expands to placeholders and field names as well. There’s a way to work with the placeholders and not be required to create multiple placeholders that have the same function called “Dynamic Placeholders“. However, the other two require some discipline as a developer and a content author.
As a content author, to avoid general confusion, giving unique names to items will avoid a possible situation where content you’ve entered is not showing up properly or not at all. I’ve run into a few situations where the client has asked me to troubleshoot why the content they’ve updated was not displaying like they were expecting. When I started troubleshooting, I noticed that there were items that had the same name. It turned out they were editing the lower of the items which meant the rendered content wasn’t actually updating. In addition, I had also noticed that other renderings were missing content entirely. After looking into this situation, I found out that there were different templates that were utilizing the same name as well. So, the content author added a Rich Text block to the page and correctly pointed the Datasource. However, the item above it was an Accordion template that shared the same name. Since Sitecore uses the path to get to the Datasource as opposed to a GUID, the rendered page was trying to render the Accordion template in the Rich Text rendering, which didn’t render properly. One of the easiest ways to do this is to either put all items that belong together in a folder or name each one differently but name them in a way that a content author will understand that they go together (see green highlighted area).
As a developer, however, one of the things that will avoid general confusion for content authors is to name your template fields well. Naming something “Content” can work if you’re creating a template that’s going to be inherited in to multiple places. However, if you are creating a field specifically for a template type, it’s worth naming your fields more specifically. As you see in the screenshot, there are two fields named “Page Title”. One field is being inherited while the other field was added to the template itself with the same name. This means, the first one will be the field that gets rendered while the second one is about as useless as it can be. To avoid these types of situations, it’s good to plan out your templates before you create them to see what fields are being inherited and what fields you’ll need to create.