About

The motivations and philosophy behind the OI Laravel packages

About

Why These Packages Exist

The OI Laravel packages were born out of recurring friction in day-to-day Laravel development. Rather than copying the same boilerplate from project to project, each package extracts a well-scoped solution into a reusable, well-documented library.

The goals are simple:

  • Solve a real problem — no packages for the sake of packages
  • Stay out of the way — minimal configuration, sensible defaults
  • Compose well — each package works standalone; none requires the others
  • Be maintainable — clean code, full test coverage, clear documentation

The Packages

OI Laravel TypeScript was created to close the gap between PHP models and TypeScript frontends in Inertia.js applications. Keeping types manually in sync is error-prone and tedious; this package automates it entirely.

OI Laravel INSEE was built for French-market applications that need to verify or look up company data. The raw INSEE SIRENE API is powerful but verbose — this package wraps it in an expressive Laravel interface.

OI Laravel Documentation emerged from the need to document the packages themselves. Instead of hosting static files or relying on third-party services, this package provides a self-hosted, Markdown-driven documentation system that lives inside a standard Laravel application.

Philosophy

These packages follow the Laravel convention of preferring explicitness over magic and convention over configuration. They integrate naturally into existing Laravel applications without requiring significant structural changes.

All packages are open source, actively maintained, and welcome contributions.

Contributing

Found a bug or have an idea? Contributions are welcome on GitHub. Each package repository includes contribution guidelines, a test suite, and a development setup guide.

Project under MIT License.
Design by