Extended work path
Multi-user access, customer data, cross-system sync and long-term maintenance are not problems the individual follow-along edition has to solve. Only when they arise is it worth designing and implementing separately.
You do not know which work is most worth doing first; the materials are not convenient to test on your own; multiple people need to collaborate; pilot results have been unstable; or you want to turn individual practices into a long-term team system.
First look at the work, materials and boundaries together, then decide whether more complex material organization, permissions, integrations or long-term maintenance are needed.