Starter showcase card layout update #8117
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KyleAMathews
force-pushed
the
master
branch
5 times, most recently
from
fc4ca3e
to
2116fff
Compare
|
Hi @riencoertjens! Now that the first push for the starter library is out, any interest in revisiting/updating this PR? |
|
yes, I'll do it this weekend... |
* Extend the docs on `sourceNodes`. Expanding the docs to be a bit more verbose and explain in more depth what this API does. Based on a discussion with @pieh. * Update api-node-docs.js
Soo in March this year @spences10 opened this PR: #4139 But it never got added to the sidebar 😛 Therefore I added unknowingly this PR: #8876 ----------- This PR exposes the Linux doc to the sidebar and puts a link to this doc on the windows doc.
This changes `__experimentalThemes` from the following
```
__experimentalThemes: [['theme-name', optionsObject]]
```
to match the plugins spec
```
__experimentalThemes: [{
resolve: 'theme-name',
options: {}
}]
```
* This is to reduce the number of user-visible config styles.
* There will be a future change to be fully compatible with the [load plugins](https://github.com/gatsbyjs/gatsby/blob/390803c8f679e53d398d40b9535c1a8784380a48/packages/gatsby/src/bootstrap/load-plugins/load.js#L37-L85) functionality (defines a `themes/` directory for local themes and handles absolute paths, etc). This change is meant to match the plugins API spec superficially so that the blogpost #9517 doesn't have syntax incompatible with the future.
* change banner text to promote webinar * add link to v1 docs in migration guide * Fix quotation marks * Rm „fallback“ banner content, mark prop as required
We will be getting those for a while :( (as PR that remove usage was used on branch before the linting change). This currently fails linting, because `Link` is defined but not used
…#9606) * feat(www): add lead scroll to horizontal scrollers feat(www): setup IntersectionObserver feat(www): add initial lead animation to horizontal scrollers on Ecosystem page fix(www): remove intersection-observer polyfill fix(www): change fake scrolling to 'only left' ver fix(www): make 'fake scroll' not fake * fix(www): add code formating * fix(www): add code formating and fix eslint errors * fix(www): add small delay for lead animation * fix(www): decrease dalay to 250ms * refactor(www): refactor easy function * fix(www): revert to overriden proper Ecosystem board texts * fix(www): remove unused CSS style
* chore: create folder * docs: add gatsby for apps post * docs(blog): add gatsby for apps blog post * chore: update * chore: remove old post * chore: add content * chore: add bullet points (google apps messed formatting up) * docs: hopefully finish blog post * chore: remove image * chore: remove comma * chore: address feedback * chore: add top level header
<!-- Q. Which branch should I use for my pull request? A. Use `master` branch (probably). Q. Which branch if my change is a bug fix for Gatsby v1? A. In this case, you should use the `v1` branch Q. Which branch if I'm still not sure? A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :) Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2. Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/ -->
as it says on the tin :)
Fixes issue #9766 <!-- Q. Which branch should I use for my pull request? A. Use `master` branch (probably). Q. Which branch if my change is a bug fix for Gatsby v1? A. In this case, you should use the `v1` branch Q. Which branch if I'm still not sure? A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :) Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2. Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/ -->
<!-- Q. Which branch should I use for my pull request? A. Use `master` branch (probably). Q. Which branch if my change is a bug fix for Gatsby v1? A. In this case, you should use the `v1` branch Q. Which branch if I'm still not sure? A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :) Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2. Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/ --> One of two changes for #9757 Second change will be a complete guide for ButterCMS. I'll open a new PR for that.
seems like current (bit whacky) patterns don't play nice on windows for some reason, let's try different ones note - there is currently unrelated lint error in `www` so linting should fail - but it should have 1 error instead of thousands of errors on azure/appveyor - with this #9780 should be clear
- Added "Headless CMS" to entries appropriately - Removed minor tags that create extra noise (Recompose, Prettier, Lint-Staged, TSLint, Tags) and removed them or put them into "Linting". Especially considering that almost all starters have ESLint and Prettier. "Linting" would mean for me that this starter is especially focused on that or has something fancy - Removed invalid Styling tag
* refactor run-sift * update yarn.lock
- gatsby-cli@2.4.5 - gatsby-codemods@1.0.7 - gatsby-dev-cli@2.4.7 - gatsby-image@2.0.20 - gatsby-plugin-catch-links@2.0.7 - gatsby-plugin-cxs@2.0.2 - gatsby-plugin-google-gtag@1.0.4 - gatsby-plugin-layout@1.0.8 - gatsby-plugin-manifest@2.0.8 - gatsby-plugin-netlify-cms@3.0.7 - gatsby-plugin-netlify@2.0.4 - gatsby-plugin-offline@2.0.13 - gatsby-plugin-page-creator@2.0.4 - gatsby-plugin-remove-trailing-slashes@2.0.5 - gatsby-plugin-sass@2.0.4 - gatsby-remark-autolink-headers@2.0.11 - gatsby-source-contentful@2.0.13 - gatsby-source-drupal@3.0.8 - gatsby-source-filesystem@2.0.8 - gatsby-source-mongodb@2.0.8 - gatsby-source-wordpress@3.0.13 - gatsby-transformer-csv@2.0.4 - gatsby-transformer-javascript-frontmatter@2.0.4 - gatsby-transformer-pdf@1.0.14 - gatsby-transformer-remark@2.1.12 - gatsby-transformer-screenshot@2.0.7 - gatsby-transformer-xml@2.0.4 - gatsby-transformer-yaml@2.1.5 - gatsby@2.0.41
Adjusting feature list according to the [renaming of modular content elements to linked items](https://developer.kenticocloud.com/v1/reference#linked-content). <!-- Q. Which branch should I use for my pull request? A. Use `master` branch (probably). Q. Which branch if my change is a bug fix for Gatsby v1? A. In this case, you should use the `v1` branch Q. Which branch if I'm still not sure? A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :) Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2. Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/ -->
Hi, This is a fix for issue as discussed here #10159 (comment). prevent loop if the object is of type function
- babel-preset-gatsby@0.1.6 - gatsby-plugin-feed@2.0.11 - gatsby-plugin-react-helmet@3.0.4 - gatsby-source-wordpress@3.0.17 - gatsby@2.0.60
|
Hi @riencoertjens :) Do you have the time to update your PR? Otherwise I could tackle this. Please let me know, thanks 👍 |
|
go for it @LekoArts ! |
<!-- Q. Which branch should I use for my pull request? A. Use `master` branch (probably). Q. Which branch if my change is a bug fix for Gatsby v1? A. In this case, you should use the `v1` branch Q. Which branch if I'm still not sure? A. Use `master` branch. Ask in the PR if you're not sure and a Gatsby maintainer will be happy to help :) Note: We will only accept bug fixes for Gatsby v1. New features should be added to Gatsby v2. Learn more about contributing: https://www.gatsbyjs.org/docs/how-to-contribute/ -->
A Gatsby starter for making notes on different subjects and topics
This pr, adds all the missing dependencies used on the gatsby code base to the package.json the dependencies and the versions were obtained by doing a dry run of yarn PnP. It adresses #10245
… fields (#10228) The "Beta" Rich Text field for contentful was breaking when trying to load data into GraphQL that has circular references. Using a safe stringify method prevents it falling over and instead just prevents the referenced circular data from being available.
This reverts commit ead9d54.
…out-update' into starter-showcase-card-layout-update
|
Sorry, my git/I messed up the rebase. There were so many conflicts ... |
amberleyromo
pushed a commit
that referenced
this pull request
Dec 5, 2018
Follow-Up PR of #8117 Closes #8097 Preview: 
gpetrioli
pushed a commit
to gpetrioli/gatsby
that referenced
this pull request
Jan 22, 2019
Follow-Up PR of gatsbyjs#8117 Closes gatsbyjs#8097 Preview: 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.