AtiQr - Wikipedia Training Tool
A Wikipedia training tool designed for school Wikipedia clubs to help beginners, intermediate, and expert writers improve their editing skills. Get real-time analysis, side-by-side corrections, and learn Wikipedia guidelines through practice.
๐ Learn by Doing | ๐ฏ Real-time Corrections | ๐ Multilingual Support | ๐ Wikipedia Guidelines Mastery
๐ Features
Dual Canvas Training Mode
- ๐ Paste & Analyze: Paste your draft and see corrections side-by-side
- ๐ Article Study Mode: Analyze existing Wikipedia articles to learn from good examples
- ๐ฏ Visual Corrections: Original text vs. improved version with detailed explanations
- ๐ Learning Points: Understand why each correction matters
- ๐ Citation Training: Learn where and how to add proper citations
Wikipedia Policy Compliance
- โ Neutral Point of View (NPOV): Detect biased language and promotional content
- ๐ Verifiability: Check citation requirements and source quality
- ๐ซ No Original Research: Flag unsourced claims and synthesis
- โ๏ธ Notability: Assess if topic meets notability guidelines
- ๐ค Code of Conduct: Ensure respectful, collaborative tone
Quality Metrics
- Readability Analysis: Flesch reading score, sentence complexity, vocabulary level
- Citation Quality: Inline citations, citation density, reference formatting
- Reference Assessment: Source reliability, diversity, and recency
- Structural Analysis: Section organization, header hierarchy, content balance
- Language Quality: Grammar, spelling, and style consistency
Multilingual Support
- ๐ 8 Languages: English, French, Arabic, Swahili, Hausa, Yoruba, Amharic, Zulu
- ๐ฃ๏ธ Language-specific Analysis: Adapted guidelines for different Wikipedia editions
- ๐ Cross-language Learning: Study articles in multiple languages
- ๐ Beginner-friendly: Perfect for school Wikipedia clubs
Training Features
- ๐ Progress Tracking: Track common mistakes and improvements over time
- ๐ฏ Targeted Learning: Focus on specific Wikipedia guidelines
- ๐ก Learning Points: Understand the "why" behind each correction
- ๐ฑ Mobile Friendly: Practice on any device
- ๐ Guideline Links: Direct links to Wikipedia policy pages
- ๐ฅ Perfect for Groups: Ideal for school Wikipedia clubs and training sessions
Export Features
- ๐จ๏ธ Print/PDF: Generate printable training reports with full analysis
- ๐ Markdown: Export to Markdown format for documentation
- ๐ CSV: Export corrections to spreadsheet format for tracking
- ๐พ JSON: Export complete analysis data for developers
- ๐ค Share with Teachers: Save and share your progress for feedback
๐ Quick Start
Prerequisites
- Node.js 18+ and npm
- Modern web browser with JavaScript enabled
Installation
# Clone the repository
git clone https://github.com/your-username/atiqr.git
cd atiqr
# Install dependencies
npm install
# Start development server
npm run dev
The application will be available at http://localhost:5173
Building for Production
# Build the application
npm run build
# Preview the production build
npm run preview
๐ Usage Guide
Two Training Modes
1. Paste & Analyze Mode
- Write or paste your Wikipedia draft in the text area
- Select your language (English, French, Arabic, Swahili, etc.)
- Click "Analyze & Learn"
- Review corrections side-by-side with explanations
2. Article Study Mode
- Paste a Wikipedia article URL
- Click "Analyze & Learn"
- Study how the article follows (or breaks) Wikipedia guidelines
- Learn from good examples and identify areas for improvement
Understanding Corrections
AtiQr identifies three types of issues:
- ๐ด Critical (Errors): Violations of core Wikipedia policies (NPOV, Verifiability, No Original Research)
- ๐ Important (Warnings): Style issues that affect article quality (weasel words, peacock terms)
- ๐ต Suggestions: Recommendations for improvement (citation placement, structure)
Learning from Corrections
Each correction includes:
- Original Text: What you wrote
- Improved Version: How it should be written
- Explanation: Why the change is needed
- Guideline Link: Direct link to Wikipedia policy page
- Category: Type of issue (citation, NPOV, style, etc.)
Common Issues AtiQr Catches
- Missing Citations: Factual claims without sources
- Biased Language: Words like "clearly", "obviously", "best"
- Weasel Words: Vague phrases like "some people say"
- Peacock Terms: Promotional language like "legendary", "world-famous"
- Original Research: Personal opinions or conclusions
- Poor Structure: Missing sections or unbalanced content
๐ ๏ธ Technical Architecture
Frontend Stack
- React 18: Modern React with hooks and functional components
- TypeScript: Type-safe development with full IntelliSense
- Tailwind CSS: Utility-first CSS framework for rapid styling
- Vite: Fast build tool and development server
- Lucide React: Beautiful, consistent icon library
API Integration
- Wikipedia REST API: Article content and metadata
- Wikipedia Action API: Search functionality and article parsing
- CORS Handling: Proper cross-origin request management
Code Organization
src/
โโโ components/ # Reusable UI components
โ โโโ ArticleInput.tsx # Search and URL input
โ โโโ AnalysisResults.tsx # Main results display
โ โโโ ScoreCard.tsx # Individual metric cards
โ โโโ SuggestionsList.tsx # Improvement recommendations
โ โโโ RecentAnalyses.tsx # Analysis history
โโโ services/ # Business logic and API calls
โ โโโ wikipediaApi.ts # Wikipedia API integration
โ โโโ qualityAnalyzer.ts # Article analysis algorithms
โโโ types/ # TypeScript type definitions
โ โโโ index.ts # Shared interfaces
โโโ App.tsx # Main application component
๐ง Configuration
Environment Variables
No environment variables required for basic functionality. All APIs used are public and don't require authentication.
Customization Options
- Scoring Weights: Modify weights in
qualityAnalyzer.ts - UI Theme: Adjust colors in
tailwind.config.js - API Endpoints: Configure in
wikipediaApi.ts
๐งช Testing
# Run linting
npm run lint
# Type checking
npx tsc --noEmit
# Build test
npm run build
๐ฑ Browser Support
- Chrome 90+
- Firefox 88+
- Safari 14+
- Edge 90+
๐ค Contributing
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Development Guidelines
- Follow TypeScript best practices
- Use semantic commit messages
- Ensure responsive design
- Add proper error handling
- Write clear, self-documenting code
๐ License
This project is licensed under the MIT License - see the LICENSE file for details.
๐ Acknowledgments
- Wikipedia API for providing comprehensive article data
- Tailwind CSS for the excellent utility-first framework
- Lucide React for beautiful, consistent icons
- The Wikipedia editing community for inspiration
๐ Support
For questions, issues, or contributions:
- Create an issue on GitHub
- Contact the development team
- Check the documentation wiki
Made with โค๏ธ for the Wikipedia community

Log in or sign up for Devpost to join the conversation.