Announcing the Winners of the 2016 Creativity in the Public Sector Awards


Adobe
Adobe is thrilled to recognize some of the best creative work done at public sector agencies over the past year. This year’s submissions demonstrated outstanding design-led innovation taking place across federal, state and local agencies to achieve a variety of important missions, reflecting the importance of creativity as a strategic tool for citizen engagement.
This year, submissions were accepted under the following categories:

Best Integrated Cross-Channel Campaign
Best Responsive Web Design
Most Engaging Citizen-Facing Creativity
Honoring the Heroes

And now… Announcing the 2016 Creativity in the Public Sector Award winners!
County of San Diego, “Live Well San Diego” (Best Integrated Cross-Channel Campaign)
See submission here on Bēhance.

The County of San Diego had a vision to improve the health of its 3.3 million residents. The Live Well San Diego campaign was launched, and brought to life online through an innovative digital experience that improved citizen engagement with the county.  The County also campaigned internally across their employee base to effectively communicate how their work at the County contributes to the Live Well San Diego vision.
 
NASA Johnson Space Center, “NASA Science Investigations: Plant Growth” (Most Engaging Citizen-Facing Creativity)
See submission here on Bēhance.

Conveying Space Station Research can be very difficult. Previously, the Johnson Space Center had used web pages with overwhelming text descriptions, videos, images and other means to demonstrate their important work.  Using Photoshop and Illustrator for imagery along with 3-dimensional computer software, the NASA team created an educational game to take the public through an “experience” to show how to plants grow in space.
 
City of Sandy Springs, “City Springs Website” (Best Responsive Web Design)
See submission here on Bēhance.

 
The City of Sandy Springs Design Team was asked to create a website for the city’s downtown development project – City Springs ­– to share up-to-date information about the project, including what people should expect and details around how the project fits within the city’s larger City Center Master Plan. The city saw a substantial increase in citizen engagement in the project and support for the development initiative overall.
 
City of Greenville, SC, “Greenville Heroes Tribute to Officer Allen Jacobs” (Honoring the Heroes)
See submission here on Bēhance.

Greenville police officers and firefighters share a rare, behind-the-scenes glimpse into what their profession entails. This well-produced video was produced as part of the Greenville Heroes: Serve & Protect Awards Luncheon.
We saw so many great projects submitted this year, and it was a challenge to select just one winner in each group.
We wanted to give a special mention to the U.S. Department of State for their “International Education Week” campaign, which was another excellent submission in the Best Integrated Cross-Channel Campaign category. See submission here on Bēhance.
Another special mention goes to web designer Abol Bahadori from Mondo, for a proposed mobile app with section 508 compliance for the U.S Defense Intelligence Agency. See submission here on Bēhance.
Look for the 3rd annual Creativity in the Public Sector Awards program to open at the Adobe MAX Creativity Conference October 16th-20th, 2017 in Las Vegas, NV.

AEM Multi-Site Tips & Tricks Preview – IMMERSE 2017


Adobe
We are excited to share another post in the AEM Rockstar Tips & Tricks Guest Blog series! This Tips & Tricks preview is from Brett Birschbach, an AEM Certified Architect and AEM Rockstar semi-finalist who will be a session presenter at Adobe’s global virtual developer conference, IMMERSE May 15th – 19th 2017. Brett will detail his Tips & Tricks in a follow-up post after IMMERSE. Brett’s session will be on Tuesday, May 16, 1:15-2:15 PM Central (11:15-12:15 PDT).
Brett is the Adobe Marketing Cloud Solutions Architect for HS2 Solutions, a digital transformation company based in Chicago. He is a hands-on problem solver with experience leading large multinational, multi-site platform projects.  Brett led the development of the new Shared Component Properties feature in the open source ACS AEM Commons library. For more from Brett, visit his Github: HitmanInWis.
Multi-site platforms are the norm in a mature Adobe Experience Manager installation. However, most implementations, in true Agile fashion, start as a single site and then expand to support multiple. Suppose your client is the NFL and it wants to put all 32 teams on the same AEM platform. We all know that launching 32 team sites on day one is A Bad Idea, so likely you are going to start with just one site as a proof of concept.  However, Agile tends to tempt a lot of us in this situation into thinking that “I’ll just code for this one site now, and worry about multi-site support and code structures on the second site when I actually need them.”  YAGNI, right?  Except…you ARE going to need it.  Pretending you are building a single site when you know the platform is going to support multiple, thinking only in the present instead of taking a step back and getting the full picture, is a great way to paint yourself into a corner.
 
Image by Ali Moussa, HS2 Solutions
Coding a multi-site platform beginning with single-site patterns, we are faced with technical debt in making the transition to multi-site – technical debt that often never gets fully paid.  Let’s be real, clients want to see sites #2 through #32 launched as quickly as possible after site #1 is launched.  After all, that’s the vision you cast them – that they would easily be able to create and manage all their sites on a single platform using the same components and authoring techniques as the first site.  To the client, having a single working site seems like it should account for 80% of the total work, so the rest of the sites should be a snap.  You know as well as I do that the urgency to turn out these sites means that much of the technical debt accrued early in the project will be worked around and put off until resolution on a proverbial someday, never to be repaid.  Bad decisions made when creating the first site often linger on for as long as the platform lives.
Image by Ali Moussa, HS2 Solutions
But it doesn’t have to be this way.  Structuring your code base for multi-site success isn’t that hard to do, it’s just easier not to do it (which is why we end up in this situation).  But what if you had a step-by-step guide?  What if you could leverage the experience of peers who have already done it well?  This stuff isn’t rocket science, and the principles don’t change much from project to project.  No sense wasting your time trying to come up with all the techniques on your own.  Wouldn’t you rather be doing the fun stuff like banging out a sweet, interactive Schedule component for authors to drop onto those 32 NFL team sites?  Of course, you would!  That’s why I encourage you to attend the “Multi-Sites: Setting your Codebase Up for Success” session at Adobe IMMERSE 2017.
 

Why should you attend?

Adobe IMMERSE is the premier AEM developer conference of the year, focusing on the technical audience.  If you’re not already registered, sign up using the link above!
I’ll be covering Basic, Advanced, and Overachiever techniques, 15 in all, using the NFL example above (modified to HFL, to avoid any grumbling from the lawyers).
The techniques come from a successful, international, multi-site platform implementation hosting a dozen brand and corporate sites, so they are tried and proven.
Every example (yes, every last one) will be demonstrated by real code that you can download, look at, and play with in order to gain a true understanding that only code can give.

Disclaimer: Being a Green Bay native (and therefore huge Packers aficionado) I *may* take the liberty to take a few jabs at our archrivals in Chicago…don’t take it personally 🙂
 
 
 

Copyright Reform Needed for New Era of Creativity

Adobe
Posted by J. Scott Evans, Director, Trademarks, Adobe Legal
Copyrights provide tremendous value to the U.S. economy and culture, contributing more than $1.2 trillion to the U.S. GDP and employing more than 5.5 million Americans in industries that depend on a strong copyright system. The Copyright Office, headed by the Register of the Copyrights, plays a central role in helping creators protect their work, but the nation’s copyright system is not keeping up with changing trends and the Register is not subject to Congressional approval. To keep up with advances in technology and content development, Congress needs to modernize the Copyright Office so that it can continue to administer the nation’s copyright laws, offer services and support to creators and users of creative works, along with providing expert, impartial assistance to Congress, the courts, and executive branch agencies on questions of copyright law and policy.
Currently, the Register is unilaterally selected by the Librarian of Congress. This process requires no direct input from the Administration or Congress. While the Library of Congress (LOC) has a mission of national importance as well, it is different than and sometimes in conflict with the role of the Copyright Office. The Copyright Office administers laws that reward and incentivize creation by giving creators a period of exclusive rights, whereas the goal of the Library of Congress is to make such creations widely available to the public. This creates clear conflicts of interest that can harm the nation’s creators and innovators. The Copyright Office has also faced numerous IT challenges and personnel shortages that the Library has not helped to rectify. Too often, the Copyright Office’s efforts to modernize have been stymied by the competing needs and direction of the LOC.
As more and more industries grow to depend on the Copyright Office, Congress needs impartial copyright advice. Thankfully, Rep. Bob Goodlatte, (R-VA), has introduced H.R. 1695, The Register of Copyrights Selection and Accountability Act of 2017 (RCSAA), which would make the Register of Copyrights a presidential appointee subject to the advice and consent of the Senate.
The Register of Copyrights does far more than just administer the copyright registration system. The Register serves as the top advisor to the president and the Administration on all matters related to copyright policy and helps Congress develop copyright legislation. Much like other presidential appointees that require Senate approval, the Register has significant impact on a number of industries that are critical to the US economy. H.R. 1695 would finally give Congress a formal role in selecting its advisor through the confirmation process, reflecting the growing importance of copyright to our economy and culture.
The bill is an essential step in modernizing an antiquated Copyright Office. Making the Register a presidential appointee subject to Senate confirmation ensures a more neutral and fair selection process compared to the status quo, increases accountability, and gives all Americans a voice in the selection of the Register through their elected representatives. This simple change will also help ensure that the Register of Copyrights has the voice and resources needed to implement policy, manage its operations, and organize its information technology in a way that brings the Copyright Office into the 21st century
Adobe encourages Speaker Ryan and the House leadership to take up the measure for a floor vote as soon as possible. Thanks to the bill’s modest approach, the bill enjoys overwhelming bipartisan support in both the House and the Senate. In fact, the House Judiciary Committee approved the measure by a decisive 27-1 vote earlier this year – something practically unheard of in today’s hyper-partisan environment.
The time to move H.R. 1695 is now. Congress and the nation’s creative industries have been working together for more than four years to craft this bipartisan, bicameral bill that will improve the nation’s copyright system. Presidential appointment and Senate confirmation puts the Copyright Office on a better footing to meet its statutory duties and serve the American people for generations to come.
 
 
 

UX 전문가에게 묻다: 사용자로부터 얻은 교훈


Adobe
디자이너가 사용자에 대해 더 많은 것을 파악하려면 사용성 테스트, 사용자 리서치, 웹 분석 등 몇 가지 툴을 사용할 수 있겠지만, 경우에 따라서는 기대조차 하지 않은 시점에서 사용자가 해답을 제시해 주기도 합니다. 이 해답은 디자이너가 인식하는 사용자의 정체성, 행동 방식의 틀을 빗나가거나 디자이너가 생각하는 개념에 정반대되는 것일 수도 있습니다. 사용자는 인간이고 인간이 항상 예상대로 행동하지만은 않기 때문입니다.
우리는 몇 명의 UX 전문가에게 실제로 사용자를 파악하는 데 그치지 않고 더욱 심도 깊은 이해력을 보유한 디자이너가 되기 위한 조언을 요청했습니다. 다음은 UX 전문가의 답변을 요약한 것입니다.
 
어느 상황에 효과적이라고 해서 다른 상황에도 동일할 것으로 가정하지 마십시오.

UX 디자이너로서 활동해 오면서, 필자의 경우 검증되고, 지속적으로 적용 가능하며, 사용성이 뛰어난 디자인 패턴에 주로 의지했습니다. 이렇게 하면 무엇보다도 양식 필드나 탭을 새로 만드느라 시간을 낭비할 필요가 없어지는데 그 이유는 수년에 걸친 웹에 관한 사용성 리서치 덕분에 무엇이 효과적인지 잘 알고 있기 때문입니다. 그러나 실제로 중요한 것은 상황입니다. 인터넷에서 주류가 된 동일한 구식 패턴을 사용하여 운전자에 차량용 인포테인먼트 디자인을 제공하는 경우 상황은 특히나 중요합니다.
휴대전화의 기능을 능숙하게 찾을 줄 아는 사용자의 경우, 2톤 차량이 탈선하지 않게 운전에 집중할 때와 같은 고도의 집중력으로 동일한 패턴에 반응하지 않습니다. 겉으로 성공적으로 보이는 디자인이 사용성 테스트에서 기대 이하인 것을 보면, 새로운 상황을 디자인할 때 사용자에게 가장 효과적인 패턴이라는 확실한 가정일지라도 테스트할 필요가 있다는 것을 알게 되었습니다.
~ 에밀리 마후드 보우먼(Emily Mahood Bowman), 제너럴 모터스 시니어 UX 디자이너
 
디자이너는 사용자가 아닙니다. 관찰하고 공감하되 사용자를 진정으로 파악하고 있다는 생각은 금물입니다.

