惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
K
Kaspersky official blog
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
Recorded Future
Recorded Future
Engineering at Meta
Engineering at Meta
U
Unit 42
D
Docker
I
InfoQ
D
DataBreaches.Net
Google DeepMind News
Google DeepMind News
N
Netflix TechBlog - Medium
C
Check Point Blog
The Cloudflare Blog
美团技术团队
V
Vulnerabilities – Threatpost
博客园_首页
T
Threat Research - Cisco Blogs
Google DeepMind News
Google DeepMind News
Attack and Defense Labs
Attack and Defense Labs
A
Arctic Wolf
IT之家
IT之家
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
T
Troy Hunt's Blog
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
人人都是产品经理
人人都是产品经理
C
Cyber Attacks, Cyber Crime and Cyber Security
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Security Archives - TechRepublic
Security Archives - TechRepublic
S
Schneier on Security
Apple Machine Learning Research
Apple Machine Learning Research
MyScale Blog
MyScale Blog
P
Privacy International News Feed
云风的 BLOG
云风的 BLOG
Recent Commits to openclaw:main
Recent Commits to openclaw:main
T
The Blog of Author Tim Ferriss
GbyAI
GbyAI
The Last Watchdog
The Last Watchdog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
aimingoo的专栏
aimingoo的专栏
P
Proofpoint News Feed
The Register - Security
The Register - Security
博客园 - 三生石上(FineUI控件)
Forbes - Security
Forbes - Security
NISL@THU
NISL@THU
Y
Y Combinator Blog
T
Threatpost
Microsoft Azure Blog
Microsoft Azure Blog
L
Lohrmann on Cybersecurity

Sanity.io

A Board Game agent built using Sanity Context and Vercel's AI SDK | Sanity Build a prototype with Claude Code that your whole team can edit | Sanity What’s New - May 2026 | Sanity I built a London pub guide with v0 and the Sanity MCP in six hours. Here's what I learned. | Sanity Build a conference concierge with Agent Context and Anthropic | Sanity Build a content-aware Telegram agent with Vercel AI SDK and Chat SDK | Sanity How I used Agent API to generate photos for my family’s recipes | Sanity What’s New April - 2026 | Sanity Better context, better matches: An AI love story (for dogs) | Sanity How to write for an agent | Sanity Content Agent, meet Slack: AI content operations in your workflow | Sanity Structure powers intelligence | Sanity Your agent needs better content. Here's how to give it. | Sanity How to serve content to agents (a field guide) | Sanity Sanity TypeGen GA: Automatic TypeScript types for content and GROQ | Sanity Sanity is now available on the Vercel Marketplace | Sanity The logo soup problem (and how to solve it) | Sanity Content Releases: From scattered updates to coordinated publishing | Sanity What's New - February 2026 | Sanity How we solved the agent memory problem | Sanity v0 Builder Challenge: The winners | Sanity Introducing: Sanity Agent Skills | Sanity Content Agent: Days of work in one conversation | Sanity Our Sanity Values | Sanity Open Source Pledge 2025: Stepping up when it matters | Sanity v0 builder challenge: $3000 in prizes | Sanity Why AI Breaks Without Structured Content Operations | Sanity What’s New January - 2026 | Sanity BFCM 2025: What teams built when infrastructure stopped being the problem | Sanity How AI shaped holiday shopping and what it means for content in 2026 | Sanity Sanity Studio v5: Embracing React 19 | Sanity You’ll need a CMS eventually. Let your agent set it up. | Sanity “You should never build a CMS” | Sanity AI Content Operations: A 30-Day Implementation Guide | Sanity What’s New December - 2025 | Sanity Scheduled Drafts: Stop manually publishing content at midnight | Sanity What’s New November - 2025 | Sanity Everything *[NYC] 2025 recap: A day of AI, Content Operations, and Culture | Sanity Clankers and content operations | Sanity Content Agent: AI that understands your structured content is here | Sanity Why design-driven content modeling creates technical debt, not velocity | Sanity What's New October - 2025 | Sanity From studio to inbox: How Kevin Green eliminated email campaign friction | Sanity The content editor's guide to content operations [E-commerce edition] | Sanity styled-components maintenance mode: A 40% faster fork | Sanity From zero code to a live website in 7 hours (thanks, Cursor!) | Sanity First attempt will be 95% garbage: A staff engineer's 6-week journey with Claude Code | Sanity Internationalization is more than translating words | Sanity What's New - September 2025 | Sanity We just deleted our 35k-member community Slack | Sanity What's New - August 2025 | Sanity The engineer's guide to content operations [E-commerce edition] | Sanity SEO for AI: Evolving from Web Pages to the Content Lake | Sanity What's New - July 2025 | Sanity Sanity Studio v4: A major version bump for a minor reason | Sanity What's New - June 2025 | Sanity Dashboard and Insights: Your New Content HQ | Sanity Canvas: AI-accelerated, context-aware, freeform authoring | Sanity Agent Actions: AI building blocks for structured content | Sanity Functions: Life beyond pressing publish | Sanity A new era for content applications with Sanity App SDK | Sanity The end of CMS era and our $85M Series C. | Sanity What's New – May 2025 | Sanity Introducing the Sanity Model Context Protocol (MCP) server | Sanity What's New – April 2025 | Sanity Pushing all the envelopes with ambitious content | Sanity Self-hosting is only free if your time is worth nothing | Sanity Content that lasts: Scaling beyond your frontend | Sanity The Live Content API is now Generally Available | Sanity The future beyond AI chat bots | Sanity Learning the new skill of working with AI | Sanity What's New - March 2025 | Sanity Give it in plain text: Making your content AI-Ready | Sanity No More 'DO NOT PUBLISH': Introducing Content Releases | Sanity React in 2025, what's next? | Sanity The final boss of front-end: block editors | Sanity Introducing Sanity for Startups | Sanity A block content editor that loves you back | Sanity A Black Friday Snooze Fest: Massive Traffic, No Drama | Sanity How to make a recipe site that scales well | Sanity The Sanity Winter Release 2024 | Sanity AVIF Arrives, Sanity’s Promise Fulfilled | Sanity Sanity joins the Open Source Pledge | Sanity Your content is now Live by default | Sanity Begin Team to Join Sanity | Sanity Sanity Digest - September '24 Edition | Sanity Sanity partners with Google. Now live on the Google Cloud Marketplace. | Sanity Sanity Digest - August ‘24 Edition | Sanity Now playing: the latest Mux Video Input plugin for Sanity | Sanity Community Digest - June ‘24 Edition | Sanity Community Digest - May ‘24 Edition | Sanity Guide to Sanity's newest product announcements | Sanity AI and Content Creation: A Leader's Guide | Sanity Of course, you should be able to type your content quickly! | Sanity New to AI Assist: translation, reference suggestions, image generation | Sanity Speak the language of your editors: Sanity Studio UI localization | Sanity Introducing the new Sanity Growth plan to serve collaborative teams | Sanity Presentation: Work faster than ever with structured content | Sanity Goodbye Feedback Frenzy, Hello Sanity Studio Comments! | Sanity Easing into the App Router with the Sanity Toolkit for Next.js | Sanity
“Our digital experience is our brand”: Conversation with Scott Gentz of AT&T | Sanity
Sarah Beldo · 2022-12-20 · via Sanity.io

“Digital transformation” can take many forms. At AT&T, an important part of their transformation involved shifting to a structured content model, so they can implement a true multichannel branded experience for their customers.

With 30+ years of experience across multiple industry sectors, Scott Gentz — Director of Technology, Strategic Platforms — was at the helm of this evolution, which changed how the company thought about creating and managing content, as well as how the engineering team functioned. We sat down with him to learn more about AT&T’s journey.

On meeting customers’ heightened expectations

It used to be that our logo was our brand, but now our customer experience is our brand. Our digital experience is our brand.

Our customers want a feeling of familiarity and human touch when interacting with our brand. They want to be able to trust that we understand them and what they want, whether they’re buying something or solving a problem or learning the answer to something — online, through a store, or through a chat agent. These heightened expectations changed how we think about our platforms.

Today, the landscape is evolving so that “digital” is anywhere and everywhere. Knowing this, we started thinking about the customer journey and how we wanted to tailor the experience. How do we bring a consistent experience to someone, wherever they are in their journey, whether that’s talking to a virtual chatbot, visiting our website, or walking into a brick-and-mortar store?

On the journey to adopting structured content

