Skip to content

Commit 0267d39

Browse files
authored
Merge pull request #11 from tcaldwell-x/update-directory/ariana
update customer directory
2 parents 0f94688 + f12f318 commit 0267d39

File tree

4 files changed

+18
-27
lines changed

4 files changed

+18
-27
lines changed

images/newtypefully1.png

1.54 MB
Loading

images/newtypefully2(1).png

1 MB
Loading

resources/enterprise/customer-directory.mdx

Lines changed: 13 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Enterprise data customers
3-
sidebarTitle: Customer Directory
2+
title: "Enterprise data customers"
3+
sidebarTitle: "Customer Directory"
44
---
55

66
import { IntroCard } from '/snippets/card.mdx';
@@ -23,7 +23,7 @@ Here's the modified version of your code with all images removed from the IntroC
2323

2424
<Tabs>
2525
<Tab title="A-E">
26-
<CardGroup cols={3}>
26+
<CardGroup cols="3">
2727
<IntroCard title="Agorapulse" href="https://www.agorapulse.com/?utm_source=data_website&utm_medium=twitter%20enterprise%20customer%20directory" />
2828

2929
<IntroCard title="Alethea" href="https://www.alethea.com/?utm_source=data_website&utm_medium=twitter%20enterprise%20customer%20directory" />
@@ -35,7 +35,9 @@ Here's the modified version of your code with all images removed from the IntroC
3535
<IntroCard title="Audiense" href="https://audiense.com/" />
3636

3737
<IntroCard title="Avaya LLC" href="https://www.avaya.com" />
38-
38+
39+
<IntroCard title="Ayrshare" href="https://www.ayrshare.com/" />
40+
3941
<IntroCard title="Blinkfire Analytics" href="https://www.blinkfire.com/" />
4042

4143
<IntroCard title="Bloom Social Analytics" href="http://bloomsocialanalytics.com/?utm_source=twitter_data_website&utm_medium=enterprise%20customer%20directory" />
@@ -97,9 +99,8 @@ Here's the modified version of your code with all images removed from the IntroC
9799
<IntroCard title="Eyesover Technologies" href="https://www.eyesover.com/?utm_source=twitter_data_website&utm_medium=enterprise%20customer%20directory" />
98100
</CardGroup>
99101
</Tab>
100-
101102
<Tab title="F-K">
102-
<CardGroup cols={3}>
103+
<CardGroup cols="3">
103104
<IntroCard title="Facelift" href="https://facelift-bbt.com/en/" />
104105

105106
<IntroCard title="Factal" href="https://www.factal.com/?utm_source=twitter%20enterprise%20customer%20directory" />
@@ -149,9 +150,8 @@ Here's the modified version of your code with all images removed from the IntroC
149150
<IntroCard title="Kustomer, Inc." href="https://www.kustomer.com/?utm_source=twitter_data_website&utm_medium=enterprise%20customer%20directory" />
150151
</CardGroup>
151152
</Tab>
152-
153153
<Tab title="L-O">
154-
<CardGroup cols={3}>
154+
<CardGroup cols="3">
155155
<IntroCard title="LexisNexis" href="https://www.lexisnexis.com/" />
156156

157157
<IntroCard title="LifeRaft" href="http://liferaftlabs.com" />
@@ -180,28 +180,19 @@ Here's the modified version of your code with all images removed from the IntroC
180180

181181
<IntroCard title="Notified" href="https://www.notified.com/?utm_source=twitter_data_website&utm_medium=twitter%20enterprise%20customer%20directory&utm_campaign=twitter%20enterprise%20customer%20directory" />
182182

183-
<IntroCard title="NTT DATA Corporation" href="https://partners.x.com/en/partners/ntt-data">
184-
185-
</IntroCard>
183+
<IntroCard title="NTT DATA Corporation" href="https://partners.x.com/en/partners/ntt-data" />
186184

187185
<IntroCard title="OBI4wan" href="https://www.obi4wan.com/nl/?utm_source=twitter%20enterprise%20customer%20directory" />
188186

189-
<IntroCard title="Oktopost" href="https://www.oktopost.com/">
187+
<IntroCard title="Oktopost" href="https://www.oktopost.com/" />
190188

191-
</IntroCard>
189+
<IntroCard title="Ontic" href="https://ontic.co/?utm_source=twitter%20enterprise%20customer%20directory" />
192190

193-
<IntroCard title="Ontic" href="https://ontic.co/?utm_source=twitter%20enterprise%20customer%20directory">
194-
195-
</IntroCard>
196-
197-
<IntroCard title="Orlo" href="https://orlo.tech/">
198-
199-
</IntroCard>
191+
<IntroCard title="Orlo" href="https://orlo.tech/" />
200192
</CardGroup>
201193
</Tab>
202-
203194
<Tab title="P-Z">
204-
<CardGroup cols={3}>
195+
<CardGroup cols="3">
205196
<IntroCard title="PeakMetrics" href="https://www.peakmetrics.com/" />
206197

207198
<IntroCard title="Pickaw" href="https://pickaw.com" />

success-stories/typefully.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@ description: "Helping creators + companies manage and optimize their content on
77

88
## The Challenge
99

10-
Typefully was born a tool to write threads on Twitter, before it was rebranded as X. As users of the X API for many years now, they’ve always followed and updated X API developments closely to provide the best possible experience to their users, and adopt the latest features very quickly. By having a close relationship with X,  Typefully has been able to support new X features quickly and offer a very complete publishing experience to their users.
10+
Typefully was born a tool to write threads on Twitter, before it was rebranded as X. As users of the X API for many years now, they’ve always followed and updated X API developments closely to provide the best possible experience to their users, and adopt the latest features very quickly. By having a close relationship with X, Typefully has been able to support new X features quickly and offer a very complete publishing experience to their users.
1111

1212
## The Solution
1313

14-
Typefully leverages several key features of the X API to power their core functionality, ensuring seamless publishing, analytics, and scheduling for their users.
14+
[Typefully](https://typefully.com/) leverages several key features of the X API to power their core functionality, ensuring seamless publishing, analytics, and scheduling for their users.
1515

1616
For **post publishing and scheduling**, we rely on POST /2/tweets to support all post types—text, media, polls, and long-form posts—along with advanced thread management, auto-retries, and quote tweet handling. Typefully’s scheduling system integrates deeply with X, enabling timezone-aware posting, queue management, and automation features like auto-retweets and follow-ups.
1717

@@ -21,9 +21,7 @@ On the account management side, OAuth 2.0 and real-time verification ensure seam
2121

2222
It’s exciting, as Typefully is a small team of just 5 people, to empower creators and companies via the X API to publish more than 130,000 posts every month.
2323

24-
![](/images/success-stories/typefully-1.png)
25-
26-
![](/images/success-stories/typefully-2.png)
24+
![Newtypefully1 Pn](/images/newtypefully1.png)
2725

2826
## The Results
2927

@@ -33,6 +31,8 @@ _Typefully_'s tight integration with the X API has made a real difference in how
3331

3432
Their social media workflow is streamlined through our **collaboration features**, allowing team members to **share draft posts, leave feedback comments, and organize them with tags.** This coordinated approach has been particularly valuable for perfectly timing announcements and news about Raycast products and features.
3533

34+
![Newtypefully2(1) Pn](/images/newtypefully2\(1\).png)
35+
3636
The collaboration tools have eliminated communication silos for teams like Raycast, **reducing the time spent on social media management while improving content quality through close feedback loops**.
3737

3838
By leveraging the X API through Typefully, companies maintain a consistent and engaging social presence without the complexity typically associated with multi-account management. Teams can focus on creating quality content rather than dealing with publishing logistics, resulting in more effective communication on X.

0 commit comments

Comments
 (0)