Skip to content

Launch post revisions: refresh screenshots, drop schedule image, copy fixes - #18

Open
yanboishere wants to merge 12 commits into
felinics:mainfrom
yanboishere:pr-14
Open

yanboishere wants to merge 12 commits into
felinics:mainfrom
yanboishere:pr-14

Conversation

@yanboishere

Copy link
Copy Markdown
Member

Summary

Revisions to the launch post "Introducing Memoh: a cloud computer for every agent" (zh & en):

  • Refresh product screenshots with up-to-date captures from app.memoh.net:
    • 02-computer.png: chat + cloud desktop split view
    • 04-files.png: Files tree view with cloud desktop
  • Remove the schedule illustration (05-schedule.png) and its caption from both language versions
  • Remove Hermes from the agent lists
  • Use english slugs for blog urls instead of dates
  • Remove the graphical-desktop and coding-required FAQs

Publish the product launch post in the Manus-style announcement format:
always-on agent computers, hosted/desktop/self-host paths, and real product screenshots.
Blog posts are not locale-switched. Publish zh and en as two markdown
files that share screenshots and link to each other.
Load posts from en/ and zh/ so the language switcher swaps article
bodies. Translate the Chinese Discuss and desktop posts to English,
and the original English intro to Chinese. Keep /blogs/2026-09-11-en
as a redirect to the canonical slug.
Rewrite overlapping desktop/closing copy, drop reused May 15 GIFs,
point to prior posts instead of restating them, and publish as
2026-09-15 with redirects from the old slug.
Drop the machine-translated copies of 2026-02-16, 2026-05-02, and
2026-05-15. Blog chrome stays locale-switched; those articles stay
in the language they were written in. The Sep 15 launch post still
has authored EN and ZH.
Rename blog markdown files and image directories to descriptive English slugs, move dates into frontmatter, sort posts by date, and keep old date-based URLs working via router redirects and slug aliases. Rewrite README with blog content conventions.
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