VS Code Integration Tutorials
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- git, markdown
- Domain
- developer-experience, documentation
Research direction
Start by reviewing the proposed tutorial topics in issue #169 and defining the scope of the series, including which VS Code extensions are covered and whether each topic needs written and video material. Done means the selected tutorials explain TODO management, Git history and blame, and CSV/XML/XLSX viewing alongside rxiv-maker, with clear academic-writing examples.
Written by the indexing model from the issue text.
Description
📝 Description
Create a series of written and video tutorials showcasing how to combine rxiv-maker with popular VS Code extensions to maximize productivity when writing scientific papers.
🎯 Motivation
While rxiv-maker already provides excellent manuscript generation capabilities, many researchers use VS Code as their primary editor and could benefit from learning how to leverage the broader VS Code ecosystem alongside rxiv-maker for an enhanced writing experience.
💡 Proposed Content
Tutorial Series with different plugins:
- TODO Management
- Integration with Todo Tree extension
- Managing research tasks, citations to add, figure improvements, etc.
- Custom TODO tags for academic writing (e.g., // CITE:, // REVIEW:, // FIGURE:)
- Enhanced Markdown Editing
- Version Control for Papers
- For example GitLens for git history tracking
- Git blame
- Rainbow CSV / Excel Viewer
- For looking inside .csv/.xml/.xmlsx files without code or leaving vs code
- Other options?
- Dominant language
- Python
- Stars
- 45
- Forks
- 7
- Avg merge
- 15m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HenriquesLab/rxiv-maker
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HenriquesLab/rxiv-maker#335 ·
-
eature request: automatically continue long figure legends on the next pagePossibly taken @paxcalpt claimed this 77 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 38/100
HenriquesLab/rxiv-maker#324 · 1 comment ·
All issues in HenriquesLab/rxiv-maker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib-wallet#587 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Judgment-Pack/judgment-pack-spec#275 ·
Maintainers usually reply within 1 day
-
ai-generated
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
documentation good first issue priority: low size: XS
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
yeongseon/azure-functions-doctor-python#651 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Changaco/python-libarchive-c#146 ·