From d0601f06c080a8eb8d781fdd0e3338cd7ed42690 Mon Sep 17 00:00:00 2001 From: grm Date: Thu, 17 Sep 2026 16:42:15 +0300 Subject: Add post summaries, featured images and a page outro MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Recreating gizmolab.net as a blog showed three things the design system could not express, all of them ordinary blog features: - Listings can show a summary and a "Read more" link instead of the whole post (theme.list_style). The summary is the source up to ; without the marker a Markdown post is cut at a block boundary after 70 words (never inside a code fence) and an HTML post is shown whole, since cutting hand-written markup blind would leave tags open. Computed at render time (Post.Excerpt/HasMore), nothing new is stored. - A post can carry a featured image (posts.image, a library file that is unset when the file is deleted): a thumbnail floated beside the entry on listings, and on the post page above or below the text, or not at all, as theme.post_image says. The picker is the design page's imagepick; its library panel moves out of design.html into partials/imagelib.html so both forms share it — which also removes a stale pickAction call the design form's click handler would have hit. - A page can have a closing text after its posts (pages.outro_md/html), in the intro's format: the per-page counterpart of the blog-wide "after the posts" module, for a home page that ends in a site map or a widget. The editor partial takes formatof to share another editor's Format row, and its upload field is now _file so two editors fit in one form. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Sd8UPWrvyYCLj97JexNw3A --- internal/web/summary.go | 62 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 internal/web/summary.go (limited to 'internal/web/summary.go') diff --git a/internal/web/summary.go b/internal/web/summary.go new file mode 100644 index 0000000..bc48e94 --- /dev/null +++ b/internal/web/summary.go @@ -0,0 +1,62 @@ +package web + +import ( + "strings" + + "github.com/gramanas/blogspace/internal/store" +) + +// Listings can show a summary of each post instead of the whole thing +// (theme.list_style). The blogger marks where the summary ends with +// in the source; without the marker a Markdown post is cut after +// its first summaryWords words, at a block boundary, and an HTML post is shown +// whole (cutting hand-written markup blind would leave tags open). + +const ( + moreMarker = "" + summaryWords = 70 +) + +// fillExcerpts sets what the list shows of each post: the summary when the +// theme asks for one, the whole body otherwise. +func fillExcerpts(theme Theme, posts []store.Post) { + for i := range posts { + p := &posts[i] + p.Excerpt, p.HasMore = p.BodyHTML, false + if theme.ListStyle == "summary" { + p.Excerpt, p.HasMore = postSummary(p) + } + } +} + +// postSummary renders the part of the post a listing shows, and says whether +// there is more to read. +func postSummary(p *store.Post) (string, bool) { + if before, _, ok := strings.Cut(p.BodyMD, moreMarker); ok { + return renderBody(p.Format, before), true + } + if p.Format == store.FormatHTML { + return p.BodyHTML, false + } + head, cut := leadingBlocks(p.BodyMD, summaryWords) + if !cut { + return p.BodyHTML, false + } + return renderBody(p.Format, head), true +} + +// leadingBlocks returns the blank-line separated blocks from the start of the +// Markdown up to the first that brings the word count to n, and whether +// anything was left out. A fenced code block is never cut in two. +func leadingBlocks(md string, n int) (string, bool) { + blocks := strings.Split(md, "\n\n") + words, fences := 0, 0 + for i, b := range blocks { + words += len(strings.Fields(b)) + fences += strings.Count(b, "```") + if words >= n && fences%2 == 0 { + return strings.Join(blocks[:i+1], "\n\n"), i+1 < len(blocks) + } + } + return md, false +} -- cgit v1.2.3