Normalize terminology from Display Suite / DisplayPod to Frontier

[sc0ttkclark]

Before we launch 1.0, we'll need to be sure we switch all terminology / logos out for the plugin to really spruce it up and take advantage of the strong 'Frontier' branding. I can get us some outside logo help if you want.

[naomicbush]

Started working on this — realized that using PodsFrontier as a noun to replace DisplayPod was a bit less intuitive than the latter

Example: Create a new PodsFrontier vs. Create a new DisplayPod

So @sc0ttkclark decided on FrontierDisplay and also removing the camelCase to follow WordPress Coding Standards (http://make.wordpress.org/core/handbook/coding-standards/php/#naming-conventions)

[sc0ttkclark]

Any references to DisplayPod in the UI as a singular / plural term, like in your above example, we probably need something better to call it that makes sense to the user. As part of #6 maybe that's "Frontier View".

[DavidCramer]

I like the sound of Frontier View. My thinking was also on the term "view"

-----Original Message----- From: "Scott Kingsley Clark" [email protected] Sent: ‎2013-‎11-‎09 00:26 To: "pods-framework/pods-frontier" [email protected] Cc: "David Cramer" [email protected] Subject: Re: [pods-frontier] Normalize terminology from Display Suite /DisplayPod to Frontier (#9)

Any references to DisplayPod in the UI as a singular / plural term, like in your above example, we probably need something better to call it that makes sense to the user. As part of #6 maybe that's "Frontier View". — Reply to this email directly or view it on GitHub.

[naomicbush]

@Desertsnowman realized this will take you a lot less time than me :-) All yours.

[DavidCramer]

I'm working on UI at the moment so, yes it probably would.

[sc0ttkclark]

@Desertsnowman is this already done? I think it is, but you can clarify. The shortcode / functions should be normalized with "pods_frontier_*" and [pods_frontier ....] or [frontier ....]

[DavidCramer]

current structure is [frontier view="id"]