-
-
Notifications
You must be signed in to change notification settings - Fork 27.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add WordPress-Gatsby #1627
Add WordPress-Gatsby #1627
Conversation
… backend technology. There is no category in this list, where it would fit. So next to JAMStack, it seems to make most sense, as it is a JAMStack stack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a period at the end of the list description
Descriptions of resources in the list would be very helpful. |
This is done, for the one description I had.
This I guess makes sense for all the Technology-Based links. I feel the Tutorials are mostly self-explanatory. What do you think?
Anything else missing besides the descriptions? |
In the Starters & Themes section, provide a brief description of what a Starter and Theme is. This will both signpost beginners and help the project gain traction. At the beginning of the README include a simple explanation of what headless CMS is and/or the benefits of this approach/architecture. |
I added the descriptions for themes, starters and about static-site-generators + headless CMS. Thanks for info. |
I added descriptions to all of the resources. Thanks for mentioning. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks much better to me.
GatsbyJS => Gatsby |
I think the readme intro (in your repo) could be clearer about the benefit of combining WordPress and Gatsby. |
Co-Authored-By: Sindre Sorhus <sindresorhus@gmail.com>
Wasn't sure how to name it, as Gatsby is using different approaches on their site. So you would change everything to Gatbsy and not GatsbyJS? Or the other way around?
I'll add a paragraph about it, under the description of headless CMS and static site generators. Wouldn't explain it too much though, as I think it is very biased and the pros and cons are depending on a lot of things. I would rather add some resources, who talk about it, so everyone can figure out themselves, if it is the right approach for their usecase. |
@sindresorhus I changed everything to Gatsby now instead of GatsbyJS and added the paragraph about the benefit of the approach. Also committed your suggested change. Now lets hope this list has all the awesomeness it needs now :) |
Looks good now :) |
https://github.com/henrikwirth/awesome-wordpress-gatsby
A curated list of resources about WordPress as a headless CMS with Gatsby
PRs reviewed:
#1622
#1623
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
Add Name of List
.Add Swift
Add Software Architecture
Update readme.md
Add Awesome Swift
Add swift
Adding Swift
Added Swift
- [iOS](…) - Mobile operating system for Apple phones and tablets.
- [Framer](…) - Prototyping interactive UI designs.
- [iOS](…) - Resources and tools for iOS development.
- [Framer](…)
- [Framer](…) - prototyping interactive UI designs
Requirements for your Awesome list
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-lint
on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.Mobile operating system for Apple phones and tablets.
Prototyping interactive UI designs.
Resources and tools for iOS development.
Awesome Framer packages and tools.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
awesome-name-of-list
.awesome-swift
awesome-web-typography
awesome-Swift
AwesomeWebTypography
# Awesome Name of List
.# Awesome Swift
# Awesome Web Typography
# awesome-swift
# AwesomeSwift
awesome-list
&awesome
as GitHub topics. I encourage you to add more relevant topics.Contents
, notTable of Contents
.unicorn
.contributing.md
. Casing is up to you.Example:
- [AVA](…) - JavaScript test runner.
Node.js
, notNodeJS
ornode.js
.You can still use Travis for list linting, but the badge has no value in the readme.
Inspired by awesome-foo
orInspired by the Awesome project
kinda link at the top of the readme. The Awesome badge is enough.Go to the top and read it again.