The context and limits of the design work and information presented here.
1. The portfolio and its purpose
This website presents the frontend interface development of Maurits Storm, the public name of independent professional MAURITS WILLEM EWOUD STORM VAN S GRAVESANDE. It helps visitors explore frontend interface development before starting a conversation. The identification address is Maroastraat 22, 1060 LG Amsterdam, Netherlands. The pages introduce design possibilities; they do not constitute an accepted project brief, a signed proposal or an assurance that every request can be undertaken.
2. Fictional concept work
Find the useful note, A clear route, A useful response use fictional briefs to demonstrate original frontend interface development decisions. They are not presented as paying clients, delivered commercial projects, published research or independent endorsements. Any values, labels and interface content belong to the example. Similar names outside this portfolio do not establish a relationship. The project pages explain the brief and the implementation choices; their concept status is part of that explanation. No audience, revenue or performance results are claimed for the studies.
3. Mockups and production reality
The examples are locally rendered diagrams or interface demonstrations. Their labels, controls and sample content illustrate a bounded fictional brief. They do not establish that a real system has been deployed, integrated, audited or measured. Any interactive control changes only the example shown in the browser; it creates no booking, account, payment or external record. A production engagement needs its own source content, technical environment, accessibility review and acceptance checks. Visual clarity in a concept does not guarantee a business outcome or establish the accuracy of future supplied data.
4. Descriptions and professional boundaries
The descriptions explain the decisions visible in the examples and the questions useful for defining a project. They do not constitute legal, medical, financial or regulatory advice, or certify an organisation or system against a standard. Any factual information, data definitions, permissions, security requirements and specialist approvals need to be checked in the actual engagement. An interface or diagram can make supplied material easier to use without independently verifying that material. Agree responsibilities and appropriate review before publishing work in a setting where people will rely on it.
5. Rights and outside services
An example being publicly visible does not make it a free asset for commercial reuse. Commissioned usage rights and the handling of third-party materials need their own agreement. Local font files are used under their respective licenses. Your email service and any separately engaged supplier have independent terms and technical behavior. The portfolio cannot guarantee their delivery, availability or execution merely because they are involved in a later conversation.
6. No unagreed outcome promises
Visual design can organize information and shape expression, but the portfolio does not promise a particular level of sales, recognition or audience response. An enquiry does not confirm a delivery date, fee or project acceptance. Any assurances concerning a commission must be identified in its agreed scope. General statements here cannot substitute for reviewing the actual brief, limitations, responsibilities and proposed outputs before work begins.
7. Questions and document relationship
Read this page with the Terms of use, Privacy policy and Cancellation and refund policy. Those pages explain site use, the email-draft workflow and the distinction between an initial enquiry and a paid engagement. A separate written project agreement can address specific matters in more detail. Nothing here excludes mandatory rights. If an example, statement or permitted use is unclear, prepare an email to [email protected] naming the relevant page and question.