Weave Code
Contentful Laravel Package
markup/contentful
A Laravel package for integrating Contentful into your applications, providing a convenient bridge to fetch and work with content from the Contentful CMS API. A lightweight option for teams already using Contentful who want a simple PHP/Laravel integration layer, though it has a small community and...
A client library to integrate with the Contentful APIs (Content Delivery and Content Management) for PHP 5.6+.
Frequently asked questions about Contentful
- Is markup/contentful still maintained and does it support Laravel 10 or 11?
- No. The package has been abandoned since April 2018, its last release predates PHP 7.2, and it never declared PHP 8 support. Composer resolution against Laravel 10 or 11 on PHP 8.1+ is likely to conflict or require ignore-platform-reqs workarounds that add production risk.
- How do I install markup/contentful in a Laravel application?
- You would normally install it with Composer, but on a modern Laravel 10 or 11 project the dependency constraints are frozen in the Laravel 5.6 era and installation will often fail. Forcing it with --ignore-platform-reqs is possible but pushes unsupported PHP and Guzzle/PSR-7 versions into your application. That is not a safe baseline for a new integration.
- Does markup/contentful include a Laravel service provider, facade, or config file?
- No. Despite being described as a Laravel package, the evaluation notes it is a thin plain-PHP client for the Contentful Delivery API with no service provider, config publishing, facade, or Illuminate bindings. A Laravel application must wire the object graph itself, typically behind a repository or reader interface.
- Can markup/contentful resolve linked entries and assets from Contentful?
- That is not guaranteed and should be verified before relying on it. Contentful returns entries as links with an include depth, and a lightweight 2018 CDA client may return raw links that your application must hydrate itself. If link resolution is not handled by the package, you will need to build that logic in a wrapper.
- Does markup/contentful support Contentful's Sync API or Preview API?
- The package is positioned as a read-only Contentful Delivery API client, and the evaluation questions whether it exposes the Sync API or Preview API at all. Sync is the practical way to bulk-mirror content using initial sync plus nextSyncUrl, while Preview uses a different host and token for editors. Verify both explicitly; if absent, you own those code paths.
- What should I do about caching and rate limits with the Contentful Delivery API?
- markup/contentful does not provide a cache abstraction, retry/backoff, rate-limit awareness, or Laravel event/logging integration. Contentful enforces per-space request ceilings, so production use requires your own cache decorator and throttling around the client. A common approach is to wrap the package in a repository interface and cache published entries outside the package.
- Does markup/contentful work with PHP 8.1 and modern Composer dependencies?
- No supported PHP 8 compatibility was ever declared. The last release is from the PHP 7.1 era, and its HTTP and PSR dependencies are likely stale enough to pin or conflict with a modern Laravel application. Treat PHP 8.1+ support as unsupported unless you are prepared to fork and maintain the package.
- How does markup/contentful handle multiple locales and fallback languages?
- The available context does not confirm explicit locale, wildcard locale, or fallback-chain handling. Multi-locale behavior is one of the key questions to verify against the source, because Contentful locale and fallback semantics are easy to get subtly wrong. If the package does not handle it, plan to implement locale selection and fallback in your own reader layer.
- What are the alternatives to markup/contentful for Laravel and Contentful?
- Contentful provides an official maintained PHP SDK and a first-party Laravel integration, which are the natural alternatives. Choosing a third-party 2018 client over the vendor-supported path is hard to justify unless existing code already depends on it. A small custom repository around the official SDK is often the most maintainable option.
- Is markup/contentful suitable for production use in a new Laravel project?
- Generally no. It is abandoned, has zero dependents and only 12 stars, lacks Laravel-native integration, and carries unmaintained HTTP dependencies with no CVE response. The capability of serving Contentful content through Laravel is worth doing, but this artifact is replaceable and should not be the foundation for a new production integration.
Weaver
How can I help you explore Laravel packages today?