Add Buidler to list of dev tools in build section. #42
Conversation
|
Happy to include buidler, but please make the formatting consistent with the rest of the listings.
|
| ### Buidler *A task runner for Ethereum smart contract developers* | ||
| - [buidler.dev](https://buidler.dev) | ||
| - [Github](https://github.com/nomiclabs/buidler) | ||
|
|
There was a problem hiding this comment.
Lines 67 to 71 should be moved above line 64, or is Buidler not a developer tool?
There was a problem hiding this comment.
It is, and the way I see it this is the structure I proposed:
Developer tools
Frameworks
Truffle
Embark
Waffle
Workflow automation
Buidler
Buidler is a task runner, not a development or testing framework, so I added a new category under Developer tools, same hierarchy level as Frameworks. I wasn't sure where else to put it.
What do you suggest?
There was a problem hiding this comment.
You're right. Actually the issue is that the Frameworks formatting is wrong.
IMO 'frameworks' which is probably one of the vaguest words in all of software should just be removed, and Buidler inserted under Developer tools so that we have:
Developer tools
Truffle
Embark
Waffle
Buidler
What do you think?
There was a problem hiding this comment.
I agree 100% about "frameworks", but I think the original intention was to have "Developer tools" as the top level category for all the developer tools, and then have more detailed categories inside. Maybe we could repeat the tools across several categories to communicate more precisely what they're good for? like
Developer tools
Testing libraries
Waffle
Truffle
Embark
Dapp development
Embark
Workflow automation
Buidler
Deployment
Etherlime
Truffle
Embark
Buidler
Linters
Solhint
I know that with the huge amount of features some of these tools have they'll be repeated a lot, but while redundant this feels like much better orientation for someone who's never used any of them.
What do you think? I'm also not against doing just one list without categories but I don't think that will last very long as all the dev tools are added
There was a problem hiding this comment.
At this point, I don't want to list things multiple times, or worry about how to design for another level of headings.
Going with the simplest solution for now.
I think it is the same format as the other listings.
|
Changed * into ðereum#42; because * is not visible on webpage
updated interface using optional lastUpdatedDate, but this should be hardened in the Front matter schema PR ethereum#42
Frontmatter typing
No description provided.