Brand Name Generator

A tool for finding a brand name. It builds combinations from two parts (a main word plus a second word or an ending) and checks whether the domains are available in the zones you choose.

Everything runs in the browser, with no backend. The source works as is, with no build step; an optional build packs it into one file that opens straight from disk.

Features

• Two word lists with add, hide and delete, plus a random word generator
• Readable joining of endings: Nova + -io = Novio, Fast + -tron = Fastron
• Domain availability check for any zones, each marked as required or optional
• Favorites, manual hiding with undo, grouping, search and filters
• English and Russian interface, light and dark themes

Project structure

index.html                  page markup
css/styles.css              styles, light and dark themes
js/theme-init.js            applies the saved theme before the page renders
js/main.js                  entry point
js/app.js                   App: state and wiring between the parts
js/core/                    Storage, AppState, I18n, DOM helpers
js/domain/                  NameBuilder, WordGenerator, ZoneRules, DomainChecker, SearchQuery
js/ui/                      WordPanel, ZonesPanel, ResultsView, ComboCard, FavoritesView,
                            Autosave, Backup, Toast, Dropdown, theme/language/columns switchers
locales/*.json              interface translations
icons/sprite.svg            interface icons (SVG sprite)
icons/flags/*.svg           language flags
icons/favicon.svg, *.png    favicon, home screen icons and the social preview image
site.webmanifest            web app manifest

The code is plain JavaScript split into ES modules, one class per responsibility. domain/ has no DOM access and holds the naming and domain rules; ui/ renders the interface and calls back into App.

Standalone file

To get a single page that opens straight from disk, with no server:

npm install
npm run build

This writes dist/index.html with styles, scripts, icons, flags and translations inlined. Double-click it, or copy it anywhere. Rebuild after changing the source.

Running locally

The scripts are ES modules, and translations and icons live in separate files; browsers don't load any of these for a page opened straight from disk. Serve the folder over HTTP instead:

python3 -m http.server 8000

Then open http://localhost:8000.

Code style

Formatting is handled by Prettier and readability rules by ESLint: braces on every if/for, one statement per line, no nested ternaries, blank lines between logical blocks. After npm install:

npm run format   # fix formatting
npm run lint     # check the rules

Data

Everything is stored in the browser (localStorage) and stays on your device. The site has no server, so this is the working storage.

The backup file (Settings → Backup, or autosave in Chrome, Edge and Opera) is for moving data to another browser or computer. It holds:

• data: words of both parts, hidden words, favorites, hidden combinations, check results;
• settings that shape the result: domain zones, readable endings, reverse order.

View preferences (theme, language, columns, open tab, list toggles) depend on the device, so they stay in the browser and are neither exported nor imported. Older backups still import; their view preferences are ignored. In Chrome, Edge and Opera you can also turn on autosave to a file. Data files (data.json) are excluded from the repository.

Domain check

Availability is detected via DNS (Google Public DNS): a domain with no DNS records is almost certainly available. It is a fast and reliable sign but not a guarantee, so confirm with a registrar before buying.

Adding a language

1. Copy locales/en.json to locales/<code>.json and translate the values. The keys are the source strings of the interface, so leave them as they are.
2. Add the language to the LANGS list in index.html: its code, full name and flag.

License

MIT © 2026 digikid