Generate content for projects pages
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
No files or tests are named. Start by locating the existing projects pages in the site source and reviewing their current structure and related documentation links. Done means each project page includes a brief summary, quickstart guide, library relationships, documentation link, and links to blog posts and presentations.
Written by the indexing model from the issue text.
Description
Include: Brief summary, quickstart guide, how does library relate to other libraries, link to docs, link to blogposts and presentations.
- Dominant language
- Jupyter Notebook
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 blaze/blaze.github.io-source
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
blaze/blaze.github.io-source#7 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
blaze/blaze.github.io-source#4 · 1 comment ·
All issues in blaze/blaze.github.io-source
Similar issues
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ramnes/notion-sdk-py#408 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/docs#46222 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
peteonrails/voxtype#844 ·
Maintainers usually reply within 1 day
-
enhancement priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Add a mail symbolOpenenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100