[Docs]: Where are the docs from v8?

[juanpablob]

Which variants of Embla Carousel are you using?

• embla-carousel (Core)
• embla-carousel-react
• embla-carousel-vue
• embla-carousel-svelte
• embla-carousel-autoplay
• embla-carousel-auto-scroll
• embla-carousel-solid
• embla-carousel-auto-height
• embla-carousel-class-names
• embla-carousel-fade
• embla-carousel-docs (Documentation)
• embla-carousel-docs (Generator)

Steps to reproduce

Thanks for this lib :). I wonder where the documentation for v8 is located at? Anywhere on the website I can't find them. Everything leads to v9 rc.

Expected Behavior

I should be able to access current version's documentation.

Additional Context

I have also tried...

What browsers are you seeing the problem on?

No response

Version

v8~

CodeSandbox

No response

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues
• I agree to follow this project's Contributing Guidelines for bug reports

[davidjerleke]

@juanpablob Please move this to a discussion instead (type: question), it's not a bug. Thanks.

For now, you'll have to browse the repository history like in the screenshot below. Not optimal, but as mentioned in the "🙏 Thanks & Supporting Embla" section in the release notes (#1271):

The documentation currently uses GatsbyJS, which introduces significant development overhead and maintenance complexity. Migrating to Next.js or an alternative modern framework would streamline development and reduce friction.

It's up to the community now. Without decent sponsorship or contributions, I can't free up more time for big tasks like that.

[juanpablob]

Oh I see! thank you for your reply! :)

[modulareverything]

Since Embla v9 is in pre-release and not yet a major new release, is it a bit premature to update the docs to v9? I'm sure you have your reasons, but I can't yet update to v9 and browsing through the repo to read the v8 docs is a bit tedious. Any way you could just put the old docs on a sub-domain or something?

As always, I appreciate all your hard work on this!

[jtoliver]

Spent about 45 mins frustrated that events wasn't working only to realize I was looking at v9 doc :)

[jtoliver]

Might save someone time by adding a disclaimer / link on the Get Started page, quicker than a subdomain

[modulareverything]

Spent about 45 mins frustrated that events wasn't working only to realize I was looking at v9 doc :)

I was doing the same with draggable 😆

[olsonpm]

I appreciate the response, and this library has been helpful so far. Since people installing this will get v8 by default, and I assume gatsby is building off of master - maybe reverting the master branch to the latest stable version would be appropriate? Where v9 work can be done on a separate branch til it's stable.

Regardless, thanks for your work on this.

[davidjerleke]

I want to address the recurring comments in this thread because there seems to be a misunderstanding about how this project is maintained.

When suggestions come in like “could you put the old docs on a subdomain?”, “maybe revert master?”, or “maybe add a disclaimer?”, they implicitly assume that I have spare time or optional bandwidth to implement those things and switch context back and forth. The reality is that I don’t.

The documentation site was previously built with GatsbyJS and had become a significant maintenance burden. Migrating it to Next.js wasn’t a small tweak—it was a large piece of work. If you’re curious about the scope, you can take a look here:

• [Docs]: Migrate Docs from GatsbyJS --> NextJs #1303

That PR alone represents a substantial amount of unpaid work just to keep the project maintainable going forward.

I’m the sole maintainer of Embla. I also have a full-time job and two kids. 99.99% of the time I spend on this project is unpaid. Because of that, I have to prioritize very aggressively. Sometimes that means releasing new versions without running long RC periods, campaigns, or polishing every edge case of the ecosystem (like perfectly versioned docs).

I assume everyone here has good intentions, and I appreciate that people find the library useful. But repeated suggestions about what I could or should do aren’t particularly constructive when they come without contributions. Being thankful is polite and appreciated, but it doesn’t actually keep a project healthy.

For clarity: the documentation situation has already improved significantly with the new Next.js docs. They now support versioning:

• https://www.embla-carousel.com/docs → v9.0.0-rc01
• https://www.embla-carousel.com/docs/v8 → v8 documentation

This capability didn’t exist in the old Gatsby setup, and implementing it was part of the migration work.

If something is important to you:

• A 👍 reaction on the issue is enough to signal priority.
• A contribution (even a small one) is extremely valuable.
• Sponsorship helps create the time needed for bigger tasks.

For example, there are currently multiple issues around the React compiler. One developer spending some time investigating and gathering insights—without even fully solving the problem—would already help a lot.

Projects with a single maintainer are inherently fragile without community support. In teams with multiple maintainers, work can be distributed. Here, everything ultimately funnels through one person, and there’s a hard limit to what I can do.

I’ve been working in this industry for more than 10 years. I know how things are “done by the book”. The constraint here isn’t knowledge—it’s time.

I genuinely enjoy working on Embla and I want it to continue improving. But please keep in mind that this project doesn’t pay my bills. If you want to help make it better or faster, the best way to do that is to contribute, investigate issues, or sponsor the project.

Otherwise, please avoid asking for more than what I already put into this in my unpaid time.

[modulareverything]

Fair point. Thanks is one thing, but contribution is another.

I've created a PR for something small just to get my feet wet with it here #1308

[olsonpm]

My comment didn't assume you have time. I'm willing to create a PR with master reverted. To be clear, me suggesting that isn't assuming you have time to review it. I don't create a PR first because it's always best to get clarity on direction before creating a PR. If this is a direction you're okay with then let me know.

[davidjerleke]

Solved in:

• [Docs]: Migrate Docs from GatsbyJS --> NextJs #1303