Welcome to our contributor community! 🎉
Your contributions make Flutter development better for everyone
|
Your contributions directly help Flutter developers worldwide create beautiful apps faster and easier. Work with modern technologies, improve your skills, and learn from experienced developers. Showcase your contributions to a popular open-source project used by developers globally. |
Connect with like-minded developers, share knowledge, and collaborate on exciting features. Help guide the direction of Flutter theme development tools and influence what gets built next. Contribute to tools that make coding more enjoyable and accessible for everyone. |
| 🐛 Bug Reports | ✨ Feature Requests | 📝 Documentation | 🎨 UI/UX Improvements |
|---|---|---|---|
| Found something broken? Help us fix it! | Have a great idea? Share it with us! | Make our docs clearer and more helpful | Enhance the user experience |
| Report Bug | Request Feature | Improve Docs | Enhance UI |
🔍 More Ways to Help
- 🧪 Testing: Try new features and report issues
- 🎓 Tutorials: Create guides and tutorials for other developers
- 🌐 Translations: Help make the tool accessible in more languages
- ⚡ Performance: Optimize code for better speed and efficiency
- 🔧 DevOps: Improve build processes and deployment workflows
- 📊 Analytics: Add insights to help users make better theme choices
# Fork on GitHub, then clone your fork
git clone https://github.com/mukhbit0/Flutter-Theme-Generator.git
cd Flutter-Theme-Generator# Install all project dependencies
npm install
# Start development server
npm run dev |
# Create a descriptive branch name
git checkout -b feature/awesome-new-feature
# or
git checkout -b fix/bug-description# Make your changes and test locally
npm run dev # Development server
npm run lint # Check code quality
npm run build # Test production build |
flowchart TD
A[🍴 Fork Repository] --> B[📥 Clone Your Fork]
B --> C[🌿 Create Feature Branch]
C --> D[💻 Make Changes]
D --> E[🧪 Test Locally]
E --> F{✅ All Tests Pass?}
F -->|No| D
F -->|Yes| G[📝 Commit Changes]
G --> H[🚀 Push to Your Fork]
H --> I[🔄 Create Pull Request]
I --> J[👀 Code Review]
J --> K{💯 Approved?}
K -->|Changes Needed| D
K -->|Yes| L[🎉 Merged!]
1. 🍴 Fork the Repository
- Visit the Flutter Theme Generator repository
- Click the Fork button in the top-right corner
- Select your GitHub account as the destination
2. 📥 Clone Your Fork
git clone https://github.com/mukhbit0/Flutter-Theme-Generator.git
cd Flutter-Theme-Generator
# Add the original repository as upstream
git remote add upstream https://github.com/mukhbit0/Flutter-Theme-Generator.git3. 🌿 Create a Feature Branch
# Always create a new branch for your changes
git checkout -b feature/your-feature-name
# Good branch naming examples:
# feature/color-picker-enhancement
# fix/dark-mode-toggle-bug
# docs/installation-guide
# ui/responsive-mobile-layout4. 💻 Make Your Changes
- Keep changes focused: One feature or fix per pull request
- Follow existing code style: Use our linting rules and patterns
- Write meaningful commit messages: Explain what and why, not just what
- Test your changes: Ensure everything works as expected
5. 🧪 Test Your Changes
# Run the development server
npm run dev
# Check for linting errors
npm run lint
# Run type checking
npm run type-check
# Build to ensure no production issues
npm run build6. 📝 Commit Your Changes
# Stage your changes
git add .
# Write a clear, descriptive commit message
git commit -m "feat: add color contrast checker for accessibility"
# Follow conventional commit format:
# feat: new feature
# fix: bug fix
# docs: documentation changes
# style: formatting changes
# refactor: code refactoring
# test: adding tests
# chore: maintenance tasks7. 🚀 Push and Create Pull Request
# Push your branch to your fork
git push origin feature/your-feature-nameThen visit GitHub to create a pull request with:
- Clear title describing what you've done
- Detailed description explaining the changes and why
- Screenshots for UI changes (before/after)
- Testing instructions for reviewers
|
|
Before submitting your pull request, ensure:
- Linting passes:
npm run lintshows no errors - TypeScript compiles:
npm run type-checksucceeds - Build succeeds:
npm run buildcompletes without errors - Manual testing: Your changes work as expected
- Responsive design: UI works on mobile and desktop
- Accessibility: Proper ARIA labels and keyboard navigation
- Performance: No unnecessary re-renders or heavy computations
|
## 🐛 Bug Description
Brief description of what went wrong
## 🔄 Steps to Reproduce
1. Go to theme generator
2. Upload a logo file
3. Click on color picker
4. Bug occurs here
## ✅ Expected Behavior
What should have happened
## ❌ Actual Behavior
What actually happened
## 🖼️ Screenshots
Add screenshots if applicable
## 💻 Environment
- Browser: Chrome 118
- OS: macOS 13.5
- Device: Desktop |
We focus on features that:
|
## 🚀 Feature Description
Clear summary of the proposed feature
## 🎯 Problem Statement
What problem does this solve?
## 💡 Proposed Solution
How would this feature work?
## 🌟 Benefits
- Who would benefit?
- How would it improve the tool?
- What use cases would it enable?
## 🎨 Mockups/Examples
Screenshots or wireframes if applicable
## 🔧 Technical Considerations
Any implementation thoughts? |
|
|