Skip to main content

Feature Matrix

Feature Matrix docs and general info

Last update: 20 Feb 2026

FUNCTIONAL SPECIFICATION

Use the functional spec for reference only. It is a draft, and does not capture all details of the app. It has not been updated since initial development in 2024.

IP16 Feature Matrix Functional Specification

OVERVIEW

Staff at IPI has changed hands and as of Q1 26 the current IPI engineer that is managing the content is Subhodeb Murkherjee, who has been working with Gaird Schlesinger from the vendor team at Mighty Digital.

FEATURE MATRIX USAGE QUESTIONS

Various questions and responses between Subhodeb an Gaird. As documentation is written, these will be written up in the Features List, and may be added to the FAQ section.

tip

Click on the tab headings to view each Q & A item

Q: What is the correct URL to access the admin backend?

Answer:

  1. The Feature Matrix login, and the front end, are not accessible from the base domain
  2. The URL of "https://featurematrix.ipinfusion.com/" will not display anything
  3. The correct admin login URL is: https://featurematrix.ipinfusion.com/ipi-login/
  4. The correct public view URL is: https://featurematrix.ipinfusion.com/public/
  5. Admin URLs require the user to be logged into the backend first
  6. E.g., links such as: https://featurematrix.ipinfusion.com/wp-admin/edit.php?post_type=platform will result in a Not Found error if the admin user is not already logged in

HOW TO MIGRATE CHANGES FROM STAGING TO PRODUCTION

note

The PRD and STG instances are not automatically connected. They are separate sites managed in the hosting back end. There is no feature in the WordPress admin backend to automatically publish content from staging over to production, or vice versa. Publishing data in the WordPress app happens only within a site instance, but not between.

There are two ways to move content between PRD and STG instances, both of which are manual steps:

  1. REPEAT WORDPRESS EDITS - For small edits, the same editing steps done in staging are repeated in production. This can be tedious, but for small number of edits it is faster.
  2. SERVER PUSH - When the quantity or complexity of edits is larger, the entire staging instance is pushed to production from the site hosting backend.

In the same fashion as when PRD is copied to STG to make a 1:1 mirrored copy, the reverse is also done. Once updates are completed and approved in STG, then that instance is copied back to PRD. The entire site and DB are mirrored in one operation. This has been done in the past without issue.

When a full site push is needed, IP Infusion staff will coordinate with the vendor team at Mighty Digital to copy STG over to PRD.

note

All site instances are backed up nightly (PRD and STG separately). In the case a server push needs to roll back to a previous instance that is also done from the site hosting back end.

FULL FEATURES LIST

TBD