Give readers the X content they need without filling the page with feeds. Agree with your admin how many posts to show and how often to load them. This helps you plan API costs.
Why use this pattern?
A page full of feeds is hard to scan. Readers may miss the main point. Each profile or List timeline also loads posts with your team’s X API key. X charges for those reads.
Fewer timelines can mean fewer paid reads. A set post count and refresh time make those reads easier to plan.
Live example
Below is a sample page that follows this advice. Imagine a team made it to explain Atlassian’s Rovo Dev launch. The team wrote the text. The post and the timeline come from X Connector and work on this page.
Rovo Dev: what it means for us
Summary
Atlassian added Rovo Dev to Jira on . It can take a coding task, write the code, run tests and open a pull request. We will try it on 2 small tasks first.
The announcement
One post is enough here. It is the source for the summary.
More from Atlassian
Five recent posts, in case there is follow-up news.
Next steps
-
Pick 2 small Jira tasks for Rovo Dev.
-
Review its pull requests at the next team meeting.
The key facts are in the text. Each embed has a reason above it, and there is only one timeline. It shows the same account and post count as the timeline in Embed a profile timeline. The app saves those posts once, and both pages show the saved copy until the next refresh.
Before you start
-
You can edit the page.
-
For profile or List posts, agree with your admin on X API access and credits. Choose how often to load new posts.
Build the page
-
Above each embed, write why readers need it. Use one post if that is all the page needs.
-
For a timeline, try 10 posts and 400 px for Widget height. Readers can scroll inside it. Change these example settings to fit your page.
-
Use alignment controls. For a fixed-width timeline, turn Full width off before setting its width.
-
Reuse the same source and post-count settings where useful. Ask your admin how often to load new posts.
-
Check the page as a reader and ask your admin to review usage costs after adding timelines.
Check before sharing
Check that readers can find the main point without opening every embed. Sharing saved posts can mean fewer requests to X. The app cache and X’s daily repeat-charge rule do not put a fixed cap on your bill. Keep the key facts in Confluence text.
Use it with these patterns
Apply this advice to each page you build: