How to quickly add the three SigMap component links to existing announcement files.
Always include these together:
🔧 SigMap Tool: https://github.com/manojmallick/sigmap
📚 SigMap Docs: https://manojmallick.github.io/sigmap/
📊 SigMap Benchmark: https://github.com/manojmallick/sigmap-benchmark-suite
Find:
GitHub: https://github.com/manojmallick/sigmap-benchmark-suite
Replace with:
SigMap Ecosystem:
🔧 Tool: https://github.com/manojmallick/sigmap
📚 Docs: https://manojmallick.github.io/sigmap/
📊 Benchmark: https://github.com/manojmallick/sigmap-benchmark-suite
Locations to update:
- LinkedIn post (multiple places)
- Dev.to article (resources section)
- Email announcement
- Reddit posts (each post)
- HackerNews post
- Slack/Discord posts
Thread 1, Post 9 (Update CTA):
Old:
GitHub: https://github.com/manojmallick/sigmap-benchmark-suite
New:
SigMap Ecosystem:
📦 Tool: github.com/manojmallick/sigmap
📚 Docs: manojmallick.github.io/sigmap/
📊 Dataset: github.com/manojmallick/sigmap-benchmark-suite
Thread 1, Post 1 (Update Hook):
Old:
Let me share what we found 🧵
GitHub: https://github.com/manojmallick/sigmap-benchmark-suite
New:
Part of the larger SigMap ecosystem. Let me explain 🧵
GitHub: https://github.com/manojmallick/sigmap-benchmark-suite
Thread 2, Post 1 (Add Ecosystem Intro):
Add before "Here's the methodology":
Part of the SigMap ecosystem:
📦 Tool: github.com/manojmallick/sigmap
📚 Docs: manojmallick.github.io/sigmap/
📊 Data: github.com/manojmallick/sigmap-benchmark-suite
Thread 3, Post 1 (Update CTA Intro):
Old:
Ready to use SigMap for your own research/tool?
New:
Ready to use the complete SigMap ecosystem?
Complete ecosystem:
📦 Tool: github.com/manojmallick/sigmap
📚 Docs: manojmallick.github.io/sigmap/
📊 Dataset: github.com/manojmallick/sigmap-benchmark-suite
How to get started 🧵
Priority 1 (Must Update):
- TWITTER_PREMIUM_OPTIMIZED.md — Posts 1 & 9 of each thread
- PLATFORM_ANNOUNCEMENTS.md — LinkedIn & Reddit sections
- Main README.md — Add ecosystem table
Priority 2 (Should Update):
- Dev.to article
- Email announcement
- GitHub discussions post
- HackerNews post
Priority 3 (Nice to Have):
- Slack/Discord posts
- Papers with Code entry
- Academic mailing lists
| Platform | Location | Context |
|---|---|---|
| Post 1 & final post of each thread | Intro + CTA | |
| Beginning + resources section | Context + links | |
| GitHub | Main README + discussions | Overview |
| Dev.to | Resources section | External links |
| Opening post | Ecosystem intro | |
| Key section | Complete ecosystem | |
| HackerNews | Post text | Technical context |
"The SigMap ecosystem consists of three components:
🔧 Tool — The context extraction implementation
📚 Docs — Complete integration guide
📊 Benchmark — Large-scale evaluation (this project)
Together, they provide everything needed for context extraction research."
"For implementation details: github.com/manojmallick/sigmap
For usage guides: manojmallick.github.io/sigmap/
For evaluation & research: github.com/manojmallick/sigmap-benchmark-suite"
"📥 Start here:
1. Explore the tool
2. Read the documentation
3. Download the benchmark dataset
All open-source, CC-BY-4.0 licensed."
- Open PLATFORM_ANNOUNCEMENTS.md
- Find all instances of GitHub links
- Replace standalone GitHub links with ecosystem format
- Update intro/hook sections to mention ecosystem
- Save
Time: 10-15 minutes to update all platforms
After updating, verify:
- All three links present in each announcement
- Links formatted consistently
- No broken URLs
- Ecosystem context clear
- Call-to-action updated
- Hashtags updated if needed
- Character count OK for Twitter (if edited)
✅ DO:
- Use consistent formatting for the three links
- Explain relationship between components
- Provide multiple entry points based on user needs
- Keep links up-to-date
❌ DON'T:
- Include only one link (incomplete picture)
- Use different formats across platforms
- Forget to update CTAs
- Break existing URLs
After initial update, keep ecosystem links current:
- Check links monthly for accessibility
- Update if repos move or URLs change
- Add new components if created (e.g., CLI tool)
- Maintain consistency across all platforms
Always have these ready:
Tool: https://github.com/manojmallick/sigmap
Docs: https://manojmallick.github.io/sigmap/
Benchmark: https://github.com/manojmallick/sigmap-benchmark-suite
Primary: https://doi.org/10.5281/zenodo.19898842
Extended: [Pending Zenodo]
Copy-paste as needed in announcements.
Before:
- Mentions only benchmark repo
- Incomplete picture of project
- Users don't know about tool or docs
After:
- All three components visible
- Complete ecosystem understanding
- Users can choose their entry point
- Professional, cohesive project image
Total update time: 15-20 minutes
Impact: Much stronger, more complete project presentation
Effort: Minimal (mostly copy-paste with finds/replaces)