At Losyef Yazılım there is no "I use this on every project" list. The tool is matched to the project: Astro for a content-heavy business site, React and Next.js for work that needs application logic. This post explains the questions behind that split.
Five questions first
The choice starts with the work, not with a favorite technology:
- How many pages will there be? A site with a handful of pages and a site that keeps growing aren't built the same way.
- Who will update the content? You, or will you send requests and someone else makes the change?
- Is anything dynamic? Forms, search, filtering, user logins.
- Will it have grown a year from now?
- Does anything need to run on a server?
More often than not, the answers point to the tool on their own.
When Astro fits
For sites whose pages are built once, in advance, and don't change per visitor: business sites, service pages, project galleries, blogs. The result is plain pages with nothing running on a server. They load fast and are simple to host.
That's why MT Mobilya's 21-page site was built with Astro: it's content-heavy, nothing on screen changes per visitor, and updates are made by Yusuf rather than the workshop.
The choice for this site
The site you're reading was also built with Astro, but not by default. Yusuf wanted to see an option other than Astro, so Eleventy and Next.js were compared. Plain HTML was ruled out because this is a multi-page site: the repeating parts (menu, footer, cards) would have had to be managed by hand on every page. After the comparison, the decision was to stay with Astro.
When React and Next.js fit
For work where screens change per user, where there are multi-step forms, or where there is real application logic. Reusing components is handled well, and the setup leaves room to grow.
There is a cost: more setup and maintenance, and dependencies that need updating over time. For a simple business site, it's too heavy. Hosting also brings a decision that has to be made at the start: to run on static hosting, the project either needs a static export or a host-specific adapter. Changing that later is expensive.
What if you'll update the content yourself?
Then the question changes. If the site owner needs to edit their own content, a content management system like WordPress comes to mind. But that means separate hosting and constant security updates, and it doesn't work with an automatic publish-from-GitHub setup. That's why "who will update the content?" is always one of the first questions.
Needing a server doesn't make the whole site an app
A site with pre-built pages can still have small pieces that run on a server when needed: a form, or a request that uses a secret key, can be handled by a small function inside the site. There's no need to build the whole site as an app. The first question is whether a separate server is really needed.
In short
The tool comes from the answers. Content-heavy and the same for every visitor: Astro. Application logic: React and Next.js. If you have a project in mind, answering these five questions in the email draft on the contact page makes the choice faster.
Working on something similar? Get in touch on the contact page.