adrianmcli / adrianmcli/dev-react-component
Making multiple components / Add a dev server
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Some people (credits to @alex-wilmer) have expressed interest in:
1. Being able to make more than one component, and;
2. Have a convenient built-in dev server.
And while I can definitely respect the need for these features, I feel like it is a little out of my reach at this moment. Either because of my laziness or lack of ability, I would recommend dealing with these problems in the following way:
# Make a library of components
I would like to have this as well, but alas it's not something that I can chew on at this time.
Most of the things I create are usually one-off, small components, and I think many designers have a similar propensity. As such, the Unix philosophy of making tiny, simple programs that do only one thing and do it well is pretty apt here.
At this time, if you want to make a library of components, I will have to apologize and simply ask you to create a new project for each component you want to make.
In other words, **I'm sorry, but I can't help with that right now**.
The upshot is that since this boilerplate is so minimalistic, it should be extremely easy to piece together a library with your individual component projects once we have a feature for building a library.
Or alternatively, you can use this boilerplate as a starting point, and simply move to a completely different management framework like [Knit](https://github.com/knitjs/knit/) or [Lerna](https://github.com/lerna/lerna) once you get there.
For me personally, I do not like to prematurely optimize, and since I am not prolific enough to make a library, I do not need such tools. At the end of the day, this boilerplate was made for me.
# Dev Server
Use the Storybook branch.
React Storybook may not give you much control over how you want to design your site, but it definitely gives you all you really need to design/develop most standalone components.
React Storybook is what I used to build the docs for [React Reveal Text](https://github.com/adrianmcli/react-reveal-text), and it allows for making some awesome interactive docs.
There is no need to manage Webpack, but you do have to learn React Storybook, although I'd say it's very much well worth it (and really way easier than learning Webpack).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.