Adds a loud banner that calls out for supporting bower#175
Adds a loud banner that calls out for supporting bower#175Potherca wants to merge 2 commits intobower:masterfrom Potherca:callout-for-support
Conversation
|
I find it little too obtrusive as well |
|
The rationale is, in order to combat what is turning into a small shit storm, to fight fire with fire. So loud/obtrusive may be called for. That said, I am not a designer and have poor (visual) taste. So "much" may indeed be "too much". I do feel, however, that some manner of callout on the website is needed to make clear that bower is not dead. This in part because the spread of FUD on Twitter continues and all we have in order to combat it is a line in a readme file. |
|
In a week nobody will remember, that's how the Internet works.. Besides FUD is neither good or bad. It just brings attention to Bower so we've got few people interested in helping. If someone will find NPM better fit because of it, it's cool. I have good experience with npm 2.x for front-end dev (3.x has its issues). There's declaration form at the top of README: https://github.com/bower/bower btw. I've already accepted a PR with link to BountySource: #174 |
|
Regardless of the outcome, thank you for your time and comments. Much appreciated! |
|
:) bower is not dead. I far prefer it to NPM for front end. Thanks for your support! |
Adding to the discussion about making the need for support more clear, I thought this might be helpful.
Personally I don't think that adding a rather obtrusive banner to the banner website is a "Bad Idea"TM. It makes it very clear how badly support is needed and how much the community at large is falling Bower in offering this.
Feel free to close/ignore this PR if you deem it to be too gaudy. Just consider it the 2 cents of someone who feels talk is cheap (only slightly more so than pull-requests).