Simplified dynamic pages, simplified schema-driven forms, loading boundaries
Simplified dynamic pages
You can now much more easily create dynamic pages in Plasmic—these are pages with URL paths like /products/[slug] and which can show data for any specific record.
When you create a new page, you can choose “Dynamic Page” and select which data source table you want to create dynamic pages for. You can even choose which field you want to use as the lookup field, such as whether you want it to be /products/[id] or /products/[slug]).
Furthermore, when editing the dynamic page, you can now easily switch to viewing a different record—no more hunting elsewhere for the right ID to paste in! (This additionally works for any existing page that already has a path parameter used in a query.)
This works with any current and future schema-aware data sources in the Integrations feature, including Postgresql and Airtable, with more to come!
Simplified and schema-driven forms
When we launched forms, we started with the ability to craft fully customized forms with arbitrary components, layouts, and behavior.
Now forms start off in “simplified mode,” which streamlines the experience of working with forms for the majority of more straightforward form building use cases. Simply configure the list of fields in the right sidebar. If and when you need more control, flip the switch to advanced mode, and all your existing fields are preserved!
A highlight of simplified forms is the new “Connect to Table” button. Just point to the table you want, and your form will get all its fields—and submitting will run the appropriate create/update operation! Plus, you’ll be able to further tweak and customize any of these default settings.
Loading boundaries
You can now insert loading boundaries, which let you gracefully show a loading spinner if anything inside the boundary depends on query data that’s still loading for the first time.
This works with the queries that you can create in the page/component data tab.
With loading boundaries you can design the exact loading indicators you want on the screen, and avoid cascading waterfalls of spinners everywhere.
(For React developers: this is similar to Suspense, and is currently restricted to client-side data fetching.)
And more
Multi-statement code expressions now work in any custom code editor.
Now when registering var(--my-custom-font) (as in Next 13 fonts), the fonts will now display with a friendlier “My Custom Font” name throughout the editor.
Left sidebar tabs now scale more gracefully when there are many imported projects.
The plasmic info CLI now supports dumping more complete project info, including authors, timestamps, and historical info in JSON format.