[wp-trac] [WordPress Trac] #34887: Standardize on front end (n.) and front-end (adj.)

[WordPress Trac]

#34887: Standardize on front end (n.) and front-end (adj.)
--------------------------------------+------------------------------
 Reporter:  ocean90                   |       Owner:
     Type:  defect (bug)              |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Text Changes              |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  good-first-bug has-patch  |     Focuses:
--------------------------------------+------------------------------

Comment (by obrienlabs):

 @ocean90 I'll agree that `front end` may not be good for all cases in
 future. However, best I can tell it's correct right now. Nothing in the
 patch references putting something in front of something else (which would
 be `front-end/frontend`), rather everything is relating to the part of the
 software closest to the user (`front end`).

 By this same principle, I think the same can be said for `back end`.
 Everything I found in code did not put anything behind something else
 (`back-end/backend`). It looked like everything was referenced as being
 the part of software to the administrator (`back end`).

 However, I'm not an English major and am open to feedback.

 Perhaps we could create our own version of
 https://gcc.gnu.org/codingconventions.html#Spelling and have it tailored
 for WordPress and have it added to the
 [https://make.wordpress.org/core/handbook/ Make Wordpress Core Handbook]?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34887#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform