From 06ec45e9966356cb2c54d2842133dd6af02b0664 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 22 Sep 2026 09:36:01 +0000 Subject: [PATCH] Tighten the "New article" paragraph of the #3 teaser 615 characters to 576. The BAPI's twenty years become an adjective rather than a clause, and the correction the article is built on - those are not three programming models, they are three ABAP statements - loses its "because" and stands as the dash it always was. Both were nearly cut in the draft this came from. They are what the paragraph is for: without the twenty years the three are a list of techniques rather than of decades, and without the last clause the post says a screen ran three times but not why that is possible. #abap2UI5 joins the tags. One post of forty carries it today (#2, with #abapGit); the other 39 are #ABAP #SAP #UI5. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_0182AiPodwfGRKPNZG9D5epe --- blog/teaser-posts.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/blog/teaser-posts.md b/blog/teaser-posts.md index c5abef85..2a09d483 100644 --- a/blog/teaser-posts.md +++ b/blog/teaser-posts.md @@ -76,7 +76,7 @@ says the whole thing on its own. ## One Class, No Programming Model Plain text — LinkedIn renders no markdown. The article link comes from the -attached article preview, so the post carries no inline URL. 615 characters, +attached article preview, so the post carries no inline URL. 576 characters, and the first line is 56 of them: the claim on its own, above LinkedIn's fold. @@ -87,13 +87,13 @@ fold. > no binding, no annotations, nothing to transport but the class. > > New article 🎉 The same edit screen three times: through a RAP business -> object, straight to a database table, and against a BAPI that has been -> running in production for twenty years. One unchanged UI class — because -> those are not three programming models, they are three ABAP statements. +> object, straight to a database table, and against a twenty-year-old BAPI. +> All of it with one unchanged UI class — not three programming models, three +> ABAP statements. > > What would sit behind your screen? > -> #ABAP #SAP #UI5 +> #ABAP #SAP #UI5 #abap2UI5 ## No Annotation in Between