I would love to have access too. To see if this is the best approach moving forward for my clients. I have primarily used the Legacy Builder, is this similar to that? And does the content modelling json look similar (I'm using the PHP SDK)?
Hi Michael,
If you let me know the url for one of your repos on which you'd like to test this then I can request it from the team,
Thanks
Hi Phil. I would love access to the new Type Builder in this repo: testiltptypes
Have a nice day
Should be activated now.
Thanks. But it doesn't work. It seems that repositories created as "Other" (or not "Svelte/Nextjs") are not having the new Type Builder enabled. I tried creating a new repo with Svelte and it works there.
Also some feedback: the live previews (slice_simulator) is still there, but isn't that a Slice Machine thing? So it should be removed and just show the same thumbnail as the Slice has when selected.
Also, when adding a UID field to a custom type or page type at a later point, it sometimes got stuck until it appeared in the bottom. It's probably edge case, because you always add it first anyway 
And last thing: I really loved the JSON editor in the old Custom Type Builder, it made it really quick to start a new project (based on an older project's structure). And it made naming easier, because a slice called "Image + text" would sometimes be "image___text" etc. I would love that in the new editor too.
Today I added an Integration Field with the Prismic CLI. It works in the page builder, but now the type builder wont load the Main part of my Page type, it says "Oops! We couldn't load the static zone".
Hey Michael, thanks for testing this and for the detailed notes.
A few points on our side:
For repositories created with “Other”: historically, frameworks outside of Next, Nuxt, and Svelte were not supported by Slice Machine, so making those repositories compatible with the new Type Builder requires a bit more work than just enabling it.
For the UID field behavior and the Integration Field / static zone error, we’ll look into those bugs.
For the slice preview / slice_simulator: that’s a good suggestion. I’ve noted it.
For the JSON editor, I’d be interested in hearing more about your use case. In particular, how often do you start from an existing project structure, and what parts of the JSON editor made that workflow faster for you?
Hi Benjamin. Sure my pleasure:
I just experienced the UID bug again, I created a new Page Type, but before I saved first time is had disappeared. After I added it again, it is now in the bottom of the static zone when using the Page Builder (requiring me to use the CLI to change the json structure).
The JSON editor was my entry point for all projects. As a freelancer building around 10 Prismic sites per year, I would always start by copying a full Page template from another repo, then paste it into the JSON and start editing from there. Also relevant for a Menu template etc. It would just save me some time and make it easier to keep same field names between projects.
Hi Michael, thanks, that helps a lot.
On the UID issue: I’ve raised it internally. We have not been able to reproduce the disappearing UID yet, but the behavior you describe is not expected.
The UID should not disappear before the first save. Also, if you re-add it, it should not leave you with a broken order in the Page Builder that you then need to fix with the CLI.
One thing we identified is that UID handling is currently inconsistent across model types, so we’re looking at this more broadly, not just as a one-off ordering issue.
In the JSON editor, I understand the need better now: for you, it was mainly a fast model-reuse workflow across client projects, not just an advanced editor. I’ll bring it back to the team that way: we need to support copying/importing existing Page Type/Menu structures while preserving field names and order. Am I right?
Hi, yes that sounds right.
I tried making a new page type again, but couldn't replicate the UID field disappearing.
I hope you can make the Integration Field work in the type builder, that would be really great.
Thanks.