Skip to content

Shorten the Store readme and clean up the community listing - #79

Closed
Tiwas wants to merge 1 commit into
mainfrom
docs/store-readme-and-listing
Closed

Tiwas wants to merge 1 commit into
mainfrom
docs/store-readme-and-listing

Conversation

@Tiwas

@Tiwas Tiwas commented Oct 30, 2026

Copy link
Copy Markdown
Owner

v1.10.38 is live, and Athom approved it with one request: the Store readme had grown into a device overview, a list of standalone Flow cards and technical notes. They want a short, engaging summary in one or two plain-text paragraphs, as described in App Store Guidelines 1.3.

Changes

  • Store readme (no.tiwas.booleantoolbox/README.txt): two everyday-language paragraphs with no lists, versions, Markdown or URLs. Links stay in the App Manifest (homepage, support, bugs, source).
  • Translations: guideline 1.11 asks for the readme in the same languages as the app description, so this adds README.{no,da,sv,de,nl,fr,it,es,pl,fi}.txt. homey app publish reads them from the app folder. README.*.txt is added to .homeyignore next to README.txt, so they stay out of the bundle.
  • HOMEY_COMMUNITY_LISTING.md: v1.10.38 in both store and test. One What's new in v1.10.38 section sums up everything since the previous store version (1.10.16) and replaces the 15 per-version sections. Version tags are removed from the feature text, a Presence+ section is added, and stale v1.10.32 install links are fixed.
  • README.md: the Circadian Light Group heading no longer says stable v1.10.16.
  • Project rules: AI_RULES.md section 8 and a pointer in CLAUDE.md. The readme stays within guideline 1.3, new features are never appended on release, translations change together, and the community listing keeps a single What's new section.
  • WORKLOG.md entry.

No app code changed. The new readme reaches the Store with the next published build.

Verification

  • homey app validate --level publish passed.
  • npm run test:package: 912 files, 8.09 MB, 17 manifest assets. The file count is unchanged, so the readmes are not in the bundle.
  • All 11 readme files have two paragraphs and no URLs, Markdown markers or indentation.

Athom approved v1.10.38 but asked for a shorter Store readme: one or two
plain-text paragraphs instead of a device overview, Flow card list and
technical notes (App Store Guidelines 1.3).

- README.txt is now two everyday-language paragraphs with no lists,
  versions or URLs, translated into the ten other languages the app
  description already uses. README.*.txt stays out of the app bundle.
- HOMEY_COMMUNITY_LISTING.md reflects v1.10.38 in both store and test,
  replaces the per-version sections with one "What's new" summary since
  v1.10.16 and drops version tags from the feature descriptions.
- README.md no longer calls the store version 1.10.16.
- AI_RULES.md section 8 and CLAUDE.md record the readme rules so later
  releases do not grow the readme again.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-30T11:34:38.663857Z 5e50a8d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Tiwas

Tiwas commented Oct 30, 2026

Copy link
Copy Markdown
Owner Author

Replaced by #80. The commit message here tripped the message check, and the same changes now sit in one new commit there.

@Tiwas Tiwas closed this Oct 30, 2026
@Tiwas
Tiwas deleted the docs/store-readme-and-listing branch October 30, 2026 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant