Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Anatomy of a Dash component library

Open
#119 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, julia, python, r, webpack
Domain
documentation

Research direction

Start at the root of the generated component library and review the listed JS, webpack, npm, R, Julia, PyPI, and documentation files. Create a Markdown guide grouped by Python, R, JavaScript, and Julia that explains each file and whether a beginner needs to modify it; the guide is done when the root files and their roles are covered.

Written by the indexing model from the issue text.

Description

When we look at the root of the generated component library, we notice a lot of files from various aspects of Dash. We will have files related to

  • JS (.eslintrc, src/, index.html),
  • webpack (webpack.config.js, webpack.serve.config.js),
  • npm (package.json, .npmignore, package-lock.json),
  • R (.Rbuildignore, R/, inst/deps/),
  • Julia (src/),
  • pypi (MANIFEST.in, setup.py)
  • docs (.md files)
  • etc.

Although you get a hang of what each file does after a while, I think it might be a bit disorienting for a beginner, especially since the files span 4 different languages. It would be nice to have a md doc describing what each file does, whether you will need to worry about it not. The doc could be grouped by language (Python, R, JS, Julia).

Thoughts on this?

Dominant language
Python
Stars
294
Forks
196
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plotly/dash-component-boilerplate

All issues in plotly/dash-component-boilerplate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.