chore: prepare migration to TOON format repo

[johannschopplich]

Hi there, @mattt!

I'd love to migrate your repo to the TOON format umrella org. For all TOON implementations, I have a similar structure in mind to make contributing easy. That's what this PR is – align TOONEncoder with Official TOON Format Standards.

This standardization ensures consistency across the TOON ecosystem while maintaining the documentation and examples you've created.

Is that ok for you? I'd prefer to merge first and immediately afterwards move the repo. How does that sound to you?

[johannschopplich]

After moving, I will rename to toon-swift and I'd welcome if the package could be renamed to ToonFormat in the future, so decoder functionality can also be implemented in the same package.

[mattt]

Sounds great! Thanks for bringing this into the fold. Merging this now.

Tip

You can set up default contributing guidelines at the org level by creating a public .github repo.

After moving, I will rename to toon-swift and I'd welcome if the package could be renamed to ToonFormat in the future, so decoder functionality can also be implemented in the same package.

Absolutely — let's plan to change the library target exported by the package to be named ToonFormat in a follow-up PR.

[mattt]

@johannschopplich IIRC, I'll temporarily need create repo permissions to do a transfer. Lemme know when you grant that to me and I'll kick that off.

[johannschopplich]

@mattt You're right. Can you please try again? I've added the permission for team members to create repos, so you should be good to go for the migration path.

[johannschopplich]

You can set up default contributing guidelines at the org level by creating a public .github repo.

Thanks! I wasn't aware of that. Then I can clean up the other repos. Thanks!

[mattt]

@johannschopplich We're live! Thanks again for your help.

I just opened #5 to follow up on #4 (comment)