Thank you for your interest in contributing to DevToolkit! We're excited to have you join our Hacktoberfest 2025 community.
- Fork this repository
- Create a new branch for your feature
- Follow our design guidelines (see below)
- Test your tool on desktop and mobile
- Submit a pull request
IMPORTANT: All new tools must use our design template to maintain consistency.
📖 Read the complete template: TOOL_TEMPLATE.md
tools/your-tool-name/
├── index.html # Main tool page (use template!)
├── script.js # Tool functionality
└── README.md # Tool documentation (optional)
- ✅ Use the provided HTML template from
TOOL_TEMPLATE.md - ✅ Follow our color scheme (Hacktoberfest orange/blue theme)
- ✅ Include animated background and back button
- ✅ Make it responsive for mobile devices
- ✅ Use consistent typography and spacing
Add your tool card to index.html:
<a
href="tools/your-tool-name/index.html"
class="tool-card"
data-category="your-category"
>
<div class="tool-icon">
<i class="fas fa-your-icon"></i>
</div>
<div class="tool-content">
<h3 class="tool-title">Your Tool Name</h3>
<p class="tool-description">Brief description of functionality.</p>
<div class="tool-tags">
<span class="tag">Category</span>
<span class="tag">Feature</span>
</div>
</div>
<div class="tool-arrow">
<i class="fas fa-arrow-right"></i>
</div>
</a>- Dark theme with Hacktoberfest colors
- Animated background with floating shapes
- Back button (top-left, fixed position)
- Consistent typography using Poppins font
- Hover animations and smooth transitions
- Mobile-responsive design
text- Text processing toolscode- Code-related toolsutility- General utilitiesconverter- Format converters
--primary-color: #ff6b35 /* Hacktoberfest Orange */
--secondary-color: #0081b4 /* Blue */
--bg-primary: #0f0f23 /* Dark Background */
--bg-secondary: #1a1a2e /* Card Background */
--text-primary: #ffffff /* White Text */Before submitting your PR:
- Read and followed
TOOL_TEMPLATE.md - Tool uses consistent design with main website
- Responsive design tested on mobile
- Back button links to main page
- Tool added to main page grid
- No console errors
- Clean, well-commented code
- PR linked to an issue
- Desktop Testing: Test on Chrome, Firefox, Safari
- Mobile Testing: Test responsive design on mobile devices
- Functionality: Ensure all features work as expected
- Performance: Check for smooth animations and fast loading
High-quality visual documentation helps users understand your tool quickly and makes your contribution stand out. Follow these guidelines to create professional screenshots and GIFs.
- Resolution: Capture at 1920x1080 or higher
- Browser: Use Chrome with clean UI (hide bookmarks bar)
- Zoom Level: Use 100% zoom for consistency
- Window State: Maximized browser window
- Format: Save as PNG for crisp quality
- Device: Use Chrome DevTools device simulation
- Recommended Devices: iPhone 12 Pro (390x844) or Pixel 5 (393x851)
- Orientation: Both portrait and landscape when relevant
- Touch Elements: Show interactive elements clearly
- ✅ Tool in action - Show the tool being used with sample data
- ✅ Input/Output examples - Demonstrate clear before/after states
- ✅ Key features - Highlight unique functionality
- ✅ Responsive design - Show mobile and desktop versions
- ✅ Error states - Show validation messages when relevant
📋 Pre-Screenshot Checklist:
- [ ] Clean browser (no personal bookmarks/extensions visible)
- [ ] Use meaningful sample data (not "test", "asdf", etc.)
- [ ] Ensure proper lighting/contrast in your environment
- [ ] Close unnecessary browser tabs
- [ ] Use consistent window size across screenshots
- Interactive workflows - Multi-step processes
- Animations and transitions - Show smooth UI interactions
- Tool demonstrations - Complete usage examples
- Feature highlights - Show key functionality in action
- Duration: 3-10 seconds (keep it concise)
- Frame Rate: 15-20 FPS (smooth but not too large)
- Resolution:
- Desktop: 1280x720 (720p) maximum
- Mobile: Original device resolution
- File Size: Under 5MB (optimize for GitHub)
- Format: GIF or MP4 (MP4 preferred for smaller size)
Free Tools:
- LICEcap (Windows/Mac) - Simple screen recording to GIF
- ScreenToGif (Windows) - Advanced GIF editing features
- Kap (Mac) - Clean, simple screen recording
- GIPHY Capture (Mac) - Easy GIF creation with editing
Browser Extensions:
- Loom - Record and convert to GIF
- CloudApp - Quick screen capture with GIF export
Online Tools:
- EZGIF.com - Convert videos to optimized GIFs
- CloudConvert - Format conversion with compression options
🎯 GIF Recording Tips:
- [ ] Plan your actions beforehand (practice the workflow)
- [ ] Use deliberate, slower movements (easier to follow)
- [ ] Include brief pauses between actions (1-2 seconds)
- [ ] Start recording after the page loads completely
- [ ] Focus on the relevant area (crop unnecessary space)
- [ ] Use realistic data that demonstrates the tool's value
📁 File Structure:
tools/your-tool-name/
├── screenshots/
│ ├── desktop-main.png
│ ├── desktop-demo.png
│ ├── mobile-portrait.png
│ ├── mobile-landscape.png
│ └── workflow-demo.gif
└── README.md
desktop-main.png- Main tool interface (desktop)mobile-portrait.png- Mobile view in portraitfeature-highlight.png- Specific feature demonstrationworkflow-demo.gif- Complete usage workflowerror-handling.png- Error state examples
Before submitting your PR, ensure your visual documentation includes:
Required Screenshots:
- Desktop main view - Tool interface with sample data
- Mobile responsive view - At least one mobile screenshot
- Tool in action - Demonstrating core functionality
Optional but Recommended:
- Workflow GIF - Complete usage demonstration
- Feature highlights - Key functionality screenshots
- Before/after examples - Input and output states
- Error handling - Validation and error messages
Technical Quality:
- High resolution - Clear, crisp images
- Consistent styling - Same browser, zoom level, window size
- Meaningful data - Realistic examples, not placeholder text
- Optimized file size - Compressed appropriately for web
- Proper naming - Clear, descriptive filenames
- Use the same browser (Chrome recommended) for all screenshots
- Maintain consistent zoom level (100%)
- Use clean sample data that showcases the tool's purpose
- Ensure proper contrast and readability
- Show the tool in its best light - well-designed, functional
Good Sample Data:
✅ JSON Formatter: Real API response example
✅ Text Converter: "Hello World" → "HELLO WORLD"
✅ Color Picker: #FF6B35 (Hacktoberfest Orange)
✅ Password Generator: "K7#mN2$pQ9@x" (realistic password)
Avoid:
❌ "test", "asdf", "sample text"
❌ Lorem ipsum for functional demonstrations
❌ Empty or minimal inputs that don't showcase features
❌ Personal or sensitive information
## Screenshots
### Desktop Interface

### Mobile Responsive Design

### Tool Demonstration
### 📸 Screenshots
**Desktop Interface:**

**Mobile Responsive:**

**Demo GIF:**
feat: Add [Tool Name] toolfix: Fix [issue] in [Tool Name]docs: Update [Tool Name] documentation
## 🛠️ Tool: [Tool Name]
### 📝 Description
Brief description of what this tool does.
### ✨ Features
- Feature 1
- Feature 2
- Feature 3
### 📱 Testing
- [x] Desktop (Chrome, Firefox, Safari)
- [x] Mobile responsive design
- [x] All functionality working
- [x] No console errors
### 🎨 Design Compliance
- [x] Uses TOOL_TEMPLATE.md
- [x] Consistent with main website design
- [x] Includes animated background
- [x] Back button implemented
- [x] Mobile responsive
### 📸 Screenshots
[Add screenshots of your tool here]
Closes #[issue-number]- Don't create custom styling that conflicts with the design system
- Don't forget the back button and animated background
- Don't skip mobile responsive testing
- Don't use different colors than the design system
- Don't submit without reading
TOOL_TEMPLATE.md
Looking for inspiration? Here are some tool ideas:
Text Tools:
- JSON Formatter/Validator
- Markdown to HTML Converter
- Text Case Converter
- Lorem Ipsum Generator
Code Tools:
- Color Picker
- RegEx Tester
- Base64 Encoder/Decoder
- URL Encoder/Decoder
Utilities:
- QR Code Generator
- Password Generator
- Hash Generator
- Image Compressor
- 📖 Read:
TOOL_TEMPLATE.mdfor complete guidelines - 👀 Reference: Check
tools/word-counter/for example implementation - 🐛 Issues: Open a GitHub issue for questions
- 💬 Discussions: Use GitHub Discussions for general questions
This project is participating in Hacktoberfest 2025!
- Make meaningful contributions
- Quality over quantity
- Follow our design guidelines
- Be respectful and collaborative
- Register for Hacktoberfest 2025
- Make sure your PR is meaningful and follows guidelines
- Wait for maintainer review and approval
- Celebrate your contribution! 🎉
Please be respectful and welcoming to everyone. All contributors are expected to follow our Code of Conduct.
Thank you for contributing to DevToolkit! Your contributions help developers worldwide and make the open-source community stronger.
Happy Coding! 🚀✨