“I’m interested in making customizations to the experience.”

This persona is can be described by others as a problem solver, analytical, and strategic.

Jobs to be done

  • As a back-end developer, I want to create, configure, customize, extend, and maintain applications.
  • As a back-end developer, I want to modify custom modules
  • As a back-end developer, I want to create custom extensions
  • As a back-end developer, I want to create custom widgets
  • As a back-end developer, I want to interact with APIs to automate or extend functionality.
  • As a back-end developer, I want to register remote repository of custom code-based components
  • As a back-end developer, I want to enable content APIs that expose CMS content
  • As a back-end developer, I want to create API tokens to automate or extend functionality for my team.
  • As a back-end developer, I want to easily export data and app code if my organization ever outgrows the current CMS solution.
  • As back-end developer, I want quick access to in-product support; help documentation, view support tickets, submit support tickets.

Decisions they must make

  • Which frameworks/languages to use to optimize speed and performance?
  • How can I build this with flexibility for the future in mind?

Pain points/Frustrations

  • “It’s not easy to undo the initial setup.”
  • Speed of data transfer
  • Lack of admin security settings by role and content.
  • Why does this break every time I apply updates.