A-BC

Architectural Brand Code
‍‍
v2.5

Semantics

Semantics is about the relation of words to thoughts, but it is also about the relation of words to other human concerns.
Semantics is about the relation of words to reality - the way that speakers commit themselves to a shared understanding of the truth, and the way their thoughts are anchored to things and situations in the world.

Steven Pinker

2. Semantics




2.1 Tag-line + Slogans

Aside from the Graphics Identity, a tag-line communicates the purpose, the spirit, and the attitude of a brand. For Nike, we have 'Just do it.'; For Apple, 'Think Different'; for Mc Donald's 'I'm lovin' it'...

A tagline is about the business itself, and should stand the test of time (it doesn’t change). Taglines represent the tone and feeling you want for your products and services. It is often part of your company graphics and it stays with you all the time.

Slogans are intended to be less long lasting and more flexible. They're often used in advertising campaigns. (they change over time). Slogans are often used only for one product, or one campaign.

Tagline

SLEEEP Takes Us Further

Slogans

For the practicals

SLEEEP : A Space for Recharge (whenever you need it.)

For the public

SLEEEP : Everyone Needs It. Everyday. Everywhere.

For the dreamers

If you do not SLEEEP, you cannot dream.




2.2 TIME

Starting with dates. One of the common confusion is the order of Year (YYYY), Months (MM) and Day (DD), especially between British centric systems versus US centric systems. At SLEEEP, we take the logic of decreasing scale, i.e. YYYY > MM > DD as the order. The separator we use would be " . " (period). In contexts such as file naming or URLs where " . " is not appropriate, the separator could be omitted.

Do

Don't

YYYY.MM.DD
2019.01.03
20190103
DD.MM.YYYY / MM.DD.YYYY
03.01.2019
03012019
Confusion!

For day of weeks, due to the frequency of its use in graphical layouts, abbreviations are often employed. As over-abbreviation will cause confusion, The minimum abbreviation allowed at SLEEEP is the '1.5 Letter abbreviation.' See below:

Do

Don't

Tuesday / Thursday / Saturday / Sunday
T / Th / S / Su
1.5 Letter
TUE / THU / SAT / SUN
3 Letter
Tuesday / Thursday / Saturday / Sunday
T / T / S / S
Confusion!




2.3 Locations

For locations, we focus on using cities, instead of countries to reflect our belief in a world without borders. For cities, we use a ISO 3-letter abbreviation standard (IATA code.)

The general rule for naming is [BRAND].[3-letter city code].[street / district name]. The capitalization follows that
the brand SLEEEP is in all-caps, the rest are all in lowercase.

In terms of deciding whether to use the street / district name, it depends on how well-known the street is. For example, Gough st. is used instead of Sheung Wan as Gough st. is a well known destination to our target audience. On the other hand, CWB and Silom are used for the other two branches.

Do

Don't

[BRAND].[3-letter city code].[street / district name]
SLEEEP.hkg.cwb
SLEEEP.bkk.silom
[Brand].[street no.].[city]
Sleeep.242.hk

2.3.1 Location list

By opening date

SLEEEP.hkg.gough
SLEEEP.bsl.ppp1
SLEEEP.hkg.shrine
SLEEEP.hkg.cwb
SLEEEP.bkk.silom




2.4 Web/Networks

2.4.1 URL

"www" stands for World Wide Web, and while it used to have specific meanings when the internet was still spreading from local networks to a global network, today, the internet being global is a fact taken for granted. Thus, for most websites, there's no longer a difference whether or not one prefixes the URL with "www." In the spirit of our universal values and minimalism, we shall omit "www."in the presentation of our company URLs.

On the other hand, while in some market, the '.io' extension is still not well recognized. In order to help readers easily recognize our URL as a website, we will prefix it with the necessary protocal "https://". The "s" is an important element as it stands for security, an aspect that SLEEEP Tech. must honor strongly.

Do

Don't

https://sleeep.io
www.sleeep.io

IMPORTANT: it is prohibited to use any URL beyond our primary one under any circumstances. This is a fundamental expression of unity that SLEEEP believes in. We strive for a world without borders and would not dissect our core URL into different regions.

Locale specific websites will be created as needed.

Do

Don't

sleeep.io/hkg
sleeep.io/bkk
sleeep.hk
sleeep.th