고객지원 팀이 브라우저에서 사용자에게 “뒤로 가기” 버튼을 가르쳐주는 것을 알게 된 이후로 고객에 대한 생각을 전면적으로 바꿔야만 했습니다. 사용자들은 뒤로 가기 버튼이 있는 줄도 몰랐던 것입니다. 우리의 주요 사용자가 자신의 도메인과 조직에 상당히 많은 지식이 있다는 사실만으로 그들도 제가 사용하는 방식과 완전히 똑같은 방식으로 컴퓨터를 사용할 것으로 생각했습니다.
사용자의 관점에서 이해하려고 노력한다 해도 저는 미국 오클라호마 출신의 중상층 백인 남성일 뿐이라는 것을 깨닫게 되었습니다. 사용자는 저의 입장이 아닙니다. 그들은 여성, 유색인종, 장애우이거나 미국인이 아닌 외국인일 수도 있으며 부유하거나 빈곤할 수도 있습니다. 이 사실을 잊고 있다면 공감한다고 할 수 없습니다. 스스로 공감한다고 생각한다면 자신만의 가정에 몰입한 결과입니다.
우리는 페르소나를 만들어 상황에 맞는 질의를 수행하고 가능한 모든 피드백을 받을 수 있습니다. 하지만 페르소나를 우리가 써야 할 가면으로 취급하는 순간, 공감한다고 착각하게 됩니다. 이는 공감하는 것이 아닙니다. 우리는 이 가면을 쓴 채 변함없이 우리의 개인적인 경험, 편견, 사회적 및 경제적 특권을 전달하기 때문입니다.
디자인 리서치를 활용하여 사용자의 정체성에 대한 편견과 가정뿐만 아니라 디자이너 자신의 정체성에 대한 편견과 가정을 정면으로 직시할 때 비로소 관찰은 공감으로 변합니다.
~ 딜런 윌뱅크스(Dylan Wilbanks), 인티그리스 UX 디렉터
 
사용자 행동 이면의 감정까지 디자인하십시오.
우리 모두 정도는 다르지만 “이번 주에는 월요일부터 토요일까지 운동해야지”라고 말해놓고 좌절을 경험한 적이 있습니다.(새해 결심을 떠올려 보십시오.) 그러나 여타의 이유로 잘해봐야 한 주에 2~3회 정도 운동하는 데 그쳤을 것입니다.
한 프로젝트를 진행하면서 필자는 사용자의 태도와는 별개로 실제 행동을 파악하고는 새삼 놀랐는데, 사용자를 논리적이고 이성적인 태도와는 다른 행동으로 이끄는 새로운 “태도”를 포착한 것이 아니었다는 점이었습니다. 더욱 심도 있게 살펴보니, 사용자는 철저하게 감정에 기반한 태도가 아닌 자신의 논리에 기반한 태도를 보여줬던 것입니다. 이것이 바로 우리 팀이 사용자의 특정 행동을 유발하는 감정에 기반한 태도를 디자인하게 된 이유입니다. 결론적으로, 사용자의 행동 유도를 위한 디자인 개념을 초월하여 기능적인 측면은 물론 기쁨의 감정까지도 선사하는 사용자 경험을 만드는 것입니다.
~ 소피아 M 칸(Sofia M. Khan), 제너럴 어셈블리 디자인 스튜디오 컨설턴트 겸 UX 강사
 
헨리 포드가 한 질문은 틀렸습니다.

“사람들에게 원하는 것이 무엇인지 물으면 더 빠른 말(馬)이라고 대답할 것”으로 단언했던 헨리 포드(Henry Ford)의 언급은 세상을 바꿀 만한 획기적인 아이디어를 구상하는 과정에서 고독하고 개인적인 경험으로서 디자인 혁신의 당위성을 논할 때 아마도 가장 많이 인용되는 문구 중 하나일 것입니다. 하지만 사용자와의 작업 경험이 필자에게 이 인용구가 현실과는 정반대라는 점을 일깨워 주었습니다.
사용자와의 작업 경험을 통해 볼 때 포드가 던진 질문은 틀렸으며, 이해가 결여된 것으로 제대로 된 질문이 아니었습니다. 사용자에게 무엇이 필요한지를 묻기보다 무엇을 원하는지를 묻는 것은 기본적으로 결함이 있는 접근 방식입니다. 공감에 필요한 공동의 시간과 관심을 유지하면서 사용자의 행동을 조사해보면, 사용자가 자신이 원한다고 대답한 것과 자신에게 필요한 것을 나타내는 행동은 정반대라는 것을 알 수 있습니다.
사용자의 요구를 해결하기 위해 공동으로 노력하는 과정에서 사용자의 동기, 좌절, 염려 및 생각 등을 공감하고 이해하는 것은 디자이너의 몫입니다. 사용자가 무엇을 원하는지가 아니라 사용자가 무엇을 필요로 하는지를 파악해야 순간의 개인적이거나 집단적인 취향의 변화에 영향을 받지 않고 지속 가능한 디자인을 제작할 수 있습니다. 우수한 사용자 경험을 만드는 일이 그 무엇보다도 중요하며 경험은 기술이 아니라 감정의 산물이라는 점을 알게 되었습니다. 기술과 제품은 상품화될 수 있지만 경험이라는 것은 그런 차원이 아닙니다.
~ 스콧 포셰이(Scott Forshay), IBM 모빌리티 및 신생 기술 부문 선임 전략가
 
