Sharing Ideas for New Features

Introduction

GitHub Discussions is the best place to submit feature requests for Project Planner. It allows the community to discuss, refine, and upvote ideas before they move into development.

Before Submitting

Before creating a new feature request, take a moment to check the following:

1. Search existing discussions — Your idea may already have been proposed. If it has, add your thoughts to the existing thread rather than opening a duplicate.
2. Check the documentation — The feature you're looking for may already exist. Browse the docs to see if it's covered.
3. Review the changelog — Recent updates may have added the functionality you're after.

What Makes a Good Feature Request

Clear Description

State exactly what the feature should do. Be specific and avoid ambiguity.

Use Case

Explain the problem you're trying to solve or the improvement you'd like to see. Describe any workarounds you currently use and why they fall short.

Context and Examples

Including mockups, screenshots, references to similar features in other tools, or concrete examples makes it much easier for others to understand your vision.

Consider the Philosophy

Project Planner is built around core principles. When proposing a feature, consider how it aligns with:

• Local-first — Data stays on the user's device.
• Plain text — Content is stored as readable Markdown files.
• Flexibility — Users should be able to adapt the tool to their workflow.
• Markdown compatibility — Features should work within Markdown conventions.

How to Submit

1. Go to the Ideas category on GitHub Discussions.
2. Click New discussion.
3. Give your idea a clear, descriptive title that summarizes the feature in a few words.
4. Fill in the body with a description, use case, and any supporting context or examples.
5. Submit the discussion and engage with any follow-up questions from the community.

What Happens Next

After you submit a feature request, here's the typical lifecycle:

1. Community discussion — Other users comment, refine, and upvote the idea.
2. Developer review — The maintainer evaluates the request based on alignment with the project's goals, overall benefit to users, technical feasibility, and impact on the existing codebase.
3. Status updates — The discussion is updated with any decisions or progress.
4. Implementation — Accepted features are added to the development roadmap and eventually released.

Examples of Great Feature Requests

Here are two examples that illustrate what a strong feature request looks like:

Supporting Other Ideas

You don't have to submit your own idea to make a difference. Here are ways to support existing feature requests:

• Upvote — React with a 👍 to show your support.
• Comment with your use case — Adding your perspective helps demonstrate broad demand.
• Share — Spread the word in community channels so more people can weigh in.

Questions