stackshareio / awesome-stacks Goto Github PK

I think we should see a few .NET stacks in this beautiful list too. If someone adds some good stack recommendations of .NET (like .NET Core + Vue.js) I'll be very appreciated.

Part 1: #46

awesome-lint results (27 errors)

• 1:1 Missing or invalid Table of Contents remark-lint:awesome/toc
• 27:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 29:3 Invalid list item link URL remark-lint:awesome/list-item
• 30:3 Invalid list item link URL remark-lint:awesome/list-item
• 31:3 Invalid list item link URL remark-lint:awesome/list-item
• 32:3 Invalid list item link URL remark-lint:awesome/list-item
• 34:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 144:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 125:30 Link to https://awesomestacks.dev/nuxtjs-typescript-docker is dead remark-lint:no-dead-urls
• 162:75 List item description must end with proper punctuation remark-lint:awesome/list-item
• 204:136 List item description must end with proper punctuation remark-lint:awesome/list-item
• 205:139 List item description must end with proper punctuation remark-lint:awesome/list-item
• 206:69 List item description must end with proper punctuation remark-lint:awesome/list-item
• 220:83 List item description must end with proper punctuation remark-lint:awesome/list-item
• 221:91 List item description must end with proper punctuation remark-lint:awesome/list-item
• 222:107 List item description must end with proper punctuation remark-lint:awesome/list-item
• 242:22 Link to https://awesomestacks.dev/using-vue-with-electron is dead remark-lint:no-dead-urls
• 277:27 List item link and description must be separated with a dash remark-lint:awesome/list-item
• 278:34 List item link and description must be separated with a dash remark-lint:awesome/list-item
• 296:129 List item description must end with proper punctuation remark-lint:awesome/list-item
• 325:78 List item description must end with proper punctuation remark-lint:awesome/list-item
• 349:111 List item description must end with proper punctuation remark-lint:awesome/list-item
• 289:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 371:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 415:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 419:1 Don’t use multiple top level headings (7:1) remark-lint:no-multiple-toplevel-headings
• 419:1 License section must be at heading depth 2 remark-lint:awesome/license

There is no stack for MEAN. You can add mean.

• Keep or remove Contents section? (See #11)
• Rename serverless-stack.com ↗ to Serverless ↗
• Remove React Native for the F8 App ↗? via @yonasb
• Add Good vs Bad stack examples to CONTRIBUTING.md
• Fix url https://awesomestacks.dev/victor-hugo > victor-hugo-boilerplate
• Title Case
• Remove "stack" from Ethereum DApp stack ↗
• hugo-algolia link fix
• On ProductHunt button

I think the Serverless stack is too opinionated / specific. It’s mostly promoting AWS. The Serverless framework (which is awesome by the way) is only supporting JavaScript. I suggest changing the name of this stack to AWS Serverless. There can be other stacks for Google, Azure, and others.

Is it possible to contribute Vue with three.js library ?

via https://cards-dev.twitter.com/validator

@dzello is that possible?

Need to go over this PR and make sure all of the boxes are checked before submitting a PR.

• Awesome Lint
• Remove Netlify Button
• Add CC0 to bottom of README

Others

• Has been around for at least 30 days.
• It's the result of hard work and the best I could possibly produce.
• Non-generated Markdown file in a GitHub repo.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Includes a project logo/illustration whenever possible.
• Either centered, fullwidth, or placed at the top-right of the readme. (Example)
• The image should link to the project website or any relevant website.
• The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
• Should be placed on the right side of the readme heading.
• Can be placed centered if the list has a centered graphics header.
• Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
• Should only have one level of nested lists, preferably none.
• Has an appropriate license.
  • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  • WTFPL and Unlicense are not acceptable licenses.
  • If you use a license badge, it should be SVG, not PNG.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
• Has consistent formatting and proper spelling/grammar.
• The link and description are separated by a dash.
• Example: - AVA - JavaScript test runner.
• The description starts with an uppercase character and ends with a period.
• Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.

Reach out to Patrick, ask if he wants to submit a PR for https://github.com/PatrickJS/angular-starter

I am wondering why MEAN (MongoDB, ExpressJS, Angular, and NodeJS) stack is not listed? is it not popular enough? or what is the reason?