사용자의 입장이 항상 디자이너의 입장과 일치하는 것은 아닙니다.

필자는 몇 년 전 이벤트 발견 앱인 클러스터(Clustur)를 비롯하여 대학생들을 대상으로 하는 문제 해결 프로젝트를 몇 차례 수행한 바 있습니다. 인근의 지역 이벤트를 찾아주는 서비스는 수없이 많지만 대학생들은 다른 일반인과는 매우 다른 방식으로 생활하고 있으므로 클러스터 앱은 대학생이라는 특정 사용자를 대상으로 한다는 특정한 목표 때문에 다른 이벤트 발견 앱과는 달라야 했습니다.
이들은 우리가 상상조차 할 수 없는 일들을 경험하고 있으며 이 경험이 제품의 사용 방식에 지대한 영향을 미치게 될 것입니다. 개발 초기 단계부터 사용자의 눈높이에서 보여주는 것이 좋습니다. 지금 작업 중인 프로젝트가 100% 완료될 때까지 기다리지 마십시오. 그러다가는 자칫 잘못된 방향으로 흘러가는 솔루션에 따라 개발이 진행될 수 있습니다.
누구나 자신만의 고유한 삶을 영위하고 있습니다. 리서치와 인구 통계 정보를 바탕으로 가정은 할 수 있다 하더라도 디자이너가 사용자의 삶을 직접 살아갈 수는 없습니다. 공감은 디자이너가 갖추어야 할 훌륭한 역량입니다. 사용자의 입장에서 생각해보면 사용자에게 보다 가까이 다가갈 수 있습니다.
~안드레 타쿠얀(Andre Tacuyan), 플레이그라운드 글로벌 UX 디자이너
 
사용자로부터 얻게 된 교훈이 있다면 무엇입니까? 아래 댓글란에 소중한 의견을 공유해 주십시오.
 
 
 
 
디자인. 프로토타입. 공유. 모두가 가능한 하나의 올인원 앱 Adobe XD.
웹사이트 및 모바일 앱을 디자인하고  프로토타이핑하고 공유할 수 있는 최초의 올인원 툴인 Experience Design CC(베타)를 사용하면 아이디어 구상에서 프로토타이핑에 이르는 과정을 신속하게 진행할 수 있습니다. 베타 버전을 테스트해 보시고, 여러분의 피드백을 공유해 주십시오.  다운로드 받기 
 
 
 
 
저자: 쉬나 리요네
쉬나 리요네(Sheena Lyonnais)는 토론토에서 활동하는 작가이자 편집자 겸 디지털 전문가입니다. 그녀는 주간에는 콘텐츠 마케팅을 주 무대로 활동하고 야간에는 디지털 전략을 공부하고 있으며 여가 시간에는 요가를 즐깁니다. 트위터 @SheenaLyonnais를 통해 팔로우하세요.
 
 
 
 
 

Introducing Source Han Super OTC


Adobe

The release of Source Han Serif earlier this month, on 2017-04-03, gave me an opportunity to build yet another resource for stress-testing environments, particularly those that consume OpenType/CFF Collections. (This also continues to simplify file management by combining three Super OTCs into a much larger one.)

Basically, I combined the Super OTCs of Source Han Sans (36 fonts) and Source Han Serif (28 fonts), and for good measure—and to exceed any possibility of a 64-font limit or threshold—I also included the 14 fonts from the Source Han Code JP OTC.
The Source Han Super OTC is over 300MB in size, and includes 78 fonts in total, which are supported by 21 separate 'CFF ' tables. I confirmed that macOS (I am using Version 10.12.4) and the latest Adobe apps support this 78-font and monster-like OpenType/CFF Collection.
I am now curious about Windows…
🤔
 
For those who use the Source Han fonts and have updated to Windows 10 Creators Update, please add a comment as to whether this Super OTC installs and functions in that environment.
As usual, enjoy!
🐡

Using OSGi annotations (>= AEM6.2)

Adobe
From AEM6.2 you can use OSGi annotations in your project, instead of the good-old Felix ones. You can still use the Felix annotations in your project, but I hope after this article you are tempted to use the OSGi annotations.
In this article I will describe how to use them, and some advantages in your code.
Project changes
In order to use them, make the following changes in your pom.xml
Use 3.2.0 or later for the maven-bundle-plugin
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>3.2.0</version>
<inherited>true</inherited>
</plugin>
Add the following dependencies
<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.service.component.annotations</artifactId>
<version>1.3.0</version>
</dependency>

