Schema App: Feature Request Enhancements

[zcolah]

Feature Requests

Validation & Input Enhancements

Input Masking for Text Fields

Problem: Users want real-time formatting guidance while entering text.
Solution: Implement input masking to format values as they are typed.
Example Use Case: Auto-formatting phone numbers as (123) 456-7890.
Customer Notes: Improves data consistency and user experience.

DateTime Field Improvements

Problem: DateTime fields currently lack timezone control.
Solution:

• Allow custom date format settings.
• Add a toggle for timezone awareness
• Provide a timezone selection UI Example Use Case: Displaying "Dec 25, 2022, 7:00 PM PST" instead of "2022-12-25 00:00:00:.000000".

Field & Model Improvements

Custom/Composite Field Types

Problem: Users want to combine multiple fields into a reusable structure.
Solution: Allow defining custom field types that bundle multiple sub-fields together.
Example Use Case: Creating an "Address" field type with street, city, state, and zip sub-fields.
Customer Notes: Saves time and ensures data consistency across models.

Markdown Support for Descriptions

Problem: The description field lacks formatting options.
Solution: Allow Markdown support for field descriptions.
Example Use Case: Using bold text and bullet points for better readability.
Customer Notes: Helps make field descriptions clearer and more informative.

Markdown/HTML Field for Author Instructions

Problem: Users need to add guidance for content creators without affecting stored data.
Solution: Add a field type that displays Markdown/HTML as non-editable instructions in the UI.
Example Use Case: Providing formatting guidelines for content editors.
Customer Notes: Improves clarity and reduces confusion for contributors.

Model Inheritance

Problem: Users have to duplicate fields across similar models.
Solution: Enable inheritance to share base fields across multiple models.
Example Use Case: A "Base Event" model that other event types (Webinar, Conference) extend from.
Customer Notes: Reduces redundant fields and simplifies content management.

Convert Model Type After Creation

Problem: Users might need to change a model’s type after setup.
Solution: Allow switching between Single Page, Multi-Page, and Headless models.
Example Use Case: A user starts with a Single Page model but later needs Multi-Page capabilities.
Customer Notes: Provides flexibility and prevents early-stage decision lock-in.

Content Management & Impact Analysis

Inbound Links Display

Problem: Users don’t know which content items link to the current one.
Solution: Show a list of inbound links referencing the current item.
Example Use Case: Ensuring no broken references before deleting or modifying an entry.
Customer Notes: Improves content integrity and editing confidence.

Usability & Navigation

Git Integration & Version History with Rollback

Problem: Users want better version control for models.
Solution: Add Git integration for tracking changes and rolling back if needed.
Example Use Case: Reverting to an earlier version after an unintended schema change.
Customer Notes: Enhances safety and provides a clear change history.

Open "Edit Code" & "View Logs" in New Tabs

Problem: Navigating back and forth disrupts workflow.
Solution: Ensure "Edit Code" and "View Logs" open in new browser tabs.
Example Use Case: Users debugging content issues can keep logs open while editing.
Customer Notes: Prevents losing context and improves multitasking.

Rename One-to-One & Many-to-One Relationships

Problem: The current labels are misleading for relational database users.
Solution:

• Rename "One-to-One" to "Single Link".
• Rename "Many-to-One" to "Multi-Link".
  Example Use Case: More intuitive relationship naming for developers familiar with database structures.
  Customer Notes: Prevents confusion and misinterpretation of data relationships.

Surrogate Field for Meta Title in Tabs

Problem: Not all models have a Meta Title field, making tab names unhelpful.
Solution: Allow users to set an alternative field for the browser tab title.
Example Use Case: Using the "Product Name" field for an eCommerce product instead of an empty Meta Title.
Customer Notes: Improves usability when navigating multiple content items.

General Notes

• The UI design is well-received and visually appealing.
• The field count summary by type is noted but may not have significant practical value.

---

Overall, the feedback emphasizes improving validation, field flexibility, content management insights, and UI usability.