Best way to manage multiple Developer Edition orgs while learning?

Hi everyone,

I'm currently focusing on learning Experience Cloud and its development aspects (Experience Builder, external users, portals, Enhanced Messaging, etc.), and I've run into a challenge with managing Salesforce orgs.

I'm not referring to Trailhead Playgrounds, since they often have limited licenses or don't always include the features I need.

Here's what I've experienced so far:

• I created a Developer Edition org for general learning, but later realized that Developer Edition doesn't support Sandboxes, so I couldn't keep a clean development environment.
• While learning Enhanced Messaging for Guest Users, I found that it requires a Developer Edition org with Enhanced Messaging enabled, so I had to create another org specifically for that.
• In some orgs, after experimenting with Experience Cloud users, licenses, and configurations, I eventually hit license limits or ended up with an org that's no longer clean for new experiments, which led me to create yet another Developer Edition org.

At this point, I have multiple Developer Edition orgs, each created for a different feature or learning scenario, and it feels difficult to manage.

My questions are:

1. Is this the normal workflow for Salesforce developers who are learning Experience Cloud?
2. Is there a better way to maintain a reusable development environment without creating a new Developer Edition org every time?
3. Are there any recommended strategies, tools, or org types that make this process easier?

I'd really appreciate hearing how others handle this while learning or building portfolio projects.

Thanks in advance!