<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.annotation</artifactId>
<version>6.0.0</version>
</dependency>

<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.service.metatype.annotations</artifactId>
<version>1.3.0</version>
</dependency>

Changes
Once you got the project-setup changed, we can have a look what is changed codewise.
First change is that @Service and @Component are now combined, via service you specify which service you are implementing
@Component(service = MySimpleService.class)
Still @Reference remains the same
@Reference
private SlingSettingsService settings;
Only thing here is that the imports have changed, they are now:
import org.osgi.service.component.annotations.Activate;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.ConfigurationPolicy;
import org.osgi.service.component.annotations.Reference;
import org.osgi.service.metatype.annotations.Designate;
For me the biggest change is around @Properties / @Property, defining OSGi properties in your code. You can now specify a proper interface which gives you type-safety for free. To end this, there is no need anymore to ‘read’ the properties in the @Activate-method.
Let me show you this in code:
Specify at class level the object-class-definition
@Designate(ocd = MyServiceConfiguration.class)
In your activate-method the interface is now your argument, so no need anymore to read and convert properties.
private MyServiceConfiguration config;

@Activate
public void activate(MyServiceConfiguration config) {
this.config = config;
}
The MyServiceConfiguration is an interface, that defines the properties and their types.
@ObjectClassDefinition(name = “My Service Configuration”, description = “Service Configuration”)
public @interface MyServiceConfiguration {

@AttributeDefinition(name = “Config Value”, description = “Configuration value”)
String configValue();

@AttributeDefinition(name = “MultipleValues”, description = “Multi Configuration values”)
String[] getStringValues();

@AttributeDefinition(name = “NumberValue”, description = “Number values”, type=AttributeType.INTEGER)
int getNumberValue();
}
This setup will save quite some boilerplate code on reading / converting properties.
Examples
The examples used, you can find here my local public github, also the AEM Core Components can be used as a reference:
MySimpleServiceImpl.java
MyServiceConfiguration.java
AEM Core Components

Finn Harries on Owning Your Impact


Adobe
We all have a responsibility to rise to the challenges that have been put before us. When it comes to protecting planet earth it doesn’t matter what country you’re from, what gender or sexual orientation you are or religion you believe in. This is a problem that affects every single one of us – It is a common thread that unites us all.
It seems odd to have a specific day in the calendar where we appreciate the planet we live on, however we can get so wrapped up in the nuances of our everyday lives that events like these become a critical opportunity to take a step back and reflect on our relationship with the environment around us.
To celebrate Earth Day, thousands of scientists, educators and concerned citizens are marching in the streets of Washington D.C and beyond to defend the role that science plays in our health, safety, economies and governments. They are marching to advocate for evidence-based policy making, better science education and more research funding. There has never been a need so great for scientific progress as there is right now.

But what about you? If you can’t make it to the march then what can you do to take action on Earth Day? Well there are three actions that I have found to be a powerful way to engage with both environmental and climate activism.

1. Educate yourself, then spread the knowledge.
We cannot take a clear position on an issue before we have educated ourselves on the situation at hand. There are plenty of free resources online that provide accurate information in an easy to understand manner. NASA is a great place to start, as is 350.org when it comes to activism. Once we’ve educated ourselves, we must help educate those around us. Friends, family and everyone in-between.

2. Organize; mobilize.
The Women’s March that took place earlier this year is a great example of the power of demonstration. More than 4 million men, women and children around the world took to the streets to peacefully demand change. Smaller scale actions can also have a significant impact. It can be as simple as getting two of your friends to help you write a letter to a local authority in government, or getting a couple of people together to create a piece of artwork that expresses your concern for the environment, be it a film, a photograph, a painting or a performance. For example before the Women’s March I met with a group of friends to design and paint signs that would help make our message clearer. Creativity is a powerful tool for communication and when we unite under one goal we significantly increase our chances of achieving it.

3. Lead by example.
Us creatives all respond to the world around us through our individual means of expression. We should take responsibility within our own work to share and promote the values we believe in. We can’t just talk the talk, we need to walk the walk. We have a really exciting opportunity to rethink the way we design, to reimagine the materials we use to create and to clarify the messages we’re communicating through our work. Taking a sustainable approach doesn’t need to mean sacrifice. In many cases it can produce more innovative and unique results that bring us closer to the natural environment we live in.
So what are you waiting for? Get out there. Educate, organize and lead by example in your own work. Use today to take a step back and think about how you can contribute to playing an active role in the protection and improvement of the planet we live on.

