Clark Conrad Pesa

Clark Conrad Pesa

I'm a Growth Marketer at SGEN,

About

I’m a Growth Marketer interested in how products grow, how teams build better digital experiences, and how technology can simplify the work behind them. I spend a lot of time exploring SaaS, websites, product marketing, customer problems, and the systems teams use to manage and scale their digital presence. I enjoy learning from builders, makers, and other people working in tech, especially through real-world experiences, product discussions, and community conversations. Always curious about what people are building, what problems they’re solving, and what actually works in practice.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Forums

W40 Product Update: Localization in the tools you already use

You can now connect content sources to your localization engines in Studio, translate content with your team's glossary, rules, and brand voice, and write translations back to your repositories, CMSs, or help centers.

Connect GitHub, Payload CMS, or Zendesk Help Center, or submit content through the CLI and API. Each source uses the localization engine you choose, with your team's glossary, rules, and brand voice. Product and content teams submit content from their own tools, while the localization team runs the localization infrastructure.

The CLI. Engineers use lingo push to submit source files through the localization engine's configured pipeline. lingo pull writes the completed translations to local target files on the same machine and checkout. Studio lists each submission with its status by language.

The GitHub App. When source files change on the default branch, the app translates the changes and opens a pull request with the translated files. Enable the pull request workflow to commit translations directly to a pull request branch. Require approval before automatic runs, or use /lingo translate to request specific files and languages.

•

1mo ago

How do you handle website feedback from clients?

I'm curious how other makers, designers, developers, and agencies handle website feedback.

When you're working with a client, how do you handle comments like:

"Move this button slightly to the left."

"This section doesn't look right on mobile."

Has anyone actually consolidated their website stack? What happened?

One thing I've noticed with websites is that the stack can grow pretty quickly.

You start with a CMS and hosting, then add plugins, analytics, SEO tools, forms, backups, security, integrations, and other tools as you need them.

View more