Help us win the Best Overall Developer Portal award
Public voting for the DevPortalAwards has started. To vote, please enter your email address, then click on the link you received, select platformOS Developer Portal from the list and submit your vote. We'd be very grateful to all who feel we earned your vote. Thank you to everyone who already voted!
VOTE
Documentation
Onboarding
Based on our onboarding strategy, we outlined the user journeys and related documentation needs for our three main target audience segments:
- Non-technical: Non-technical users, like Agency Owners, PMs or Business Analysts will go through the 1-click instance creation scenario and then install the blog module with 1 more click. This will result in them seeing a fully functional platformOS site with a layout, some basic design, a blog, and a Get Started article on their blog that describes how to add and edit blog posts. They will have all documentation available as simple instructions on the same UI, and they will also have a demo video.
- Semi-technical: The journey of users who are a bit more technical still doesn’t require much coding. They start with the same 1-click instance installation, but then can pull a platformOS site from a GitHub repository and then use the instance they created as a sandbox. They will have the documentation available on the same UI, but this is a bit longer and more complex, so we are planning to display it in a way that they can see the steps of the process as a whole and then explore each step in more detail.
- Technical: The third journey is that of the experienced developer, who will get into coding his own blog module based on our detailed Get Started Guide. We chose this scenario because it is a deeper exploration of the first scenario, where the same blog module is installed without any coding, so they can already check what the result will be there.
Content production
- NEW Roadmap: We updated the look of our Roadmap to make it easier to see what has already been implemented, and outlined our plans for the second half of 2019.
- NEW License and Attributions
- UPDATED Renaming: Customizations have been renamed to Models, and we have updated the documentation to reflect this change in all topics and examples.
- UPDATED Using the GeoJSON format for Geolocation: shows how to use Models instead of CustomAttribute
- REMOVED Custom Attributes
Improvements, fixes
UX
Research
- Onboarding strategy: Iterated on the onboarding flows for the pOS personas based on internal feedback rounds. And as you can read above under the Documentation section of this report, we worked out three flows for the different target audiences.
Design and Development
- NEW Partner Portal has an updated URL https://partners.platformos.com/
- NEW replace `people` with `users`
- NEW Validate Model belongs to the defined ModelSchema - when defining a FormConfiguration with a concrete ModelSchema name as a resource, it will not be possible to use it to update the Model, which belongs to the different ModelSchema
- NEW Multilingual notifications - added `locale` attribute to Email/SMS/API Notifications, which accepts liquid, to evaluate to the locale which should be used for translations
- NEW Allow users to access their custom request headers via context.headers
- IN REVIEW Data import: batch import performance improvements
- IN REVIEW Token per Instance instead of one global token
- IN PROGRESS Partner Portal redesign: We kicked of the redesign process last week. With this effort we’d like to achieve a unified brand experience on all platformOS-related sites. As we will continuously optimize the site, the goal is to build a component library with key building blocks of the Partner Portal. We imagined that this will result in Design Systems which enable teams to build a better product faster through a reusable and consistent design. This reusability will make scaling possible. This main approach can help the portal to be a comprehensive, easy to use resource with a clean look and feel. This is a long-term process with continuous updates on the site.
- IN PROGRESS Implementation of the new look and content of the pOS Instance Welcome Page
- IN PROGRESS New look and content was iterated for the pOS 1-click demo Instance creator page
- IN PROGRESS whitelist auth0 key in integrations
- IN PROGRESS Research possibility of scoping resources ID per Instance, instead of having global ID
Improvements, fixes
- NEW Improved notifications: pOS icon and better text separation
Release Notes
To learn more about the most recent changes, improvements and fixes in platformOS, check out our latest release note: August 5, 2019 — headers in context.headers, customizations to models renaming, bugfixes