Come See Adobe Sign at a Salesforce Partner Event Near You

Adobe
It’s spring—and in addition to warmer weather and spring break, it’s a top season for partner events for Salesforce customers. Adobe Sign may be sponsoring a partner event near you, and if so, we’d love to see you. We will have teams on-site to chat about the latest Adobe Sign innovations and how we can work together to deliver better signing experiences for you and your customers.
Come see us at these events:
 
New York City – May 2 // Salesforce World Tour New York at Javits Center
It’s always a great show in the Big Apple. And Adobe Sign loves the big stage. Come meet our Adobe Sign team (Gold Sponsor) at the Javits Center to see the latest integration of Adobe Sign for Salesforce, including our fantastic Lightning experience. We’ll show you how our top-rated Salesforce app improves the signing experience for everyone.
 
San Francisco – May 3–4 // Apttus Accelerate at Pier 48
What does your signature say about you? Adobe Sign returns as a Platinum Sponsor of Apttus Accelerate to showcase the advantages of pairing Adobe Sign with Apttus CLM and CPQ solutions. Come visit our booth and meet one of our handwriting analysts to find out what your signature reveals about your personality.
 
Los Angeles – May 8 // Force Academy LA at Cal State Los Angeles campus
We’re taking our five-star solution to Force Academy, a free day of learning for Salesforce users hosted by LA-based Salesforce User Groups at the Cal State Los Angeles campus. Adobe Sign is a Platinum Sponsor. Come brush up on your Salesforce skills, and while you’re at it, see how Adobe Sign can help make you a star in your organization.
 
Austin – May 11–12 // Texas Dreamin’ at The Driskill Hotel
Whether you’re inside or outside the city limits, you’ve got to come see us at Texas Dreamin’. We’re a Gold Sponsor this year, and we’re excited to bring our five-star e-sign solution to the Lone Star State. This great show is put on by the local Salesforce community to grow skills and empower users, and we’ll be there to tell our story.
 
London – May 18 // Salesforce World Tour London at London ExCeL
This show is huge! And we love it. There’s so much to see and do in this fantastic city, but you really shouldn’t miss Adobe Sign at the Salesforce World Tour London, where we are returning as a Gold Sponsor. Our fantastic UK team will be there to demo Adobe Sign integration with Salesforce and show how it drives phenomenal results for organizations in the UK and around the world.
 
Munich – May 31 // Salesforce Essentials Munich at Postpalast
Yes, Adobe Sign speaks German (and all of the other Salesforce languages, too). We are very excited to be a Gold Partner this year at Salesforce Essentials in Munich. Want to talk about e-signatures, digital signatures, cloud signatures, and local data centers? We can cover it all. [URL page above is in German]
 
Frankfurt – June 12 // Salesforce Essentials Frankfurt at Commerzbank-Arena
Adobe Sign is a Gold Partner in Frankfurt, a center of European commerce and industry. And that’s a great place to demo the power and benefits of e-signatures. If you’re in the Frankfurt region, be sure to come see us. [URL page above is in German]
 
Chicago – June 15 // Salesforce World Tour Chicago
This is another can’t-miss opportunity for us to meet with customers and anyone else who is curious about how Adobe Sign can accelerate success in Salesforce. We look forward to seeing you there.

Dave Tech Table: Premiere Pro CC 2017年4月アップデート

Adobe
弊社David K Helmlyによる、Premiere Pro CC 2017年4月アップデートの機能紹介ビデオです。冒頭の約90秒で概要を解説した後、以下の機能を紹介しています。

エッセンシャルグラフィックスパネル
モーショングラフィックステンプレート

After Effectsからのモーショングラフィックステンプレート作成、書き出し

エッセンシャルサウンドパネル

会話の音声レベル自動調整、およびノイズなどの除去

Premiere ProからAuditionへの連携
Adobe Stockへの直接出力
チームプロジェクト

After EffectsとのDynamic Linkに新たに対応

VRアンビソニックオーディオ対応
VR投影法エフェクト
アンビソニックオーディオ対応でのVRビデオ書き出し

Hinter den Kulissen: Das Tiny Atlas Quarterly Magazin


