System
We create the most appropriate system to make the plan of new structure in business operations come alive, continuously improving efficiency, optimizing existing operations.
-
01
Planning
As we analyze the current condition of your existing system, we will offer the most fitting system for your website.
By analyzing your current system, we will be able to offer the best possible solution for your website. The selection of the system will be based on the purpose of its usage, as well as its future use which leads us to plan a better schedule.
-
02
Development
We will build a system based on the specifications that have been decided at consultation.
A system will be built based on your budget and schedule as well as the specification that has been agreed on. Mockup will be submitted to ensure that we are on a right path to build your system.
-
03
Test
We will examine our system to see if it operates correctly.
In order for us to get an approval from you, we ask you to test our system making sure that inserting contents and making some changes on specification are considered properly.
-
04
Release
The system will be published after the final revision is completed.
After taking in some contents and rearranging the specification, we will prepare putting newly created system on public. Operation support will be provided even after submitting the website to you such as system maintenance.
Ore no Drupal
This is a tech blog of Acret Inc.
We will irregularly post contents related to web development and operation, with a focus on Drupal technology.
-
2026/08/27
Teaching Drupal to Actually Search
Almost every content-driven Drupal site eventually needs a search feature, and almost every team underestimates how much is involved in building one well. A naive approach, a Views filter doing a CONTAINS match against the node title and body, works for a handful of pages, but falls apart as content grows: it can't rank results by relevance, it struggles with partial or fuzzy matches, and every query gets slower as the node_field_data table grows. This is the gap that Drupal's Search API module is built to close. Search API doesn't perform searches itself. Instead, it provides a common abstraction layer between Drupal's entities and a variety of search backends (a plain database via search_api_db, Apache Solr via search_api_solr, Elasticsearch, and others), so the rest of the site can be built once, in Drupal's own configuration and Views layer, and swapped to a different backend later without rebuilding the search feature from scratch. This article walks through what Search API is, its core building blocks, and the practical steps involved in standing one up on a Drupal site.
-
2026/08/05
Honeypot and Antibot: Stopping Spam Bots Before They Hit Submit
If you run a Drupal site with a contact form, you know the drill: every morning there's a fresh batch of "messages" from "John" pitching crypto or discount watches. The good news is two free, lightweight modules — Honeypot and Antibot — quietly kill most of this spam without ever showing a real visitor a CAPTCHA.
-
2026/07/16
Twig, Symfony, and the Architectural Shift: Why Drupal 7 Themes Can't Just Be Ported
There's a specific kind of frustration that comes from opening up an old Drupal 7 theme folder, staring at it, and thinking: "surely I can just move this over." The CSS still looks fine. The layout still makes sense. Nothing about the design is wrong. And yet the moment you try to bring it into a current Drupal build, nothing lines up. Templates don't render. Variables come back empty. Things that used to just work now throw errors that don't even look like Drupal errors.
