Documentation

Content production

Last week we added lots of new content you requested. We dedicated a whole topic to explaining how User Uploads work under the hood including file size limits, and added in-depth topics on the different approaches of caching. We also added two new tutorials about integrating newsletter services (Mailchimp and ActiveCampaign).

• NEW User Uploads
• NEW Static Cache
• NEW Dynamic Page Cache
• NEW Fragment Cache
• NEW Integrating Mailchimp Using API Call Notifications
• NEW Integrating ActiveCampaign Using API Call Notifications

• UPDATED GraphQL API Reference: Objects - display reason for deprecation
• UPDATED Create Your Codebase - updated based on user requests, added more information on directory structure and sample directory structure after pos-cli init
• UPDATED Model Relations - renamed model to related_model
• IN REVIEW Update GDPR compliance topic
• PLANNED Update /users/creating-user-property
• PLANNED Explain cache in sitemap article
• PLANNED Expand gui serve document

Improvements, fixes

• FIXED Integrating Slack Using API Call Notifications - fixed example
• PLANNED Search API

UX

Design and Development

• NEW pOS Marketing site - Developers and Partners page layout and designs
• NEW pOS Newsletter style
• IN REVIEW Allow to pick algorithm for jwt token
• IN REVIEW Builder: migrate data when property type changes
• IN REVIEW Fix deploy without assets
• IN REVIEW Partner Portal Onboarding journey
• IN PROGRESS Do not include default values in pos-cli export
• IN PROGRESS Portal - api for cloning instance
• IN PROGRESS Respect full graphql query/mutation path during sync/deploy
• IN PROGRESS Split Scope for queries on large model collections
• IN PROGRESS Postgres: set timeout for queries

Improvements and Fixes

• FIXED Deploy without assets
• FIXED Liquid: match filter fix for invalid expression
• FIXED Graphql: presign url - fix for path with spaces

Development

We are delaying deployment this week to monitor a new feature and improvements on staging. Please find our release note in next week’s status report.