Design InsightsDesign InsightsDesign & Web Insights

A bilingual main site with a six-language requirements form: how should the scope be described?

Language coverage should identify pages, materials, and features separately. Using a hypothetical bilingual site and six-language form, this article distinguishes interface and content translation, foreign-language input, and human communication. Entry wording, missing-version paths, and coverage reviews avoid presenti…

Works locally but fails online: checking runtime compatibility before updating an old website

Compatibility checks start with the live site's actual runtime, then local checkers, extensions, and settings. Using PHP, this article distinguishes syntax checking from execution, identifies new functions and dependencies, and separates compatibility adaptations from upgrades. Isolated tests, related features, and liv…

Why does language switching lose the current page and filters? Testing multilingual URLs

Language-switching context needs page-specific and state-specific rules. This article covers content mapping, target publication states, anchors, filtering, sorting, and pagination, plus original form text, attachments, and private parameters. Deep-URL, round-trip, refresh, and sharing checks prevent homepage redirects…

How should mobile date inputs be tested? Opening a calendar is only the beginning

Mobile date-input acceptance requires more than opening a calendar. This article defines business meanings of start and completion dates, tests actual phone selection, keyboard and system input, clearing, blanks, past dates, and ordering, and distinguishes display formats from stored values. Cross-device, summary, noti…

How should website form test emails be marked to avoid mistaken customer follow-up?

Test records need clear identification and no-follow-up instructions, matching the same saved request and notification. This article defines purpose and entries, controlled contacts, round markers, record identifiers, actual email receipt, and cleanup ownership. Teams can retain traceable conclusions, avoid mistaken sa…

How should foreign-language budget options identify the currency clearly?

Budget currencies should appear with amounts, ranges, and periods; English interfaces do not imply dollars. This article explains budget purposes, currency names and codes, range boundaries, and uncertainty, distinguishing wording translation from reference conversion. Checks across choices, summaries, records, and not…

Why should switching a requirements form's language leave users' existing input untranslated?

Multilingual forms must distinguish system text, field identities, and visitors' original answers. This article explains why switching interface language should not translate existing input, how standard choices retain meaning, boundaries for files and draft recovery, and checks across summaries, notifications, and sav…

One form for website, UI, and brand requirements: how can service switching avoid wrong answers?

Multiple-service forms must align the current service, valid answers, and actual saved scope. This article distinguishes shared information from specific questions, explains retained inputs versus excluded submissions, and covers conditional validation, review summaries, and draft recovery. Switching, returning, and co…

Drawing Uploads for Export Inquiries: How to Explain File Formats, Sizes, and Backup Channels

Set clear drawing upload limits, test refresh and failed transfers, and link backup submissions to the original inquiry until staff can open the correct files.

After changing the website notification email, how can acceptance checks confirm inquiries still arrive?

Accepting a notification email change requires more than successful authentication. This article covers real sources, sender and recipient roles, recovery preparation, and controlled tests, matching the same saved request to target-inbox receipt. It explains inconsistent results, historical resends, test effects, and h…

What is a project-requirements review dialog for? It should help check answers, beyond copying them

Review dialogs should reveal important service-scope, contact, date, and uncertainty errors. This article covers field priorities, shared and specific grouping, unanswered versus undecided states, returning to edit, and current-summary updates. Controlled checks from confirmation through saving verify more than duplica…

How should "Not sure" work in multiple-choice questions without saving contradictory answers?

Uncertainty options depend on whether the whole answer is undecided or only part needs discussion. This article covers exclusive-choice feedback, cancellation and reselection, unanswered versus actively undecided states, and checks for summaries, draft recovery, and saved records. Teams can retain genuine readiness, pa…

Overseas Phone Numbers Keep Failing: How to Test International Contact Details in Inquiry Forms

Test country codes, separators, optional fields, and error guidance for supported regions, then verify complete contact details in saved records and notifications.

What should a submission-complete page show? Explain next steps without inventing response promises

A completion page should show actual saving, verifiable request information, and real next steps. This article distinguishes saving, email notification, and human handling, explains identifiers, corrections, timeouts, and receipt refreshes, and checks the same item across page, CMS, and email. Teams can define feedback…

A requirements form was closed halfway through. Which information should be retained?

Requirements-form draft recovery starts with supported interruption paths, storage location, and validity scope. This article distinguishes refreshes, closed tabs, and device changes, explains text and attachment states, and covers service changes, outdated questions, deliberate clearing, and successful submission. Tes…

