Over the next couple of weeks, from late August through early September, the Digital Experience team will be making key structural updates to the JMP Community architecture. This initiative focuses on streamlining the JMP content ecosystem, improving user navigation, and consolidating our blogging platforms into a single, cohesive experience.
Streamlining the blog ecosystem
To create a more unified voice and make content discovery easier, the team is consolidating current blogging channels into a single destination: the JMPer Cable blog. By bringing writing under one umbrella, external visitors will no longer need to jump between multiple feeds to find high-quality insights, stories, and updates.
Alongside the blog consolidation, the team is simplifying how technical knowledge is stored and accessed. Support notes, technical resources, and learning resources will merge into a centralized library, giving users a clean, one-stop repository for troubleshooting, skill-building, and product documentation.
Navigational enhancements
To support these content updates, the site’s main menu is receiving a targeted refresh. The navigation will feature the new “Library” section alongside “Groups,” moving it from the Community menu for better visibility. To keep the menu clean and intuitive, the redundant "JMP" branding will be removed from individual section names; for instance, the "JMP Wish List" will become the "Wish List."
This is a preliminary look at what the navigation may look like.
What does this mean for you?
If you regularly contribute to our external blogs, your primary publishing destination will soon shift exclusively to the JMPer Cable framework. Because all existing content will be automatically redirected, your portfolio of past work remains completely intact and accessible. The Digital Experience team is managing the entire migration and menu rollout to minimize any disruption to your workflow.
If you have any questions about how these changes might impact your upcoming scheduled posts, please reach out directly to Digital Experience Manager Ryan Gilmore (@Ryan_Gilmore) for guidance.
