Updated list of things I will cover:
next/develop branchFor the contribution guides, it should be split into sections like: do you want to make an easy contribution or an advanced one. At the start, we could have a small summary, and maybe split it up into a menu with pointers to different guides. One could be tests, another AST et.al
@ev1stensberg Can we add "help wanted", "Good First Contribution" tags?
This is an maintainer issue, cause we need to make sure that the structure and documentation reflects how we want people to contribute. Discussed this in a meeting, @fokusferit can give you the link
@fokusferit any update? 馃挴
Moving #450 here
So here's what needs attention:
Migrate documentation
InIt documentation at webpack.js.org
CLI descriptions at webpack.js.org and in the CLI should be more descriptive
README in all the package folders for each package
Documentation and Contribution guide
Explaination about publishing and the next/develop branch
I'm updating the initial comment, and create a checklist, so that I it's easier to reference to PR's for each task.
@ev1stensberg I would like to work on Init documentation first.
Go for it!
@ev1stensberg check #547 for init documentation
@ev1stensberg how to add documentation to webpack.js.org to complete this task
Any update here lads?
@ematipico @fokusferit it would be really nice if you guys dedicated some time to work on this! 鉂わ笍
THis weekend I have planned to focus! It's scheduled!
Hmu if you need help @fokusferit
@ev1stensberg having a documentation website is much better as it will serve the cause quicker.
If you agree to same I am happy to build a solution for this :D
Docs page is webpack.js.org so stuff needs to go there 馃槄
Yeah but I couldn't find the docs for webpack-cli there.
Exactly. This is something this task should tackle.
We can collaborate on this, as I start with that topic and we could share tasks. Are you
https://cli.angular.io
Angular CLI has its own too ;)
@fokusferit we will be doing this at https://webpack.js.org or a standalone?
@rishabh3112 they have it but in our case I think the CLI is an integral part so having them all in one place makes more sense & referencing to the CLI in that doc's will increase visibility :)
This issue had no activity for at least half a year.
It's subject to automatic issue closing if there is no activity in the next 15 days.
@evenstensberg May I work on this?
This issue had no activity for at least half a year.
It's subject to automatic issue closing if there is no activity in the next 15 days.
Issue was closed because of inactivity.
If you think this is still a valid issue, please file a new issue with additional information.