Incredimail 2013 Annual Report Download - page 234

Download and view the complete annual report

Please find page 234 of the 2013 Incredimail annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 259

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259

Tools
There are two ways to get assets to incorporate the brand into your sites.
The Brand Asset Interface
The assets described in this document are available from the Brand distribution interfaces that were created to define brand locations. The intent
of these interfaces is to make it easy for partners to be able to implement the brand. It was designed as an interface to support the rebrand change
automatically and post rebrand all the partners should use this as text file and hardcode the path instead of dynamically reading it from the file.
Hosting the Assets on Your Site
If you wish to host the assets on your site yourself, the approved images can be obtained from your Microsoft contact who can access them from
either Microsoft Brand Tools or Microsoft Mediabank.
Using the Asset Interface
Each element in the asset file contains pointers to published brand assets. To use the asset, simply target your UX to use the element provided in
the XML or JSON file. For example, if your UX requires a 40x16 image with white lettering, you would use the value of the element:
< LogoBigWhite >
http://www.bing.com/siteowner/s/siteowner/Logo_63x23_White.png
< Width > 63 </Width >
<Height >23 </Height>
</LogoBigWhite>
You should not hardcode the path itself, but rather use the value of the element as the value will change when the asset is updated at Bing launch.
By doing this you can work with the asset files before launch, and the assets will automatically change when the new files are published at Bing
launch.
We recommend that you poll our XML file and then cache/host assets locally. This will ensure optimal performance for your sites; while
enabling you to use the XML file to update your sites.
The location to the assets will be contained in XML and JSON static files on the API server that will contain the branding logos and
URLs .
The static files will be named BrandAssets.xml and BrandAssets.js and will be available on api.bing.com.
http://api.bing.com/Brandassets.xml
http://api.bing.com/Brandassets.is
Logo
Spyglass
Favicon