<p>If the fields can all use the same description and settings (allow multiple lines, text size), you could use the same field (we do).</p>

<p>If there's even the slightest chance the description need to be different (in the future), create different fields (or use the <a href="https://github.com/Anubarak/craft-relabel" rel="nofollow noreferrer">Relabel plugin</a> to create different names and descriptions for the same field).</p>

CC BY-SA 4.0
2018-12-04T13:07:08.387Z
2018-12-04T13:07:08.387Z
Paul
<p>The job of naming something is sometimes the most difficult part of a project! This is pretty subjective, but even though it seems like those three fields would share the same settings and requirements (as mentioned by @Paul Werheul), if it was me I would choose field names like <code>clubName</code>, <code>teamName</code>, and <code>playerName</code>.</p>

<p>This way the field names explicitly state what is expected to be entered or returned in your template.</p>

<p>My very humble two cents!</p>

CC BY-SA 4.0
2018-12-04T17:17:31.993Z
2018-12-04T17:17:31.993Z
Steven Thate
<p>I have a question about best-practice for naming fields; I am creating a craft site for a football club, which include the following:</p>

<ul>
<li>club name (Global)</li>
<li>team names </li>
<li>player names</li>
</ul>

<p>These are all plaintext fields. In the interest of being DRY, should I create one 'Name' field for all? Is this problematic - and therefore better to create different fields for each, so I have teamName, playerName, clubName handles etc? </p>

<entries><best-practice>
Best practice for naming fields shared across entries in CraftCMS
# Best practice for naming fields shared across entries in CraftCMS

(Asked by: username_0 on 2018-12-04)

I have a question about best-practice for naming fields; I am creating a craft site for a football club, which include the following:

* club name (Global)
* team names
* player names

These are all plaintext fields. In the interest of being DRY, should I create one 'Name' field for all? Is this problematic - and therefore better to create different fields for each, so I have teamName, playerName, clubName handles etc?

**Tags:** entries, best-practice

---

## 2 answers

### Answer by username_1 on 2018-12-04. Score: 2 | Accepted answer

If the fields can all use the same description and settings (allow multiple lines, text size), you could use the same field (we do).

If there's even the slightest chance the description need to be different (in the future), create different fields (or use the [Relabel plugin](https://github.com/Anubarak/craft-relabel) to create different names and descriptions for the same field).


---

### Answer by username_2 on 2018-12-04. Score: 5

The job of naming something is sometimes the most difficult part of a project! This is pretty subjective, but even though it seems like those three fields would share the same settings and requirements (as mentioned by @Paul Werheul), if it was me I would choose field names like `clubName`, `teamName`, and `playerName`.

This way the field names explicitly state what is expected to be entered or returned in your template.

My very humble two cents!


---

