Previews from the publisher
Turn a real community, culture or event story into a paper-zine presentation with thesis pages, cases, process and a clear invitation. Red Black Zine Deck rotates cream newsprint, black ink and poster-red surfaces around serif headlines, typewriter copy and taped photographs. It favors source-backed stories and permitted real photos; generated documentary-looking scenes must never be presented as records of an event.
Treat the zine as an edited argument with a traceable record, not an excuse to invent documentary material. Tie every number, case and photo caption to an actual source; remove unsupported sections. Use the paper/black/red rhythm to pace that argument, and flag missing photos instead of letting scrapbook decoration conceal them.
/red-black-zine-deck Create a red-black culture-zine presentation from my topic and outline as one self-contained HTML file, with full 16:9 slides, cream newsprint, black and red spreads, two-tone serif titles and torn-and-taped photo frames. Include page navigation, a thumbnail overview, speaker notes and print-to-PDF export.Provide the outline, audience, story, intended action and available real photos, verified survey figures, named cases or rollout plan. Agree the count; six to ten is only a starting proposal if unspecified. Copy defaults to English unless another language is requested. Remove a stats/case slide when evidence is missing rather than inventing numbers or names.
Plan one archetype and surface per page, using the nearest kit recipe and adapting absent arrangements. Begin on cream, reserve red for strong beats/closing and do not run three identical surfaces consecutively. Keep thesis lists to roughly two to four items, full-bleed beats to three to six and fact clusters to four clear cards when that layout is used. Do not force every archetype into a short story.
Update the wordmark, permitted logomark, domain/handle and issue/date labels while retaining the locked ink/paper/red identity. Use automatic title/tab contrast rules instead of hardcoded dark-on-dark colors. Keep photo/notes cream on every surface; use inline SVG line-art doodles, not emoji. Shorten visible paragraphs to one or two sentences and put actual talking points—not duplicated slide text—in notes.
Prioritize permitted real photos, then suitable library reuse, generation for gaps or all-new illustration; label the chosen route. The three catalog scenes suit self-publishing/collage/fairs, not unrelated event evidence. Use each pictorial source once. For restyling, preserve factual identities/context and permission; generated scenes remain illustrations. Keep black-and-white grain/contrast consistent and enough central subject/headroom for taped or torn crops.
Plan each picture at kit slot ratios with prompt/subject/result records. Use supported built-in generation or the FAL helper/FAL_KEY with separate charges and approval for paid work; submit once then poll/fetch rather than automatically replacing failures. Keep source/prompt text, credentials and provider records out of delivered HTML. Explicitly list missing frames; a photo-led deck with empty frames is not finished.
Compose approved words, alt text, images, icons and data from recipes, removing unused nodes. Python 3 handles compose/build/static checks; optional Node helpers embed/generate imagery. Resolve unfilled-image and leftover-example reports, verify count and inline resources under 20 MB. Current output embeds photos; the old companion-folder and no-PPTX claims no longer describe the shared framework.
Inspect every page over local HTTP for three-surface rhythm, title/tab contrast, torn/tape crops, real-versus-illustrative captions, image uniqueness, marker alignment, visible folios, bounds and notes/page order. On process layouts keep torn dividers out of the list column and allow translated titles room to wrap. Shared structural checks do not replace this zine-specific visual/content review.
Test navigation, overview, notes, text/image/order/layout/color edits, undo/redo, Save/reopen and presentation mode. Deliver page-view HTML with Edit/E and Save (Cmd/Ctrl+S) instructions: browser recovery is local, Save writes portable edits. Set interface/content locales separately with framework CJK/RTL support. Use current editor controls rather than assuming retired wheel/ESC/N behavior. Export/check/inspect requested PPTX/PDF and recipient fonts separately; the embedded menu replaces the old mandatory Node/Chromium export chain.
Not for suitable supplied photos, relevant bundled assets or a clearly disclosed draft with missing frames. New images can use the available built-in route or optional FAL/FAL_KEY with separate charges and approval for paid work. Submit paid tasks once then poll/fetch. A photo-led deck with empty frames must still be flagged as unfinished.
Yes—permitted real event/venue photos are preferred for factual recaps. Apply the grainy grayscale/torn-frame treatment while preserving accurate context and identities. A generated or heavily altered scene must not be represented as documentary evidence. Keep each pictorial source on one page only and center the subject for tight frame crops.
Open the self-contained HTML in the shared page-view editor, use its navigation/overview/notes controls, or enter presentation mode. Save writes portable changes into the file. Current delivery embeds pictures instead of requiring the old images folder. Check requested PPTX or print/PDF separately. Legacy arrow/wheel/touch/ESC/N promises belong to the retired bespoke engine and are not a compatibility guarantee for current controls.
Use the count agreed from your content and presentation time. If unspecified, the style suggests six to ten as a starting plan, not a fixed requirement. Choose only archetypes supported by actual material; omit split stats without verified data or a process page without a real plan. Keep red rare and avoid three same-surface pages in a row.
Yes. Change text, pictures, notes, order, layouts and individual colors in Edit, then Save. The design palette remains deliberately locked and there is no style-theme chooser. Current embedded PPTX export keeps native text/notes and separate pictures with rendered decoration; it replaces the old mandatory Node/Chromium export chain and the outdated no-PPTX restriction. Python builds/checks the source; optional media tools use Node. Inspect fonts and actual PPTX/PDF pages before sharing.
Select a star to share your experience.
No reviews yet. Ratings appear once readers share real experiences.
+7Use this Skill to create presentation.
+7Use this Skill to create presentation.
+8Use this Skill to create presentation.
+7Use this Skill to create presentation.
+7Use this Skill to create presentation.
+8Use this Skill to create presentation.
+7Use this Skill to create presentation.
+7Use this Skill to create presentation.