Take Your Journey Beyond Alongly

After we shared the Journey Passport, a few of you asked the same thing: can I put my Journey on my own website? It was a fair question. You can document a project on Alongly for months, but the record stays inside the app, and anyone who wants to see it has to come to us.

Now they don't. You can embed your Journey on your website, or export it as a file you keep.

Your portfolio shows the result. Your Journey shows how you got there.

A typical project page shows the destination: the product, the design, the launch. It is the finished piece, selected and polished. What it cannot show is the work behind it: the iterations, the things that changed, the milestones that marked real progress.

That is exactly what a Journey already holds. Until now, it only lived inside Alongly. In our Journey Passport post we said an embeddable version was on the roadmap. This is the first piece of it: your Journey's timeline, on your own page.

Embed: put the full story on your own site

Here is a real Journey, embedded exactly the way you would embed yours. Scroll it. Open the updates. This is what a visitor to your site would see.

A live embed of the “In Public” Journey. Nothing on this page was copied or re-created.

It shows your text updates, images, videos, and milestones in chronological order. It is read-only, works at any screen size, and visitors never have to sign in. Because it is the same Journey you already keep, there is nothing to maintain. Post an update on Alongly, and the embed shows it the next time your page loads.

Setting it up takes about a minute

1. Open your public Journey and choose Embed on my website.
2. Preview it and pick a theme: light, dark, or auto, which follows each visitor's own setting.
3. Copy the code and paste it into any HTML page. Most site builders have an "embed" or "custom HTML" block for this.

Need it taller or shorter? Change the height value in the code you pasted. The embed does not resize itself, so set it to whatever fits your layout.

What it changes for the people who build things

• Indie founders: put your landing page and your build history in one place. A first-time visitor sees a product, and also the months of shipped releases and milestones that say it is not going away.
• Designers and developers: sit the finished work next to the decisions and iterations that shaped it. That is the part a screenshot cannot carry.
• Makers and creators: show experiments and work in progress, not only the pieces that made the final cut.
• Freelancers and consultants: give a prospective client more than a retrospective case study. A dated record of how a project actually unfolded is hard to argue with.

The value is not showing more content. It is making the work behind the result easy to inspect.

You stay in control of what shows

Only public updates appear. Anything you shared with your Crew or kept private is never included. The embed carries a small “Powered by Alongly” link, plus a “View on Alongly” link, so visitors who want to follow the project further can find the source.

Export: a copy of your story that you own

Embedding connects your ongoing Journey to your site. Export is the opposite: a copy that lives entirely outside Alongly. Every update, in order, with its original date. You choose the format:

This is useful when you want to:

• Keep your own copy. A project archive that does not depend on any single app.
• Hand someone the whole record. A client, a collaborator, an investor, a hiring manager. They open it without installing or signing up for anything.
• Document a project over time. Preserve the sequence of updates, not just the final screenshots and launch announcements.

An export is a snapshot of your Journey at the moment you download it. Keep adding updates, and export again to capture the latest version.

Which one should you use?

If you want visitors to see the project as it grows, embed. If you want a record you can keep, send, or file away, export. Many people will want both: an embed on the portfolio for the public story, and a ZIP in a drawer for the day a platform changes or a project wraps up.

Either way, you are not recreating anything. It is the same Journey you already maintain, and you never publish an update twice.

Good to know before you start

• Embedding is for public Journeys. A Journey's visibility is chosen when it is created, so to embed your story it needs to have been started as public.
• Only the creator can export a Journey.
• Embeds refresh on page load. New updates show up the next time the page is opened or reloaded.

Available now

Open a Journey in Alongly and look for Export Journey and Embed on my website.

If you already document your work on Alongly, that record can now do more than sit in an app. Keep it as an archive, or make it part of the page where you present your work.

Your Journey is no longer limited to where you create it.