2.4.2 Wifi naming + password

Wifi naming and password is actually a valuable opportunity to communicate with guests as each guest is likely to conscious search for the network name and memorize the password in order to gain access to the world wide web. It is an opportunity for branding.

Our wifi naming + password convention is as follow (note the 'pipe' in between):
[Location Name] | [User type]

Do

Don't

[Location Name] | [User type] / standard guest password
SLEEEP.hkg.cwb | Guest
p/w: sleeepwell
SLEEEP.bkk.silom | Officer
p/w: [changes periodically]
[Anything else]
Guest network
Confusion!

2.4.3 URL Generation (Online-2-Offline (QR Code), SHORTENING)

A clear and organized collection of  URL & QR code will not only help our internal marketing traffic tracking, but to quickly give an idea to the person scanning the QR code of what content is being presented through the naming of the URL.

We will use Rebrandly as our custom URL shortener and tracker, and will use o2o.exp.is as the domain.

Do

Don't

o2o.exp.is
o2o.spaceis.ltd

For Social Media Posts/SEM

Do

Don't

o2o.exp.is/[creation-date(YYYYMM)]-[medium]-[location/region]-[marketing-campaign/event-name]
e.g.
o2o.exp.is/20191125-facebook-group-sleeep-hkg-gough-christmas-overnight-promotion
[Random name that has no way to tell where it is used.]
o2o.exp.is/721a2
o2o.exp.is/fbpost1

For Print Marketing/Product Materials

Do

Don't

For Print Materials
goto.sleeep.io/[creation-date]-[print-type]-[location/region]-[marketing-campaign-name]
goto.sleeep.io/20191125-flier-hkg-gough-christmas-overnight-promotion
NOTE: no need to add SLEEEP in front of locations,use "-" in place of "." for location names
For Products Info
goto.sleeep.io/[product-name]-[product-version]-[print-type]
goto.sleeep.io/slper-v2-3-manual
NOTE: cannot use dots for URL, use hyphens for all separations
[Random name that has no way to tell where it is used.]
goto.sleeep.io/721a2
goto.sleeep.io/2019promoflier

For Space / Signage

Do

Don't

For Location Info
goto.sleeep.io/[location-name]-[QR-code-placement-location]
goto.sleeep.io/hkg-gough-front-door
For Signage
goto.sleeep.io/[creation-date]-[location-name]-[signage-placed-location]-[signage-purpose]
goto.sleeep.io/20191128-hkg-gough-slper-1-aixo
goto.sleeep.io/20191128-shrine-laundry-machine-1-scheduling
NOTE: no need to add SLEEEP in front of locations,use "-" in place of "." for location names
[Random name that has no way to tell where it is used.]
goto.sleeep.io/SLEEEPgoughfrontdoor

2.5 Brand Naming

Culture-Specific words

Brand naming must go through SLEEEP Global. In adapting to local circumstances, SLEEEP Global team shall work with the local partners to come up with the best name version for that local language and culture.

English

SLEEEP

Chinese

Thai

眠舎

นอออน

SLEEEP Shrine

Dreeem Lab

眠社

研夢社

2.6 Product Naming

Ordinary Words w/ a Twist

Product Naming Rights are granted by seniority within SLEEEP, and may be given as a privilege to individuals who have earned such rights through exceptional performance.

Product list

By launch date

SLPer
E.X.P.
ROOOM
R.E.M.
chAIR

2.6.1 Versioning

The concept of versioning is common in products and softwares. At SLEEEP, we take an iterative approach to every design and engineering project we do, from space to hardware, service flow to systems. Hence, versioning is an important practice to keep track of all improvements, production characteristics and, most importantly, compatibility issues.

We may have used versioning in a relatively loose manner, roughly following the industry practice of 0 meaning pre-release, with Major and Minor releases. The inconsistency shall be rectified from this point on.

Moving forward, we will use versioning following the rules outlined in by the
Semantic Versioning guidelines.

In summary, given a version number MAJOR.MINOR.PATCH (x.y.z), increment the
x. MAJOR version only when you make incompatible API changes,
y. MINOR version when you add functionality in a backwards compatible manner, and
z. PATCH version when you make backwards compatible bug fixes.

Next:

3. Applications