Article categories: websites, SaaS, cloud

• Decision-Making: Categories

  This category looks at websites from the point of view of the person who has to decide. A business website is a place where a visitor understands what you offer, checks whether it fits and chooses what to do next, so it works best when it is built as a decision system first, with marketing on top of that structure. The articles here describe how decision-makers actually assess a site: whether it is relevant to them, whether the organisation is credible, what exactly is offered, what the risk is and what happens next. They draw on research from Nielsen Norman Group and on the Stanford web credibility guidelines, such as easy contact, a visible organisation and error-free content. Each piece ends with short answers to common questions. Read them if you want your site to support evaluation instead of pushing a message.

• Platforms & Cloud: Categories

  This category covers the technical foundations of platforms and hosting, explained in plain language. We build SaaS products and internal business platforms with accounts, roles, workflows, dashboards and integrations, following the same five stages as every project, with requirements before code. For hosting we set up your application on AWS: Elastic Beanstalk for the application, AWS WAF as a filter against harmful traffic, AWS Lambda to find and block scanners automatically, and ready-made Amazon CloudWatch Logs Insights reports. The AWS account always remains yours. Articles in this category look at how an application is protected from automated scans, what a platform needs written down before development starts and how such systems are checked. Until they are published, the SaaS platforms page and the AWS cloud setup page describe the work in detail.

• Process: Categories

  This category is about the way a website project runs. Every iwebforyou project goes through five stages, counted down from T-5 to T-0, the day the site goes live, and no stage begins before you have approved the previous one. Each stage has a defined result, an approval point and a risk it removes. Changes outside the agreed scope are written down and assessed, never applied informally, so that cost and time stay visible to everyone. At handover you receive full ownership, access details and documentation. The same discipline applies to platforms: requirements are written down before any code, and technology is chosen after them. Articles in this category explain these steps in plain language, what each approval means for you and what we ask from your side in time and decisions. Read them before a project starts, so that you know what to expect at each point.

• SaaS: Categories

  This category brings together our articles on building SaaS platforms, written for people who commission or manage such a product. They cover three things we consider basic. First, development test first: write a failing test, then the code that passes it, then improve the code, so every feature has its check from the start, and every confirmed bug becomes a permanent test. Second, roles and permissions: they are written as a table before any code, based on three OWASP rules, least privilege, deny by default and a check on every request on the server. Third, the separation of customer data, where AWS describes three models: silo, pool and bridge. The model is chosen in the system design, before code is written. These articles are currently available in Greek.

• Speed & Performance: Categories

  This category is about website speed and how it is measured. We guarantee a Google PageSpeed Insights Performance score of 80 or higher on mobile, measured on delivery day, on the home page and one page of each main type. We take five measurements per page and the median counts. If the score is not reached, we fix it at no charge before delivery closes. We guarantee the score, not search rankings. Mobile is the basis because Google's own tools simulate a mid-range phone on a mobile network, and Google uses the mobile version of a site for indexing, so a page that is fast on a desktop can still be slow where most visitors meet it. Articles here explain these ideas in plain language. Until they are published, the speed guarantee page has the full terms and the method of measurement.

• Structure: Categories

  This category collects our articles about structure: how the content of a business website is organised so that a visitor can find it, understand it and act on it. Structure means deciding what information exists, how it is grouped, what a visitor sees first and how they move between pages. The articles here argue that structure comes before design, because design can only support an order that already exists, and that most corporate websites fail for lack of it rather than because they look dated. They also describe the usual causes of failure: no overall structure, generic wording, mixed audiences and no help with the decision. Every article is written in plain language and closes with answers to the questions readers ask most often. If you are planning a new site or reviewing an old one, start here, before any talk of colours or layouts.

• Website Strategy: Categories

  This category gathers our articles on the strategy behind a business website: what the site is for, who it serves and how it should be judged. The articles argue that a business website is a decision system, not a marketing layer, and that its effectiveness is measured by clarity and usability in a real decision, not by traffic or looks. They explain why most corporate websites fail, namely missing structure, generic wording, mixed audiences and no decision support, and what an effective site does instead: it lets a visitor understand what the company does, judge whether it can be trusted, see whether it fits and choose a next step. Credibility signals such as a real address, easy contact and no errors are covered too. Each article is written in plain language and closes with answers to the questions readers ask most often.

← All articles