Notes from the work, while it is happening.

Getting your screenshots ready before launch week

A lot of makers spend weeks on the product and about ten minutes on the screenshots. Then the screenshots are the first thing a visitor sees on a launch page. This week I wrote down what I'd check before submitting anywhere.

1. Show the product doing its main job

The first image should show the one thing your product does best, with real looking data in it. An empty dashboard or a login screen tells people nothing.

2. One idea per image

If a screenshot needs a paragraph to explain it, it is trying to show too much. Crop it down to the part that matters and add a short caption.

3. Keep the text readable on a phone

Many people will open your launch page on a small screen. Zoom your browser out before you take the shot, or crop tighter, so the text in the image can still be read.

4. Remove anything private

Check for real customer names, emails, API keys and internal notes. It is easy to miss a browser tab or a notification in the corner.

5. Use the same size and style for all of them

Pick one width and one browser window style and stick to it. A set of images that match looks more finished than a mix of sizes.

6. Put them in order

Think of the images as a short story. First the main result, then how you get there, then one or two extra features. Leave settings pages for last or skip them.

7. Write the alt text

Add a short, plain description to each image. It helps people using screen readers and gives search engines a little more context.

A quick test before you submit

Show your first screenshot to a friend for five seconds and ask what the product does. If they can't say, change the image before you change anything else.

If you have a launch page you're proud of, tell me what you did with your images. I'm collecting good examples.

What makers ask before they submit a product

This week I paid attention to the questions makers ask before they submit to a launch site. The same few came up again and again, so I'm writing them down here.

1. "Is it really free?"

Yes. Submitting to PeekLaunch is free. Each week has 25 free launch spots. If you want to launch in a specific week without waiting, there's an optional one-time Premium plan, but the normal listing doesn't need a card.

2. "How long until it goes live?"

Products get a quick review and then go on a weekly launch board. If that week's free spots are full, you're placed in the next open week. Makers want a clear timeline, so I want to make this more visible on the site.

3. "Will I get a real page?"

Every product gets its own permanent page with its description, upvotes, and comments. That page stays up after launch week, which helps people find it later.

4. "What should I write?"

Most people struggle with the tagline. My advice: say who it's for and what it does in under 60 characters. Skip buzzwords.

What I'm working on next

• Clearer "what happens after you submit" info

• Better category pages so products are easier to browse

• Small improvements to the review flow

If you've launched something recently, I'd love to hear what confused you most on other launch sites. It helps me fix the same things here.

When words are difficult to find, a starting point can help.

I’m Viorel, founder of Eternal Memories. Our free remembrance-text collection has examples for family members, friends and colleagues. You can read them without an account and adapt them with your own memories and details:

https://eternalmemories.online/en/remembrance-texts?utm_source=indielogs&utm_medium=social&utm_campaign=families_202610

The collection is available in English, Romanian, French and Chinese. It is a writing resource, not counselling.

For families who want a shared place for life stories, photographs and memories, Eternal Memories also offers online memorials: the first year is free, no payment card needed; continuation after that is optional and paid.

I’d welcome feedback on whether the examples are clear and easy to adapt. Please avoid sharing private family information in public comments.

Multify gives users the freedom to choose the AI models that best fit their tasks. Alongside Claude and ChatGPT, the platform supports models such as Gemini, Grok, and Llama, plus more than 100 additional options through OpenRouter. Users can bring their own API keys and combine model flexibility with task boards, AI agents, MCP integrations, and workflow automation in one free productivity environment. Beyond generating responses, Multify helps coordinate work across applications and projects. Agents can use connected tools, work with shared files in ClawBox, and reference saved knowledge in Stash. Scheduled runbooks can organize multi-step processes, while compatible MCP clients provide additional ways to continue work beyond Multify. This adaptable approach helps users select models based on the task at hand, connect existing software, and build workflows without becoming dependent on one AI provider.

Where Winds Meet Calculator is a web companion toolkit for Where Winds Meet players who want measured numbers for their damage output instead of estimates. It serves players tuning gear and builds for endgame content, PvP players comparing stat priorities, and explorers tracking locations and collectibles.

## The problem

Working out whether a build is actually finished means totalling skill damage across a full rotation, dividing by rotation time, and comparing the result against an ideal endgame reference. Done by hand, that involves copying panel attributes into community spreadsheets, repeating the math for every gear swap, and still not knowing which affix to upgrade next. Location hunting adds a second layer of manual work, since in-game points of interest are spread across eight regions.

## How the product addresses it

Where Winds Meet Calculator runs the rotation simulation for you and reports the outcome in a readable form:

