Call for Contribution: Use Cases

We are opening up our Use Cases section for contributions! We’d ask you to share how you solved problems, implemented features, or improved processes using platformOS. Each use case can have a related case study on our marketing site — while the use case has a technical focus, the case study would have a business focus. If your topic is less technical, you could contribute a stand-alone case study as well.

If you write a use case, you will be displayed on it as the author, along with your contact information. This could help you demonstrate your expertise and promote your services. Besides getting kudos and being elevated in the community, other Partners might reach out to you to work on projects, helping you gain more credibility.

We help you every step of the way, so if you have an idea for a Use Case, just pitch it to us. You can send an outline, a draft, a video, and we can work on it together to turn it into a Use Case. You can also use our Use Case/Case Study Guide for inspiration.

If you have any questions, just send me a DM on Slack. We are looking forward to hearing and sharing your stories!

Documentation

Content production

• UPDATED capture variable Liquid tag - extended description based on user feedback
• IN REVIEW Article: Code Quality and Performance Best Practices for Your platformOS Site
• IN REVIEW Use case: How we solved remote docs issues
• IN PROGRESS Article: Building Our Documentation Site on Platform OS — Part 4: Implementation
• PLANNED Add documentation about handling multiple attachments
• PLANNED Update documentation for user profile
• PLANNED Describe what variables are available at each stage of processing form configuration
• PLANNED Cross-link sessions reference to Updating Instance configuration

Improvements, fixes

• PLANNED Adjust design to mobile devices
• PLANNED Update platform-os.com -> platformos.com
• PLANNED Allow links in auto-generated docs

UX

Research

• Onboarding strategy: This is an ongoing research where we are gathering experiences from new pOS users and also from experienced pOS users to be able to optimize the adaptation of platformOS. We’d like to learn from your experiences: what helped you understand pOS and the related processes, what caused you problems or difficulties. If you’d like to share your experience in a short five question interview reach out to @Kata in Slack.
  

Design and Development

• IN PROGRESS  Notification emails after module usage: Email templates for the end of module unsubscription period. Related to this we modify the screens of the create and edit module screens.
• IN PROGRESS Template for module resources: A template will be implemented on the create module page resources section (previously Description, Documentation, and Support)
• IN PROGRESS Edit screen for module versions: through this screen users can edit version numbers and release notes
• IN PROGRESS Semi-automated payment functionality for modules under subscription
• IN PROGRESS Notification emails related to module payment
• PLANNED Show versions and release notes on the module detail page

Improvements, fixes

• IN PROGRESS Upfront payment: adjusting screens
• IN PROGRESS Hide Install / Uninstall / Update buttons on module list when there is an action in progress