- How do I install pixney/statamic-twitter in a Statamic project?
- Install it from your project root with Composer: composer require pixney/statamic-twitter. Modern Statamic addons are auto-discovered, so you normally will not need to register a service provider by hand. After installing, check the package README for any publishable config or assets, then commit your composer.json and composer.lock.
- Which Statamic and Laravel versions does pixney/statamic-twitter support?
- The addon is built for Statamic, which means it runs inside a Laravel application and follows Statamic's addon conventions. The README does not spell out version constraints, so check the require block in the package's composer.json before installing. If you are on a newer Statamic major than the package targets, test it in staging first or look for a maintained fork.
- Do I need Twitter/X API credentials to use this addon?
- Yes. Fetching tweets from Twitter/X requires API access, and X now generally requires a developer account plus an access tier. You will typically create an app in the X developer portal and supply the resulting keys or bearer token through environment variables. Keep those credentials in .env and out of version control.
- How do I display tweets in a Statamic Antlers template?
- The addon ships template tools, so the usual pattern is to call its tag or variable inside your Antlers layout wherever the feed should appear. Check the README for the exact tag handle and supported parameters before wiring it into production templates. Wrap the output in your own markup and CSS so the feed matches your site design.
- Can I cache tweets so I don't hit Twitter/X rate limits?
- You should. Twitter/X API rate limits are strict, especially on lower access tiers, and a live request on every page view will exhaust your quota quickly. Cache the fetched payload with Laravel's cache or Statamic's static caching and refresh it on a schedule via a command or task. A TTL of 15 to 60 minutes is a reasonable balance between freshness and quota.
- Is pixney/statamic-twitter still actively maintained?
- Pixney addons tend to be small single-purpose packages, and this one's README is minimal, so review the repository commit history and the latest release date on Packagist before adopting it. If the most recent release predates your Statamic major version, plan either a small patch yourself or a fallback approach.
- What happens if the Twitter/X API changes and the addon breaks?
- Because the addon wraps an external API, breaking changes on X's side can break your feed even when the PHP package itself has not changed. Build your templates defensively: handle empty results and render a fallback such as a link to your profile when a fetch fails. Running the fetch behind a cache or scheduled job also limits the blast radius.
- Can I build a full social feed page with this addon, or is it only for single embeds?
- The package is described as fetching and displaying tweets for social feeds and embedded posts, so it should support rendering a list of tweets in a template loop. Before relying on richer data such as media, threads, or engagement counts, verify which fields the addon actually returns. For a simple latest-tweets section it stays lighter than pulling in a full social SDK.
- How do I test tweet rendering without calling the live Twitter/X API?
- Fake or mock the HTTP layer so your tests never reach out to X: Laravel's Http::fake and cache fakes work well if the addon uses the HTTP client internally. Alternatively, seed the cache with a fixture payload before rendering the template in a feature test. In both cases, assert on the rendered Antlers output rather than the raw API response.
- What are the alternatives to pixney/statamic-twitter for embedding tweets?
- For simple embeds you can paste X's official embed markup or keep a small Blade or Antlers partial, which avoids an API dependency entirely. If you need fetched data, look at maintained Laravel Twitter/X API wrappers or other Statamic social-feed addons and check release recency. Pick based on whether you need live data or just static embeds.