- Rotation-based DPS simulation for all 8 builds: Bellstrike-Umbra, Bellstrike-Splendor, Silkbind-Jade, Bamboocut-Dust, Bamboocut-Kite, Bamboocut-Wind, Stonesplit-Might and Stonesplit-Scale, covering burst, sustained, control and mobility playstyles

- Graduation rate scoring, calculated as your DPS divided by the baseline DPS of the ideal endgame build for that playstyle, so 100% means graduated and above 100% means you have passed the baseline

- Per-skill damage breakdown, so you can see where output actually comes from

- Affix priority recommendations based on marginal gains, which adjust as your stats change and point to the stat that returns the most next

- A gear calculator for organizing equipment, plus a community section for browsing, comparing and sharing builds

- An interactive map with 8,000+ English-translated locations across 8 regions, filterable by chests, bosses, teleport points and resources, with progress checkmarks

- Written guides on PvP damage mechanics, stat priorities, skills, factions and cosmetics

Calculation formulas are extracted from official community Excel spreadsheets, with a published changelog and calculator data updated within 24 hours of each game patch. The site is free to use and runs in the browser.

## How it works

1. Pick your build from the 8 supported weapon-line options.

2. Enter your panel attributes, including attack, critical rate and critical damage, penetration, defense and damage bonuses.

3. Read the output: DPS, graduation rate against the endgame baseline, and the damage breakdown by skill.

4. Check the affix priority suggestions to decide which stat to upgrade next, then re-run after a gear change to see the effect.

5. Use the interactive map and guides alongside the calculator to track locations and read up on mechanics.

## Use cases and who it suits

- Simulating rotation DPS for a chosen build and reading the skill-by-skill breakdown

- Checking graduation rate against the ideal endgame baseline for a playstyle

- Deciding the next affix upgrade from marginal-gain recommendations

- Locating chests, world bosses, teleport points and resources across the 8 regions

It fits solo players optimizing a main build, PvP players weighing stat trade-offs, completionists working through map content, and guilds or communities that want a shared reference for build comparison.

How Web Developers Can Ship Side Projects Faster on Weekends

Weekend side projects fail in the same way every time: Friday night is full of energy, Sunday night is full of half-finished repos. Here is how web developers can ship side projects faster without quitting their day job.

Protect a tiny scope

Before you open the editor, write one sentence: "By Sunday night, a stranger can do X."

X should be one action. Create a note. Upload a file. Generate a link. If your sentence has "and," cut it. Scope is the only lever that reliably buys speed.

Use a fixed weekend shape

A shape that works for many builders:

• Friday (45–60 min): pick the one user action, sketch two screens on paper, create the empty repo and deploy stub

• Saturday morning: auth + empty database record for that action

• Saturday afternoon: the happy path UI end to end

• Sunday morning: polish copy, empty states, and mobile

• Sunday afternoon: deploy, share with five people, write down the feedback

Stop when the clock says stop. Shipping a thin version beats another "almost."

Steal time with defaults

Decide these once and reuse them on every project:

• One framework you already know

• One host for previews

• One database style

• One component approach (even plain HTML is fine)

Decision fatigue eats weekends. Defaults give the hours back to the product.

Cut ceremony

Skip for v0:

• Perfect design system

• Custom auth flows

• Marketing site with five pages

• Automated everything

Add tests and polish after someone outside your head uses it. Until then, manual clicks and a simple README are enough.

Ship to humans, not to your future self

"Done" means someone else can open a URL and try the main action. A private branch is not shipped. A localhost demo is not shipped. Put it on a public URL, even if the design is plain.

Then ask three questions:

1. Did you understand what it does in 10 seconds?

2. Where did you get stuck?

3. Would you try it again next week?

Those answers set next weekend's scope better than any roadmap doc.

Keep a short public log

A few honest lines after each weekend ("shipped signup + create note; still broken on mobile Safari") keep momentum. Future you — and people who might help — can see progress without a long thread.

One-week rule of thumb

If you cannot reach a stranger-usable URL in two weekends, the idea is too big or the stack is too heavy. Shrink the action, keep the learning, and try again. Speed comes from smaller bets, not longer nights.

Ship the thin thing. Talk to people. Build the next thin thing. That rhythm is how side projects leave the laptop.

MAN Digital believes effective automation begins with clear processes rather than technology alone. As a HubSpot Elite revenue workflow partner, the company helps B2B teams establish trusted data, define workflow rules, clarify ownership, improve reporting, and connect the systems that support revenue operations. Once the operating model is reliable, MAN Digital can introduce programmable automation, custom HubSpot applications, and governed AI agents. Its work covers pipeline creation, revenue conversion, quote-to-cash, customer retention, and expansion, helping businesses automate with a clearer understanding of how their workflows should function.