1 of 9

�Rename `marketplace-kit` and `marketplace_builder`

Research

2 of 9

Rename `marketplace-kit`

3 of 9

25 replies

4 of 9

Comparing results

pos

pos-cli

pos-kit

Refer to the brand

Refer to the brand �

Refer to the brand

Explains what the user is installing

Explains what it is �(cli = command line interface)

Explicitly specifies what it works with.

Intuitive (Other companies named their CLI tools after their main name Heroku, AWS, Hanami.)

Consistent with other tools offering a cli interface. (Other companies named their CLI tools like this Zapier)

Allows for a variety of different-purposed commands

Simple (Easy to remember)

Short (Quick to type)

5 of 9

Rename `marketplace_builder`

6 of 9

28 replies

7 of 9

Comparing results

app

pos-instance

instance

pos-build

Other frameworks using the same structure

Name everything after the brand

Has more meaning when used in the wider context of pOS

Build works as a command (build instance) and as an output (the build directory)

Short (quick to type)

Consistency

That's what the directory represents.

8 of 9

Anything else to rename

9 of 9

Other suggestions

  • Remove any references to near-me�
  • If there are going to be multiple options kits builders these will need to be accounted for.

  • Ban things mentioning "Custom" (Customization, CustomAttribute, UserProfile) as there is no common attribute in the platform. (Better - Document, Query, User.)�
  • What names need to be unique would help us develop faster.

Original

Suggested

form_configurations

forms (3)

custom_model_types

models (2)

user_profile_types

user_profiles

user

partials

content_blocks �containers

layouts

templates

authorization_policies

policies

graph_queries

queries

custom_model_types

models

customizable_id

parent_model_id