How can a contact form prevent duplicate submissions? Disabling the button is only the first step

Disabling a button alone cannot prevent duplicate form submissions. This article distinguishes repeated clicks, network retries, and genuine new requests, explains processing feedback, request identity, checks when results are unknown, and input and attachment recovery. Repeated-click, multiple-tab, and interrupted-res…

A website inquiry says submitted successfully, but no email arrives: what should you check first?

When inquiry notification emails are missing, first check whether the same request was saved in the CMS. This article separately verifies public feedback, CMS records, and actual inbox receipt, explains notification execution and recipients, why authentication success cannot complete acceptance, and how to handle dupli…

Why do long tables become crowded on phones after being entered into a corporate website?

Website table entry requires more than neat borders in the editor. This article explains how to assess row-column relationships, check maximum size and container width separately, organize excessive fields and long explanations, and perform searches and comparisons on actual mobile pages. With headers, units, missing v…

Should an old article's publication date change after an update? Distinguish publishing, editing, and review

Article date maintenance should distinguish first publication, substantive updates, and review, rather than change every save to today. This article explains significant-change decisions, where to record formatting and typos, checks for page and structured information, and CMS triggers tested with three editing actions…

An article cover looks attractive but unrelated: how should website images address the reader's question?

Article images should address objects, processes, and decisions readers need to understand, beyond attractive business photography. This article explains cover and body-image roles, conceptual illustrations versus real screenshots, thematic differences within a consistent visual system, and checks for alt text, caption…

Should SEO information appear in article text? Roles for titles, summaries, and CMS fields

Article text and SEO information should be maintained separately around one topic. This article explains article titles, page titles, list summaries, page descriptions, and keywords, with field-to-output mapping and handover methods, then checks default templates, saved values, and actual page information. Editors can…

How should imported website articles be checked? Titles and visible images are only part of the check

Imported website articles require complete saved-text and reading-structure checks, beyond visible titles and images. Starting with a fixed source version, this article explains paragraph comparisons, heading levels, quotations, image order and alt text, and link targets, then includes reopening and repair records in e…

How should bulk article publishing work in a CMS? Define selection scope and execution conditions first

How can bulk article publishing avoid selecting the wrong scope? This article distinguishes individual selection, the current page, and every draft in the current filter, explains conditions for filter changes, content status, bilingual readiness, and publishing confirmation, and provides acceptance checks using varied…

What if a bulk operation fails midway? Separate completed, unconfirmed, and retryable items

Handling a failed bulk operation starts by separating completed work, submitted requests with unconfirmed outcomes, and work not yet executed. This article explains how to fix the operation scope, record batch results, stop subsequent tasks after an exception, and build safe retry lists from actual record states. Corpo…

How can two people edit website content without the later save overwriting changes?

Concurrent CMS editing requires checking the source version used for each save so an earlier-opened page cannot overwrite a colleague's recent changes. This article distinguishes conflicts in content, publication status, and language versions, explains which inputs to retain and how changes can be merged, and discusses…

The CMS says an article was saved successfully. Why is it still missing from the website?

Article saving and publication are separate outcomes; a CMS success message does not automatically mean visitors can see the content. This article explains reopening the original entry to check data, language statuses, and categories, then inspecting details and lists from the real article URL. Follow evidence when inv…

Chinese is confirmed but English is not ready: how should bilingual website publishing rules work?

Bilingual website publishing conditions require checking necessary materials, confirmed versions, and actual links for each item. Nonempty English fields do not establish readiness. This article distinguishes untranslated, awaiting-review, confirmed, and outdated content, explains synchronized and phased publication an…

How Do You Write Website Redesign Requirements? From Business Goals to a Feature List You Can Verify

Define website redesign goals, content, feature scope and acceptance criteria. See how JVDS Design Studio checked a bulk publishing improvement in its own CMS.

Why Corporate Website Content Becomes Chaotic: Build a Content Operations System Instead of Updating Ad Hoc

Build a Content Operations framework for content models, Owners, fact review, update dates, permissions, SEO/GEO checks, maintenance, retirement and data feedback.

How to Run A/B Testing Beyond “Two Versions for One Week”: A CRO Experiment Credibility Checklist

Build credible CRO experiments with clear hypotheses, correct randomization, SRM checks, consistent exposure, primary metrics, Guardrails, sample duration and review.