1. The Submission Protocol
How to write a high-impact specification.
To fast-track your request through our engineering triage, please structure your submission as a User Story. Vague requests (e.g., "Make the dashboard better") are hard to act on. Specific protocols (e.g., "Add team-level permission roles") get built.
Recommended Schema:
Title:
A concise summary (e.g., "Feature: Automated CSV Export Schedule").
"Feature: Automated CSV Export Schedule"
The Problem:
What friction point are you facing? (e.g., "I currently have to manually export translations every Friday.").
"I currently have to manually export translations every Friday."
The Solution:
Your proposed fix (e.g., "Allow us to schedule an auto-export to email every week.").
"Allow us to schedule an auto-export to email every week."
Context:
Screenshots, sketches, or loom videos are highly encouraged to visualize the UI.
"Attach mockups, wireframes, or screen recordings showing the desired workflow."
2. Transmission Channel
Currently, all architectural requests should be routed directly to our Product Engineering team via email.
Endpoint:
support@multilipi.comSubject Line:
[Feature Request] - Your Title Here3. The Engineering Lifecycle
What happens after you hit send?
Triage:
Our Product Manager reviews the request for technical feasibility and alignment with our core infrastructure goals.
Clarification:
We may reply to ask specific questions about your use case (e.g., "Do you need this export in JSON or CSV?").
Roadmap Assignment:
If the feature is approved, it is assigned a slot in our development sprint.
Deployment:
You will be notified via email when the feature moves from "In Development" to "Live Production."
Why Contribute?
The benefits of shaping our platform
Strategic Alignment
Influence the tool to work exactly how your team works.
Early Access
Users who submit accepted features often get beta access to test them before the general public.
Community Impact
Your workflow improvement likely solves a problem for thousands of other site owners.