Adobe
Adobe Stock ist vor Kurzem gemeinsam mit Tiny Atlas Quarterly und einer Gruppe hoch talentierter Fotografen nach Tahiti gereist, um Bilder für die Premium Collection von Adobe Stock in Französisch-Polynesien zu machen. Wir haben mit Emily Nathan, Fotografin und Gründerin von Tiny Atlas, über die Ziele des Magazins und die Bedeutung des Reisens für ihre Arbeit gesprochen.
ADOBE STOCK: Kannst Du uns ein wenig darüber erzählen was Tiny Atlas ausmacht?
Emily Nathan: Tiny Atlas Quarterly ist ein Fotografie-, Lifestyle- und Reisemagazin, eine Marke und eine Social Community, die hauptsächlich von der Fotografie lebt. Insgesamt steht bei uns das Reisen im Fokus: im Magazin, bei unseren Events und durch unsere mitreißenden Abenteuertouren.
TINY ATLAS QUARTERLY / ADOBE STOCK
ADOBE STOCK: Wie ist Tiny Atlas entstanden?
Emily Nathan: Ich habe Tiny Atlas ins Leben gerufen, um die Dinge miteinander verbinden zu können, die ich vorher bei den redaktionellen und kommerziellen Projekten vermisst habe. Ich fand, dass die Redakteure immer die gleiche Art von Reisebildern auswählten. Zudem waren das nie die, die ich in meinem persönlichen Portfolio aufgenommen hätte. Tiny Atlas ist auch eine Plattform für meine eigenen Vorlieben.
In der Werbebranche habe ich Erfahrungen mit unglaublichen Projekte gemacht und die Möglichkeit gehabt, Orte auf der ganzen Welt zu bereisen. Aber ich war in meiner Kreativität nie ganz frei, da die Projekte in erster Line den Kunden zufriedenstellen sollten. Tiny Atlas war die Idee, Reisen mit meiner kreativen Freiheit zu verbinden und die Ergebnisse dann mit anderen zu teilen. Die Projekte werden von mir so weit vorbereitet, dass diese dann von involvierten talentierten Fotografen umgesetzt werden können. Es gab bis Dato kein Magazin, das diese Elemente derart miteinander vereint hätte – also habe ich es einfach selber gemacht.
TINY ATLAS QUARTERLY / ADOBE STOCK
ADOBE STOCK: Warum ist das Reisen für dich als Fotografin so wichtig?
Emily Nathan: Reisen ist die beste Art, um auf der Welt Verständnis füreinander zu schaffen. Je mehr man reist, umso besser versteht man die Perspektiven anderer Menschen. Ich habe großartige Erlebnisse, wenn ich reise. Dadurch bin ich stärker mit meiner Fotografie, meinen Gedanken und dem kreativen Prozess verbunden. Darüberhinaus ist es interessant und einfach wunderschön.
TINY ATLAS QUARTERLY / ADOBE STOCK
ADOBE STOCK: Was hat dich dazu bewogen, eine Partnerschaft mit Adobe Stock einzugehen?
Emely Nathan: Deb, unser Director of Photography, und ich haben letztes Jahr an der Adobe MAX teilgenommen. Wir waren von all den Präsentationen und Demos von Adobe Stock beeindruckt – vor allem von den integrierten unterschiedlichen Anwendungen. Wir finden, dass Adobe Stock ein wichtiges Projekt ist und sind stolz darauf ein Teil davon zu sein. Bei Tiny Atlas arbeiten wir mit mehreren vielversprechenden Talenten zusammen. Durch die Beteiligung an der Premium-Sammlung bekommen sie eine Plattform für ihre Arbeiten und ihre Geschichten.
TINY ATLAS QUARTERLY / ADOBE STOCK
ADOBE STOCK: Was hat dir während der Zeit auf Tahiti mit deinen Kollegen besonders gefallen?
Emely Nathan: Als Fotograf ist man gewöhnlich allein oder man hat, im Falle eines Werbefotografen, die Verantwortung für ein Team. Daher war es spannend zu sehen, wie so viele Fotografen in einer Gruppe zusammenarbeiten. Wir waren auf Tahiti nicht nur von der Schönheit und Wärme des Landes überwältigt, sondern hatten auch unglaublich viel Spaß am Fotografieren. Es fühlte sich wie eine kleine einzigartige Welt an, die, durch das Magazin ermöglicht, diese vielen menschlichen Perspektiven zu einem gemeinsamen Projekt zusammenführte.
Wer jetzt Lust bekommen hat mehr Bilder von Tiny Atlas zu sehen, findet hier auf Adobe Stock das Anbieterprofil. Auch zu unserem April Trend gibt es noch weitere interessante Artikel, in die ihr mal reinschauen solltet:

Visual Trends im April: No Man Is An Island
Futuristische, hochgradig abstrakte Designs von Ingrid Tsy