Can I create features without GitHub integration?

Why Manual Features?

While GitHub integration is powerful for code-based projects, many situations call for manual changelog creation:

• Non-technical Projects - Design updates, content changes, process improvements
• Different Version Control - Using GitLab, Bitbucket, or other systems
• Mixed Workflows - Some changes come from code, others from manual work
• Editorial Control - Prefer to craft each changelog entry manually
• Client Work - Changes that aren't reflected in your repository
• Service Updates - Operational changes, policy updates, or service improvements

Manual Feature Creation

Creating Individual Features

Build your changelog by manually adding features and improvements:

• Feature Title - Clear, user-focused description of what changed
• Detailed Description - Explanation of the impact and benefits
• Feature Type - Categorize as Added, Changed, Fixed, Removed, etc.
• Release Date - When the feature was made available to users
• Priority Level - Importance ranking for organizing your changelog

Feature Categories

Organize your manual features using standard changelog categories:

• Added - New features, functionality, or capabilities
• Changed - Modifications to existing features
• Fixed - Bug fixes, error corrections, or issue resolutions
• Removed - Features or functionality that was taken away
• Deprecated - Features marked for future removal
• Security - Security improvements or vulnerability fixes

Use Cases for Manual Features

Design and Creative Projects

• Visual Updates - New branding, color schemes, or layout changes
• User Experience - Improved workflows, navigation, or accessibility
• Content Updates - New pages, updated copy, or fresh imagery
• Brand Evolution - Logo updates, style guide changes, or messaging updates

Service and Operations Updates

• Policy Changes - Updated terms of service, privacy policies, or pricing
• Support Improvements - New help resources, faster response times, or additional channels
• Infrastructure Updates - Server improvements, performance enhancements, or reliability fixes
• Integration Additions - New third-party integrations or API endpoints

Product Management Updates

• Feature Rollouts - Gradual releases or A/B test completions
• Pricing Changes - New plans, updated pricing, or promotional offers
• Partnership Announcements - New integrations or collaborative features
• Market Expansion - New regions, languages, or market segments

Mixed Workflow: Manual + GitHub

Best of Both Worlds

You can combine manual and automated approaches:

• Code Changes - Let GitHub integration handle technical updates
• Manual Additions - Add business updates, design changes, or process improvements
• Editorial Control - Review and refine AI-generated entries before publication
• Complete Picture - Ensure your changelog reflects all user-facing changes

Hybrid Workflow Example

1. GitHub Integration syncs technical commits and bug fixes
2. Product Manager manually adds new feature announcements
3. Design Team manually adds UI/UX improvements
4. Marketing Team manually adds partnership or policy updates
5. Team Review ensures all changes are captured before publication

Manual Feature Best Practices

Writing User-Focused Entries

• Focus on Benefits - Explain how changes help users, not just what changed
• Use Clear Language - Avoid technical jargon and industry-specific terms
• Be Specific - Provide concrete details about improvements and fixes
• Show Impact - Quantify improvements when possible (e.g., "50% faster loading")

Consistency and Organization

• Consistent Format - Use the same structure for all changelog entries
• Logical Categories - Group similar changes together
• Chronological Order - Present changes in a logical time sequence
• Regular Updates - Maintain a consistent schedule for changelog updates

Examples of Manual Features

Tools for Manual Management

Rich Text Editor

Create detailed feature descriptions with formatting support:

• Rich Formatting - Bold, italics, lists, and links
• Image Support - Add screenshots or diagrams to explain changes
• Code Snippets - Include technical details when relevant
• Preview Mode - See how your changelog will appear to users

Scheduling and Publishing

• Draft Mode - Prepare entries before publishing
• Scheduled Publishing - Set release dates for planned announcements
• Bulk Management - Handle multiple entries at once
• Version Control - Track changes to your changelog entries

Getting Started with Manual Features

Creating Your First Manual Feature

1. Navigate to your project in WhatWeShipped
2. Go to the Changelog section
3. Click "Add Manual Feature"
4. Fill in the feature title and description
5. Select the appropriate category and priority
6. Set the release date and publish

Building a Manual Changelog Workflow

1. Regular Collection - Establish a process for gathering changes
2. Team Input - Get updates from different departments
3. User Perspective - Frame changes from the user's point of view
4. Review Process - Have team members review entries before publication
5. Consistent Schedule - Publish updates on a regular schedule