Skip to main content

Work

Drupal
Integration
  • Drupal 10
  • Twig
  • Tailwind CSS
  • OpenAI API

Dive Into Python — Drupal 10 + OpenAI API integration

300+ hours of Drupal 10 engineering on diveintopython.org across 2023–2024 — new Jobs and Functions sections, OpenAI/ChatGPT content services, Feeds API + Queue API for imports and background work, Tailwind CSS front-end, fully responsive.
Client
Dive Into Python
Year
2023–2024
Dive Into Python homepage

What we shipped

Key outcomes

  • Built new Jobs and Functions sections — listing + detail templates on Twig + Tailwind
  • OpenAI/ChatGPT integration for content services — custom backend services over Guzzle
  • Feeds API for data imports + Queue API for background work; responsive across all devices

Dive Into Python is a Python-education platform with a curated jobs board, running on Drupal 10. Across 2023 and 2024 we contributed 300+ hours of engineering on it — new site sections, ongoing development, and the back-office plumbing behind both. The two biggest visible additions: a Jobs board aggregating Python opportunities, and a Functions docs section with paired listing and detail pages.

Dive Into Python — Jobs section: aggregated Python opportunities, listing layout
The Jobs section — aggregated Python opportunities, one of the new sections built in 2023–2024.

The Functions section in particular is a structured docs build — a list view that scales as the docs index grows, and a detail layout for the single-function pages. Both run on Drupal 10 with Twig templates and a Tailwind CSS front end, fully responsive across all devices.

Dive Into Python — Functions list page: structured docs index for Python built-in functions
The Functions list page — a structured docs index built on Drupal 10 with Twig templates and Tailwind styling.
Dive Into Python — Function detail page: full docs layout for a single Python function
A Function detail page — the docs section's full-page layout, paired with the list view above.

Behind those sections sits a data layer worth naming. Content imports run through the Feeds API; longer-running tasks push through the Queue API, so editorial workflows don't block on slow work. And the engineering hook of the engagement: custom backend services calling the OpenAI / ChatGPT API to clean and enrich content — full-stack work, with the HTTP transport on Guzzle.

Got a similar build in mind?

Tell us about the platform, the constraints, and the timeline.

  • Reply within one business day, weekday hours UA / EU.
  • 30-minute discovery call when it is useful.
  • Scope written around deliverables, risks, and ownership.
https://ukrainix.com