Skip to content

About

A web experience for DatePlan, helping couples manage events, reminders, and special moments.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

DatePlan

DatePlan Web

The official website of DatePlan, the app for couples.
Static HTML, CSS and JavaScript. No framework, no build step, no loading screen.

Live site Stack Languages License

Website · Google Play · Organization · Português


The site presents DatePlan to new visitors, sends them to Google Play and hosts the pages the app and the stores need: the privacy policy, the terms of use and the redirects for the feedback and bug-report forms.

Why a plain static site

The first version was written with Kotlin Multiplatform and Compose Multiplatform compiled to WASM. That made sense inside the KMP ecosystem, but it forced a loading screen while the browser downloaded and started the WASM runtime, for content that is completely static. For a landing page whose only goal is to turn visitors into users, that meant:

  • a bad first impression, with a spinner before any content;
  • poor SEO, because crawlers and AI readers (ChatGPT, Perplexity, Gemini) do not run WASM;
  • megabytes of bundle for kilobytes of content;
  • build and deploy complexity for something that does not share logic with the app.

The site was rewritten in plain HTML, CSS and JavaScript and deploys straight to Netlify with no build.

Features

  • Zero loading: renders instantly, no runtime and no heavy bundle.
  • SEO and AEO: indexable by Google and readable by AI models through structured data (JSON-LD).
  • Portuguese and English: detected from the browser, saved in localStorage, switchable in the header.
  • Easy to edit: features, advantages and FAQ live in a single file, content.js.
  • Same identity as the app: Alexandria font, red #FF0000, dark hero and matching spacing.
  • Legal pages: privacy policy and terms of use in both languages, with versioning.

Project structure

.
├── index.html               Page structure (not meant for content edits)
├── styles.css               All CSS: tokens, layout, components, responsive
├── content.js               EDITABLE CONTENT: features, advantages and FAQ (PT and EN)
├── i18n.js                  Fixed texts in PT/EN and the language switch
├── main.js                  Starfield, FAQ accordion, scroll reveal
├── policy-privacy.html      Privacy policy (PT and EN)
├── terms-of-use.html        Terms of use (PT and EN)
├── netlify.toml             Pretty URLs and redirects
├── sitemap.xml · robots.txt SEO
├── app-ads.txt              AdMob authorization file
├── google37d8…f923.html     Google Search Console verification
├── banner.png               1200×630 image for Open Graph (WhatsApp, LinkedIn, X)
├── app-screenshot.png       Screenshot shown in the phone mockup
├── favicon.ico · apple-touch-icon.png
└── docs/logo.png            Logo used by this README

Run locally

There is nothing to install. Open index.html in a browser, or serve the folder to test the language detection and the pretty URLs:

python -m http.server 8000
# then open http://localhost:8000

The pretty URLs (/policy-privacy, /terms-of-use) and the form redirects only work on Netlify, or with npx netlify dev.

Editing the content

Everything dynamic is in content.js. Edit both languages (pt and en) and keep the same order.

// Add a feature (siteContent.features.pt and the same item in .en)
{ icon: "🗓️", title: "New feature", desc: "What it does." },

// Add a FAQ entry (siteContent.faq.pt and .en)
{ q: "Question?", a: "Answer." },

// Highlight card (dark background)
{ icon: "🔥", title: "Highlight", desc: "Text.", highlight: true },

To remove an item, delete the whole object from { to }, in both languages.

Internationalization

i18n.js holds the fixed texts (section titles, buttons, footer). The dynamic content comes from content.js, in one array per language.

  1. Use the language saved in localStorage, if any.
  2. Otherwise read navigator.language: Portuguese browsers get PT-BR, everything else gets EN.
  3. Clicking PT or EN in the header saves the choice.

The base HTML is in Portuguese (the main audience), so crawlers and AI models that do not run JavaScript read the right content. The switch to English happens in the browser after load.

SEO and AI readability

index.html has three JSON-LD (Schema.org) blocks:

Type Purpose
SoftwareApplication Describes the app to Google: category, operating system, features and price
FAQPage Lets the FAQ appear as rich results and be quoted by AI assistants
Organization Links the site to the Play Store as the official source

It also sets canonical and hreflang links, Open Graph and Twitter cards, a sitemap and robots.txt.

Deploy (Netlify)

There is no build step: Netlify publishes the repository root.

  1. In Netlify, choose Add new site → Import an existing project and connect this repository.
  2. Leave the build command empty and set the publish directory to ..
  3. Every push to the default branch is published automatically.

netlify.toml defines the URLs the app relies on, so do not rename them:

URL Target
/policy-privacy policy-privacy.html (opened from the app's profile screen)
/terms-of-use terms-of-use.html
/bug-report-form · /feedback-form Google Forms
/download Google Play listing
/about This repository

Tech

HTML5 Semantic structure
CSS3 Grid, Flexbox, animations and custom properties
JavaScript (ES6+) i18n, dynamic rendering and interactions
Google Fonts Alexandria
Netlify Hosting
Schema.org JSON-LD Structured data

Built with AI assistance

Part of this site was developed with the help of AI tools. The approach and the process are described in this post.

Related projects

  • DatePlan: the mobile app (Kotlin Multiplatform)
  • DatePlan-API: the backend (Spring Boot, PostgreSQL, Redis)

Contributing

Fixes and translations are welcome: open an issue or a pull request. For anything related to the privacy policy or the terms of use, open an issue first. Please do not include personal data.

License

Source code is source-available under the PolyForm Noncommercial License 1.0.0: you can read, study, modify and use it for noncommercial purposes. Commercial use requires written permission from the author. The name "DatePlan", the logo, the images and the privacy policy and terms of use are not covered by this license; do not reuse them for another product.

Created by Mayck Gomes.

About

A web experience for DatePlan, helping couples manage events, reminders, and special moments.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages