Skip to content

Remove the names of client sites and internal tools from the public files - #3

Merged
HosseinKarami merged 1 commit into
mainfrom
docs/neutral-names
Nov 1, 2026
Merged

HosseinKarami merged 1 commit into
mainfrom
docs/neutral-names

Conversation

@HosseinKarami

Copy link
Copy Markdown
Member

Summary

This repository is public, so it must not name client sites or internal tools. Four files did. This change gives them neutral labels.

  • FORMS.md: the audits are "of refact.co and of two client sites". The status table of section 4 keeps only refact.co, the site of the company. The status of each client site is now in forms-status.md, in the results folder of the repository of that site. Section 5 points to the same file.
  • CHANGELOG.md: the 1.1.1 entry says "a large WordPress news site".
  • STAGE-7.md: the install test says "another site, a headless WordPress site of 740 pages".
  • PLAN.md: the product has "no dependency on other internal tools".

There is no code change and no version change.

Check

A search of all files for the names of the client sites, their domains, their staging hosts and tools, and the internal tool gives no match. The only remaining hit is the generic CAPTCHA test in src/own/page.ts, which detects any CAPTCHA widget.

The git history is not changed, by decision.

…iles

The repository is public. FORMS.md, CHANGELOG.md, STAGE-7.md, and PLAN.md
named two client sites and an internal tool. They now use neutral labels,
for example "a large WordPress news site". The status of each client site
moved to the repository of that site.
@HosseinKarami
HosseinKarami merged commit 555405a into main Nov 1, 2026
1 check passed
@HosseinKarami
HosseinKarami deleted the docs/neutral-names branch November 1, 2026 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant