├── contributing.md
├── code-of-conduct.md
├── media
└── jamstack-full-logo.svg
└── README.md
/contributing.md:
--------------------------------------------------------------------------------
1 | # Contribution Guidelines
2 |
3 | Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md).
4 | By participating in this project you agree to abide by its terms.
5 |
6 | - Ensure your pull request adheres to the following guidelines:
7 | - Search previous suggestions before making a new one, as yours may be a duplicate.
8 | - You should of course have read or used the thing you're submitting.
9 | - Make an individual pull request for each suggestion.
10 | - Use the following format: `[name](link) - Description.`
11 | - Keep descriptions short and simple, but descriptive.
12 | - Start the description with a capital and end with a full stop/period.
13 | - Check your spelling and grammar.
14 | - Make sure your text editor is set to remove trailing whitespace.
15 | - Link additions should be added to the bottom of the relevant section.
16 | - New categories or improvements to the existing categorization are welcome.
17 | - Pull requests should have a useful title and include a link to the package and why it should be included.
18 |
19 | Thank you for your suggestion!
20 |
21 | ### Updating your PR
22 |
23 | A lot of times, making a PR adhere to the standards above can be difficult.
24 | If the maintainers notice anything that we'd like changed, we'll ask you to edit
25 | your PR before we merge it. There's no need to open a new PR,
26 | just edit the existing one. If you're not sure how to do that,
27 | [here is a guide](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md)
28 | on the different ways you can update your PR so that we can merge it.
29 |
30 | ## Attribution
31 |
32 | These Contribution Guidelines are adapted from the [Awesome Creative Coding Contribution Guidelines](https://raw.githubusercontent.com/terkelg/awesome-creative-coding/master/contributing.md).
33 |
--------------------------------------------------------------------------------
/code-of-conduct.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, gender identity and expression, level of experience,
9 | nationality, personal appearance, race, religion, or sexual identity and
10 | orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at hello@terkel.com. All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at [http://contributor-covenant.org/version/1/4][version]
72 |
73 | [homepage]: http://contributor-covenant.org
74 | [version]: http://contributor-covenant.org/version/1/4/
75 |
--------------------------------------------------------------------------------
/media/jamstack-full-logo.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | JAMstack: noun \’jam-stak’\
9 | Modern web development architecture based on client-side JavaScript, reusable APIs, and prebuilt Markup.
10 |
11 |
12 |
13 |
14 | This is a carefully curated list of awesome JAMstack resources.
15 |
16 |
24 |
25 | Want to contribute with some resource? Great! Please, read the contribution guidelines before contributing.
26 |
27 |
28 |
29 |
30 |
31 | ## Contents
32 |
33 | - [General](#general)
34 | - [Chats](#chats)
35 | - [Platforms](#platforms)
36 | - [Static Site Generators](#static-site-generators)
37 | - [CMS](#cms)
38 | - [API](#api)
39 | - [Authentication](#authentication)
40 | - [Comments](#comments)
41 | - [Forms](#forms)
42 | - [E-commerce](#e-commerce)
43 | - [Search](#search)
44 | - [Database](#database)
45 | - [Automation](#automation)
46 | - [Serverless](#serverless)
47 | - [Videos](#videos)
48 | - [Tutorials](#tutorials--articles)
49 | - [Podcasts](#podcasts)
50 |
51 | ---
52 |
53 | ## General
54 |
55 | - [JAMstack](https://jamstack.org/)
56 | - [JAMstack resources](https://jamstack.org/resources/) - Videos and articles about JAMstack
57 | - [the New Dynamic](https://www.thenewdynamic.org/) - Pick up tools in our Directory to work with the JAMstack. Browse our showcase and get inspired
58 |
59 | ## Chats
60 |
61 | - [Appernetic Gitter Chat](https://gitter.im/appernetic/issues)
62 | - [JAMstack Gitter Chat](https://gitter.im/jamstack/community)
63 | - [Netlify Gitter Chat](https://gitter.im/netlify/community)
64 | - [NetlifyCMS Gitter Chat](https://gitter.im/netlify/NetlifyCMS)
65 | - [the New Dynamic Slack](https://join.slack.com/t/thenewdynamic/shared_invite/enQtMjkwNjYwNTY0NjkxLWI1NDhlNjZkZjA5ZGJmODE1OThiMjkwN2ZkMzE1YjEwN2YwNWUxYTNjZTUxMGQ2MzU3NWQ0YmVjNGU1NTkxMDk)
66 |
67 | ## Platforms
68 |
69 | - [Appernetic](https://appernetic.io) - Visual content management for static web sites, with Hugo and Github Pages
70 | - [Netlify](https://netlify.com) - All-in-one platform for automating modern web projects
71 |
72 | ## Static Site Generators
73 |
74 | - [Gatsby](https://gatsbyjs.org) - Blazing-fast static site generator for React
75 | - [Next.js](https://nextjs.org/) - Lightweight framework for static and server-rendered applications
76 | - [Hugo](https://gohugo.io) - Hugo is a static site generator written in Go
77 | - [Jekyll](https://jekyllrb.com) - Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites
78 | - [Hexo](https://hexo.io) - A fast, simple & powerful blog framework, powered by Node.js
79 | - [Metalsmith](https://metalsmith.io) - An extremely simple, pluggable static site generator
80 | - [Phenomic](https://phenomic.io/) - A modular website compiler
81 |
82 | *For a more complete list see [StaticGen](https://www.staticgen.com/).*
83 |
84 | ## CMS
85 |
86 | - [Contentful](https://contentful.com) - Content infrastructure for digital teams
87 | - [NetlifyCMS](https://netlifycms.org/) - Famous digital art blog
88 | - [ButterCMS](https://buttercms.com/) - Headless CMS and Content API
89 | - [Scrivito](https://scrivito.com) - Cloud-based JavaScript CMS built for digital agencies and medium to large-sized businesses
90 | - [GraphCMS](https://graphcms.com) - The GraphQL Headless CMS
91 | - [Prismic](https://prismic.io) - Headless API CMS for both developers and marketers
92 | - [Siteleaf](https://siteleaf.com) - A friendly CMS for your static site
93 | - [DatoCMS](https://datocms.com) - The API-based CMS your editors will love
94 | - [Prose](https://prose.io) - Prose is a content editor for GitHub designed for managing websites
95 | - [Tipe](https://tipe.io) - Next Generation API-first CMS
96 | - [Forestry](https://forestry.io) - Headless CMS for static sites built with Hugo and Jekyll
97 | - [Coisas](https://github.com/fiatjaf/coisas) - A client-side CMS for editing GitHub Markdown (and other) files
98 | - [Cockpit](https://getcockpit.com/) - A self-hosted headless and api-driven CMS
99 | - [HeadlessCMS](https://headlesscms.org/) - A List of Content Management Systems for JAMstack Sites
100 |
101 | ## API
102 |
103 | ### Authentication
104 |
105 | - [Auth0](https://auth0.com/) - Single sign on and token based authentication
106 | - [Netlify Identity](https://www.netlify.com/docs/identity/) - Brings a full suite of authentication functionality, backed by the [GoTrue API](https://www.gotrueapi.org)
107 |
108 | ### Comments
109 |
110 | - [Disqus](https://disqus.com) - Global comment system that improves discussion on websites and connects conversations across the web
111 | - [Facebook Comments](https://developers.facebook.com/docs/plugins/comments) - The comments plugin lets people comment on content on your site using their Facebook account
112 |
113 | ### Forms
114 |
115 | - [Netlify Forms](https://www.netlify.com/docs/form-handling/) - Built-in form handling on building time by parsing HTML files directly at deploy time
116 |
117 | ### E-commerce
118 |
119 | - [Flatmarket](https://github.com/christophercliff/flatmarket) - Flatmarket is a free, open source e-commerce platform for static websites
120 | - [GoCommerce](https://www.gocommerceapi.org) - A headless e-commerce for JAMstack sites
121 | - [Snipcart](https://snipcart.com/) - A powerful shopping cart platform for developers
122 | - [Moltin](https://moltin.com/) - eCommerce API for developers
123 |
124 | ### Search
125 |
126 | - [Algolia](https://www.algolia.com/) - The most reliable platform for building search into your business
127 | - [Lunr](https://lunrjs.com/) - Search made simple (on frontend)
128 |
129 | ### Database
130 |
131 | - [GraphQL](https://graphql.org) - Query language for APIs and a runtime for fulfilling those queries with your existing data
132 | - [Graphcool](https://graph.cool) - Open-source and self-hosted backend-as-a-service to develop serverless GraphQL backends
133 |
134 | ### Automation
135 |
136 | - [Zapier](https://zapier.com/) - Trigger actions connecting more than 1000 apps together
137 |
138 | ## Serverless
139 |
140 | - [Netlify Functions](https://www.netlify.com/docs/functions/) - Netlify lets you deploy Lambda functions without an AWS account, and with function management handled directly within Netlify
141 | - [Amazon Lambda](https://aws.amazon.com/lambda/) - Lets you run code without provisioning or managing servers
142 | - Microsoft Azure
143 | - [Azure Functions](https://docs.microsoft.com/en-us/azure/azure-functions/) - Serverless compute service that enables you to run code on-demand without having to explicitly provision or manage infrastructure
144 | - [Azure Logic Apps](https://docs.microsoft.com/en-us/azure/logic-apps/) - Simplifies building automated scalable workflows that integrate apps and data across cloud services and on-premises systems
145 | - Google Cloud
146 | - [App Engine](https://cloud.google.com/appengine/) - Serverless application that completely abstracts away infrastructure so you focus only on code
147 | - [Cloud Functions](https://cloud.google.com/functions/) - Serverless environment to build and connect cloud services
148 | - [Cloud Datastore](https://cloud.google.com/datastore/) - Highly-scalable NoSQL database with automatic sharding and replication
149 | - [Cloud Storage](https://cloud.google.com/storage/) - Geo-redundant object storage for high QPS needs
150 | - [Cloud Pub/Sub](https://cloud.google.com/pubsub/) - Geo-redundant real-time messaging for all message sizes and velocities
151 | - [Apigee](https://apigee.com/) - Enterprise API management for multi-cloud environments
152 | - [Endpoints](https://cloud.google.com/endpoints/) - API management apps built on Google Cloud
153 | - [Cloud Dataflow](https://cloud.google.com/dataflow/) - Serverless stream and batch data processing service
154 | - [BigQuery](https://cloud.google.com/bigquery/) - Serverless data warehousing services that help you to deploy advanced cloud data warehousing solutions for your enterprise
155 | - [Cloud ML Engine](https://cloud.google.com/ml-engine/) - Serverless machine learning services that automatically scales built on custom Google hardware (Tensor Processing Units)
156 | - [Serverless](https://serverless.com/) - Toolkit for deploying and operating serverless architectures
157 |
158 | *For a more complete list see [Awesome Serverless](https://github.com/pmuens/awesome-serverless).*
159 |
160 | ## Videos
161 |
162 | - [The New Front-end Stack. Javascript, APIs and Markup](https://vimeo.com/163522126) - Matt Biilmann
163 | - [Rise of the JAMstack](https://www.youtube.com/watch?v=uWTMEDEPw8c) - Mathias Biillman
164 | - [Git-based or API-driven CMS](https://www.youtube.com/watch?v=KX4G49ZrvY0) - Chris Macrae
165 |
166 | ## Tutorials / Articles
167 |
168 | - [Getting Started with Gatsby and Cockpit — Part 1 of 2](https://blog.ginetta.net/getting-started-with-gatsby-and-cockpit-part-1-of-2-d86871932d44)
169 | - [Creating Static E-commerce site with GatsbyJs](https://medium.com/@pinku1/creating-static-e-commerce-site-with-gatsbyjs-a349d7e022a)
170 | - [For Static Sites, There’s No Excuse Not to Use a CDN](https://forestry.io/blog/for-static-sites-theres-no-excuse-not-to-use-a-cdn/)
171 | - [E-commerce front-end for Vue.js, Nuxt.js and Snipcart](https://www.sanity.io/blog/e-commerce-vue-nuxt-snipcart)
172 | - [Building Paul The Octopus](https://www.tomango.co.uk/thinks/paul-the-octopus-2018/)
173 | - [JAMstack and Netlify: Do We really need another buzzword?](https://noti.st/philhawksworth/qp7jZC/jamstack-and-netlify-do-we-really-need-another-buzzword)
174 | - [The JAMstack Startup Landscape](https://medium.com/@CRVVC/the-jamstack-startup-landscape-c06cc3cdb917)
175 | - [How I built my blog using Gatsby and Netlify](https://blog.pavsidhu.com/how-i-built-my-blog-using-gatsby-and-netlify/)
176 | - [Developer's Guide to Headless E-Commerce](https://snipcart.com/blog/headless-ecommerce-guide)
177 | - [Handling Static Forms, Auth & Serverless Functions with Gatsby on Netlify](https://snipcart.com/blog/static-forms-serverless-gatsby-netlify)
178 | - [JAMstack for Clients: Benefits, Static Site CMS, & Limitations](https://snipcart.com/blog/jamstack-clients-static-site-cms)
179 | - [Exploring Netlify CMS, a React & Git-Based Content Management System](https://snipcart.com/blog/netlify-cms-react-git-workflow)
180 | - [JAMstack PWA — Let’s Build a Polling App. with Gatsby.js, Firebase, and Styled-components Pt. 1](https://medium.com/@UnicornAgency/jamstack-pwa-lets-build-a-polling-app-with-gatsby-js-firebase-and-styled-components-pt-1-78a03a633092)
181 |
182 | ## Podcasts
183 |
184 | - [JAMstack Radio](https://www.netlify.com/tags/podcast/)
185 |
186 | ## License
187 |
188 | [](https://creativecommons.org/publicdomain/zero/1.0/)
189 |
--------------------------------------------------------------------------------