It all started back when we were pivoting from monolithic to distributed apps, dealing with the complexity of maintaining large sites at scale. We have over 4,000 microsites, with multiple product teams and marketing teams managing them. We have content that’s shared across all of these different channels.

We realized we needed to start breaking apart our platforms and making them more flexible, easy to use, and easy to build. It wasn’t too long after that when microservices started coming along, where we were decoupling and creating more fine-grained APIs.

The UI followed, and eventually we realized that the same principles applied at the front end. We had to start decoupling. We had to start breaking content down into smaller chunks and adding structure so we would have the flexibility to do great things at scale. All the pieces started to come together, and we realized that we had to look at our entire approach more holistically.

On charting a path to transformation

The pain points that we were looking at were well-known throughout the company. How do we get to market faster? How can we reduce the amount of content that we have to maintain in multiple places?  How do we optimize for what really matters, which is establishing a connection and loyalty with a customer?

For example, we observed that if a customer was coming to us on the website, they would see a particular offer. And then they would move into a different channel, but maybe that offer was now different and not quite contextually aligned with what they’d previously seen. And we pinpointed the reason for that disparity: we were authoring and maintaining content in multiple places.

We knew fixing that problem would help us deliver a more consistent experience and get to market faster. We needed an approach that would adapt to our marketing needs so that we could get things out quicker.

Those were the drivers that helped us align the other internal stakeholders with the business value of what we were trying to accomplish. And things really took form when we started thinking about how to do this at scale. How do we build different presentation layers, with the right tooling and stack, and revamp our design system? We started adopting a more componentized, building-block approach.

Then, we started thinking about collapsing all the tools that feed into this approach. How do we start thinking about the customer experience sooner? How do we align our technologies? It was a change in thinking.

On shifting people’s mindset

As a 30-plus-year technologist, I focus first on technology. But I've learned over time that culture is equally important: how people think, and their different perspectives on things.

Any time you pivot to a new way of doing things, there's risk. If you want people to adopt a new approach, it’s important to talk to them about how their role will change. How will they engage with content within the context of this new way of thinking?

Initially, our content implementers were still working in the old way where they were thinking about how to manually structure the content. And we had to tell them that they no longer had to worry about that. Instead, we were going to structure the content behind the scenes, but make the authoring simpler for them. Now, they can preview the content in different formats and see how their end product looks.

At first, they had some concerns that not being able to directly manipulate the structure would mean giving up control. So we focused a lot on education, plus getting feedback from different folks who were working with content or the user experience.

Sometimes we put blinders on and we want to solve everything with a technology solution, but it's good to step back and look at things holistically. Not everything is going to be technology driven. We have to think about how the roles are going to evolve, how our teams are going to work in the future. I think that we’re going to continue to evolve how we work and how we build things.

On what’s next for AT&T

One of the things I liked in Carrie Hane’s book, Designing Connected Content, was where she talked about using domain-driven design to think about how to tackle a problem. We’ve really latched on to that, even using behavior-driven design when we think about modeling content and user experiences.

Now we’re not just limited to thinking about dropping a piece of content into a template. Instead, let's think about how a customer's interacting with a piece of content at a particular point in time, whether it's online or with a virtual agent. Thinking this way opens our minds to how we can structure things and build new things.

For example, we do point-in-time activation offers, whether it’s a retention offer, upsell, or cross-sell. We began by thinking only about the online context.

But then we started talking to our virtual chat teams, and we wondered: could we take this concept of an offer and also use it within this intent model?

That insight prompted us to change the way we structured our offers. We went back and started thinking about it within the context of how we could show an offer in a chat and how we could reuse content and content schemas across channels and different UI stacks.

By pursuing this approach we were able to optimize and make it more efficient for our content implementers and UI developers to generate content and the UI and in turn we are able to deliver a more consistent user experience for our customers by reusing content.

At AT&T, like many companies, our customer experiences are no longer these static stitched together customer journeys. We are using real-time, clickstream data to provide customers the most contextual and personalized experience we can give them.

As technologies like Edge Decisioning and Generative AI/ML evolve it will be even more critical to be able to structure content in a way that it can be adapted and composed to better deliver customer experiences in a fast, seamless,  contextual-relevant manner via no/low code strategies. Exciting times are here for this industry for sure!