Starter showcase card layout update #8117

@pieh

* 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

@spences10

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

as it says on the tin :)

Fixes issue #9766

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

…9792)

- 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).

Construct webpack hmr path relative to the request origin path to prevent url construction issues when accessing from local ip or any other ip that may be mapped to the dev server. This PR makes following changes to `getHmrPath()` method in `packages/gatsby/src/utils/webpack.config.js` - Always use the relative path `/` - Getting rid of manual url construction with protocol, hosts, ports etc as the relative path will automatically take care of this construction

- gatsby@2.0.42

We only added it to the v2 site in order to add the `#v2` at the end so we forgot to clean things up again after

Fixes broken link on the [Submit to Creator Showcase](https://www.gatsbyjs.org/docs/submit-to-creator-showcase/) page, just below the title. Closes #9761

Anywhere in Gatsby where a graphql resolver returns a node, we need to declare a dependency from the node to the page `context.path`. This code is littered throughout `schema`. Eventually, it would be great to figure out an alternative way to declare these dependencies, since causing side effects in query resolvers isn't ideal, but in the mean time, this PR cleans up the code a bit by introducing a resolver middleware called `pageDependencyResolver`. It executes a given resolver and then creates a page dependency. Another alternative would be to use [graphql-middleware](https://github.com/prisma/graphql-middleware) to run this on all field resolvers. Perhaps another day.

While reading the tutorial doc, I noticed one line that appeared to be missing the title markup.

- gatsby-plugin-google-gtag@1.0.5 - gatsby@2.0.43

…9829) Updates `gatsby-plugin-catch-links` to handle SVG anchors. Fixes #9816

- gatsby-plugin-catch-links@2.0.8

better safe than sorry

@pieh

This approach to displaying GraphQL compilation errors in the browser console utilizes the WebSocket connecting node running gatsby package responsible for executing GraphQL queries and the cache loaded and used on the browser side (thanks @pieh for helping in this). #5234

- gatsby@2.0.44

* Filter for v2 starters by default. #7900 * WIP * fix reset all filters issue * move out default search option * wip * refactor to use render prop * fix filtersApplied for metadata * pr refactor * linting

@pieh

* Add guide for programmatically creating pages closes #8841 * Add an Other Resources section * Address comments from review (@pieh) * activate docs sidebar link

Closes #6771

The patch entry should no longer be necessary (after v4 I think), so I should be safe to remove it. https://github.com/gaearon/react-hot-loader#no-patch-required

minor typo fix

I added a blog post about deploying a static Gatsby app to Heroku to the list of Gatsby tutorials.

…NSHOT_PLACEHOLDER (#9851)

- gatsby-transformer-screenshot@2.0.8 - gatsby@2.0.45

- Updated dead link "/audit-with-lighthouse/" to "/docs/audit-with-lighthouse/" - Updated dead link "/add-a-manifest-file/" to "/docs/add-a-manifest-file/"

`PWA` is the right tag

@moonmeister

…s links (#7256) Fixes #5887 /cc @seaneking @moonmeister I'd like to have gatsby-plugin-manifest to generate apple-touch-icon meta tags (links) for me. Would it be simple enough to generate tags under the same rules as for favicon (only when the icon is being generated by the plugin)? This has been required to be a new major release, but is that v2 (still in beta) or v3? The initial commit datakurre@4cf3ba4 should be the smallest possible change, but I'd probably like to move the code in a separate module where `withPrefix` is passed as a function argument and could be mocked in tests and make them simpler. * [x] discussion * [x] tests * [x] docs update?

This closes #9827

Introduce gatsby themes to make people aware that the feature is experimentally merged and progressing.

Added typography and react-typography to the gatsby-plugin-typography install note, because these two peer dependencies need to be installed as well. Same as on the package overview [here](https://www.gatsbyjs.org/packages/gatsby-plugin-typography/).

My site is already added to showcase. I published the source code so I added information.

I found a unused argument(`createnode`) so I removed.

Update the file title for templates/blog-post.js block code.

My first draft for the docs. Appreciate feedback if there is anything that is incorrect, can be improved or additional content that could be added.

fix wordpress column in feature comparison page: ref #2444 (comment)

Hi all, we built our company site with Gatsby, Contentful and Netlify! Thanks for building such an amazing ecosystem ❤️

Syntax Highlighting

Another refactoring! The plus side of all these is more readable code (hopefully), but they're mostly to ease the loki integration. This one renames a lot of the vars/functions in `build-node-connections` so they're consistent with the actual graphql types and field class names as per https://graphql.org/graphql-js/type/#graphqlobjecttype Another benefit of this refactor is the ability to create types (connections in this case) one by one instead of having to do them as a whole batch. This will be eventually needed for incremental builds Update: I slipped a refactor to `build-node-types` in as well.

- gatsby-plugin-manifest@2.0.9 - gatsby-source-contentful@2.0.14 - gatsby@2.0.46

@shannonbux

Following [suggestions](#9795 (comment)) from @shannonbux to improve `unit-testing.md` further

A bit more information in the Netlify part.

## Summary Redux 4 has been released for a while. Shall we update the dependency? I've already tested the change in my fork and nothing is breaking. ### Motivation Redux 4 has updated its TypeScript bindings. Personally, I prefer the new version much. Putting it aside, Redux 4 has es modules support and dropped its dependency on `lodash`. Hence, it can make the bundle smaller. close #8265

Improved markdown - for correct displaying link

* Add Vets Who Code to showcase * yaml error

- gatsby-plugin-react-helmet@3.0.2 - gatsby@2.0.47

* Improved headers and clarity in tutorial part zero * Further simplify headings * Improve Git section * Improve the summary * Add optional link explaining git * Remove other reference to learn about git * Fix titles and links to match new headings * Clarify that git only needs to be installed to use Gatsby * Mention that the git handbook also explains Github * Revert "Fix titles and links to match new headings" This reverts commit 511bc37. * Revert the headings back to having verbs * Reword references to Gatsby CLI to make it clear it is not the only Gatsby CLI * Change 'Create a Gatsby site' heading back * Fix title to match heading * Clarify git sentence * Add missing space

current implementation of using `json-stream-stringify` is causing a lot of problems and I think this should be reverted - see #9370 (comment) shortly put - this does help with not getting OOM, but it essentially make `.cache/redux-state.json` to not work at all

…#9903) I've noticed the Readme of gatsby-plugin-offline is out of sync with the actual defaults from its gatsby-node.js. This commit fixes this by copying the options object from gatsby/packages/gatsby-plugin-offline/src/gatsby-node.js into this Readme.

- gatsby-plugin-offline@2.0.14 - gatsby@2.0.48

Updated starters.yml by adding Gatsby-Tutorial-Starters.

Simple change that will let us run `yarn run publish` even if packages don't exist.

…re menu by clicking outside of it (#9620)

…URI format (#9835) Description of the issue #9834 (If this approach is correct, I could add a test for this case)

The link is now directed where it is supposed to

@AVivero

## PR description: - Add new gatsby starter that provides multiple technologies out of the box, like Redux, Sass and Bootstrap, gatsby-redux-starter by @AVivero.

* feat(www): add Ecosystem section to Homepage feat(www): homepage WIP wip feat(www): finish sections style for mobile feat(www): add Ecosystsem featured items to Hompage feat(www): homepage ecosystem section styling WIP feat(www): add arrow to action button * fix(www): fix code formating * fix(www): fix code formating and eslint errors * fix(www): fix hovering effect on Featured Item * fix(www): fix hovering effect sequel * fix(www): fix hover bug * fix(www): update texts (intro & link labels) * feat(www): add scroller observer to Home page * refactor(www): use imported scrollers observer * fix(www): change link labes on Ecosystem page * fix(www): fix some small style issues * refactor(www): refator combineEcosystemFeaturedItems and reorder some css properties * refactor(www): remove width setting from scroller container * fix(www): update featured starters * fix(www): update featured starters * refactor(www): add starter/plugins colors to the palette * fix(www): remove unused props * fix(www): fix color value in the palette

…ively (#9923) Fixes #9415 This PR leverages Workbox's automatic caching when a resource is fetched, by creating a `<link>` prefetch element for each resource. This means we don't have to worry about whether the resource can be fetched with CORS or not, since the browser handles it automatically. I've also changed the runtime caching RegExps so that only paths with certain extensions are cached, but 3rd party resources with these extensions can now be cached.

- gatsby-plugin-layout@1.0.9 - gatsby-plugin-offline@2.0.15 - gatsby-source-drupal@3.0.9 - gatsby-source-wordpress@3.0.14 - gatsby@2.0.49

* fix: start ironing out browserslist issues * chore: make linter happy * chore: change to expected shape * refactor: move browserslist functionality into gatsby core

- babel-preset-gatsby@0.1.4 - gatsby@2.0.50

) Fix #9922 `ServerStyleSheet` should be specific to each pages in order to not pollutes the other. Theses changes removes the "global" stylesheet and use the `pathname` for identify each pages. --- Just a quick note for my first PR here: thanks to every contributors for this fantastic project! 👍

The total figure is much higher (6 million) than the monthly rate and quite a lot more impactful. So, it should make for a better listing on the readme :)

Add Dawn Labs' site to the showcase

) The default behavior of the `config` snippet is to send a pageview automatically; this is in contrast with the `exclude` option and the plugin tracks, on page load, even the excluded pages. This PR solve also the double pageview hits on page load too: the first is made by the default behavior and the second one by the `onRouteUpdate` event.

- gatsby-plugin-google-gtag@1.0.6 - gatsby-plugin-styled-components@3.0.2

…fy (#9680) Related to https://www.netlify.com/blog/2018/06/28/5-pro-tips-and-plugins-for-optimizing-your-gatsby---netlify-site/#4-get-your-service-workers-um-working Recommandation is not to cache service worker file : w3c/ServiceWorker#893

- gatsby-plugin-netlify@2.0.5

removes unnecessary closing bracket in code example

Removed "However, the " from the Project Env Vars description, it seems to reference the prior paragraph and is even less clear on the formatted .org doc page. While seemingly minor, as a newcomer I read it as an extension of the Windows related paragraph, and it caused some confusion.

…#9946) [Katex 0.10.0](https://github.com/KaTeX/KaTeX/releases/tag/v0.10.0) introduced tons of new features and fixes. I also updated the testing snapshots. :)

- gatsby-remark-katex@3.0.0

* Add "Babel Plugin Macros" guide * Run Prettier * Update babel-plugin-macros.md

* Add gatsby-starter-redux-firebase * Update starters.yml

I'm adding this in response to #9436 which brings up some of the confusion in the community around gtag.js vs anlaytics.js this PR hopes to clarify some of this confusion at the top of the README where no one can miss it.

@jlengstorf

…9933) /cc @jlengstorf

`nagivation` => `navigation`

Minor cleanup: - repair links in readme and index pointing to plugins/ instead of packages/ - add fitting name and description in package.json in style of using-gatsby-image: https://github.com/gatsbyjs/gatsby/blob/44db2f70967fd4408a86590899038c9f16eb4e5d/examples/using-gatsby-image/package.json#L2-L4 - babel-eslint to ^8.2.2 to remedy various compile errors in yarn and this more informative npm error: ```bash npm WARN eslint-config-react-app@3.0.0-next.66cc7a90 requires a peer of babel-eslint@^8.2.2 but none is installed. You must install peer dependencies yourself. ``` ...seems like we might could go higher: https://github.com/babel/babel-eslint/releases ...but this fixes the issues and allows me to build the example in yarn 1.12.3 and npm 6.4.1 on node 10.13.0.

I have a business case where we need to build gatsby page from drupal webiste that is protected by basicauth (Basic access authentication). Since axios already supports it I slightly modified the gatsby-source-drupal code to enable it. Please see if you can implement this feature as proposed in this PR or similar manner.

* Add notice about StaticQuery only working with JSX * Update docs/docs/static-query.md Co-Authored-By: Siilwyn <talk@selwyn.cc>

… in dev (#9497) In reference to #9436 @tylerbuchea

Sorry, didn't realize this had to be updated manually... Related to #9963

- gatsby-plugin-google-gtag@1.0.7 - gatsby-source-drupal@3.0.10

Add [Propapanda's](https://propapanda.eu/) site to showcase

This will also hide the status check. The general idea is that any PR whose branch starts with docs/, docs, blog/, or blog (e.g. docs-some-update, docs/some-update, etc.) will not run e2e tests. This seems pretty safe, and it's effectively opt-in. Unfortunately, we can't really enforce this standard, so it's more relying on the community to open up correct branch names, but if nothing else, it's valuable for us :shrug:

@lindawatkins

This adds a case study concerning Youfit's usage of Gatsby 💪 cc @lindawatkins

* change banner text, add outbound link tracking * linting

`relavant` => `relevant`

`infastructure` => `infrastructure`

some `entires` had photos => some `entries` had photos

Uses [Gatsby Source Meetup](https://github.com/phacks/gatsby-source-meetup) to gather Meetup.com information 😊 ![image](https://user-images.githubusercontent.com/2587348/48662868-b05ae980-ea88-11e8-8385-b2466fa7a4e5.png)

* Added amazing DexWallet to the gatsby showcase * Update sites.yml * Update sites.yml

Added two portfolio websites.

Hey, just noticed the term PRPL pattern in "SEO with Gatsby", turns out we actually have another doc page about that.

I added my blog [VS Code Rocks](https://vscode.rocks) to the site showcase

* Fix codeblock not rendering on markdown * Update local-https.md

… env vars (#10030) * fix: avoid leaking defined env vars when trying to access not defined env vars * test: add some testing for env var usage and leaking * add some comments to .env.production - it normally shouldn't be commited to repo

- gatsby@2.0.51

@phonoman

…er (#10007) if object or array is under field that starts with number it will cause graphql to fail with: ``` Error: Names must match /^[_a-zA-Z][_a-zA-Z0-9]*$/ but "6E0F4D382F504Ac5837DF8B7C8618485_2" does not. ``` to workaround it - prefix type name with `_` if it starts with number fixes #9950 /cc @phonoman

- gatsby@2.0.52

…#9993) Starter for Machine learning and scientific writing

) * Adding Narcan, ritual, truebill, smartling, clearme to showcase. * removing extra / * new line * Fixing indentantion * Changing titles

…llback src (#10041) Hey there. I was looking to add in AMP support for my pages, and noticed my Contentful images weren't able to be fetched properly because the URLs were invalid: ``` https//images.ctfassets.net/sk06mmp11skx/6FZZJDW2VGcEMM2sCyKI6w/32a06680dc5ba66c69925befe2ca6ace/costs-estimate.JPG ``` I noticed it was missing a `:`, as were the plugin's tests!. This resolves that.

- gatsby-remark-images-contentful@2.0.4

… API hooks (#10045) Those plugins rely on changes introduced in #9401 which was released in `gatsby@2.0.32` Ref: #9943 (comment)

- gatsby-plugin-jss@2.0.4 - gatsby-plugin-styled-components@3.0.3

…path whitelist (#9907) * Remove all no-cache code * Remove references to no-cache in offline plugin * Initial work on hybrid navigation handler * Refactor whitelist code to allow it to support onPostPrefetchPathname * Fix service worker detection * Fix IndexedDB race condition * Prevent race conditions + reset whitelist on SW update * Remove unnecessary API handler (onPostPrefetchPathname is called anyway) * Add debugging statements + fix some minor problems * Fix back/forward not working after 404 * Remove unneeded debugging statements * Bundle idb-keyval instead of using an external CDN * Update README * Backport fixes from #9907 * minor fixes for things I copy-pasted wrong * Refactor prefetching so we can detect success

…t release

- gatsby-plugin-offline@2.0.16 - gatsby@2.0.53

In the [Set Up Your Development Environment](https://www.gatsbyjs.org/tutorial/part-zero/) page, the link with label "Create a Gatsby site" (sidebar) refers to #create-a-site instead of #create-a-gatsby-site.

just to trigger dep reinstallation for our build runner

added a new website to showcase

…odule location. (#9986) The gatsby module resolve by require might not be the gatsby module that is executing. This can occur in mono-repo configurations. This will prevent the Redux store from receiving the job actions and the bootstrap process will complete without waiting for all images to be processed. This can cause the build to finish without all images being generated. Fixes #9984.

- gatsby-plugin-sharp@2.0.13 - gatsby-source-contentful@2.0.15 - gatsby-transformer-sqip@2.0.8

Adds https://tandem.co.uk to sites list

Closes: #7143 #9731

- gatsby@2.0.54

BREAKING CHANGE: html markup has been changed, high resolution image (img.gatsby-resp-image-image) is no longer nested inside span with low resolution placeholder (span.gatsby-resp-image-wrapper) - it's sibling of that span now. This might affect any custom styling that is applied to inline images

- gatsby-remark-images@3.0.0

…rker (#10075) Related to #9913

…it's not defiened (#10069) Not really sure how I go about submitting a PR here. This addition references issue #9977 Any guidance would be greatly appreciated.

- gatsby-plugin-manifest@2.0.10 - gatsby-plugin-offline@2.0.17 - gatsby-source-faker@2.0.2

Hello the Gatsby Team, First of all, thanks for the great product you're building, and the community around it. At [Monbanquet.fr](https://monbanquet.fr) we're using it for our main production website and it's been great so far, both in terms of user and developer experience. As it's my first PR here, hit me up if I did something wrong :) Cheers

Clicking the link below results in a not found page. Updated with the correct url <img width="733" alt="screen shot 2018-11-22 at 09 53 12" src="https://user-images.githubusercontent.com/1019869/48906947-7ac55000-ee3c-11e8-8ae9-45e88b5d733b.png"> <img width="1514" alt="screen shot 2018-11-22 at 09 52 22" src="https://user-images.githubusercontent.com/1019869/48906903-59646400-ee3c-11e8-9cac-cef544a127dc.png">

Needed to specify additional changes to serve production-optimized build and bind to correct port. These were the changes I needed to make in order to make a deployment work with Heroku, please let me know if this is helpful or not! 😄 🙏

* Update starters.yml * Update starters.yml

While working on loki (#9919), I've run into lots of fun edge cases to do with sorting. One is that some connection queries specify a sort order, but some returned fields have the same value for the sort field. The behavior here is undefined, but by default sift will order by the order they were added to Gatsby. While that's not a terrible default, it makes testing sift and loki compatibility hard, since loki has undefined ordering for this case. So this PR adds a specific secondary sort key to various `www` queries, mainly for the purpose of testing sift/loki compatibility, but also because it makes sense.

…evelop mode for easier debugging (#10083) Closes #6278 Sourcemaps are not currently working on gatsby v2. This fixes that on 1 string.

- gatsby@2.0.55

…tem section (#10096) Instead by `slug` we sort the starters by `stars` (DESC) - solving #10085 (comment)

**What kind of change does this PR introduce?**  This PR is related to the issue #10103 The PR helps to publish test results for reporting in Azure Pipelines. **Summary**   Azure Pipelines provides excellent reporting capabilities that can be leveraged by this PR. An example report is shown in the image below. ![image](https://user-images.githubusercontent.com/13175100/48767951-e8a73580-ecdd-11e8-8e6a-20d7767d7c1b.png) A screenshot for code coverage : ![image](https://user-images.githubusercontent.com/13175100/48795657-938e1280-ed23-11e8-88d0-bf94f610d774.png) **Does this PR introduce a breaking change?** No

…10123) fixes #6643 I also fell for this error before, sinc the original errors are swallowed (and fairly unclear too, because of the indirection). Adding validation was suggested in linked issue, so I went for this, since I didn't see any already used object validation like "ow" in use here.

The spacing in the dependency grid looked off to me, so I improved it a bit. Before: <img width="1064" alt="screenshot 2018-11-26 at 13 58 19" src="https://user-images.githubusercontent.com/541628/49015578-cbfa7a00-f183-11e8-9ee0-2452f8c1c83d.png"> After: <img width="1079" alt="screenshot 2018-11-26 at 13 58 07" src="https://user-images.githubusercontent.com/541628/49015584-d157c480-f183-11e8-86de-b7c20bee71f8.png">

Add licensing information to the `README` file which is a usual practice being followed 👍

* fix(www): Remove multiple entries from sites tags * Forgot the Paving tag * Update sites.yml

The bridge dependency for Babel 7's `babel-core` is `babel-core@7.0.0-bridge.0`

- gatsby-source-drupal@3.0.11 - gatsby-source-filesystem@2.0.9 - gatsby-source-wordpress@3.0.15

…y line highlighting (#9696) * feat: allow highlight directives in prismjs plugin Heavily inspired by DSchau#2 * fix: Fix multiline plain-text for directives * tests: test highlight-range directive * Add built version * feat: rely on prismjs plugin for embed-snippet directive highlighting * Add console.warn if invalid range is specified * docs: document highlight directives * fix: fix endless loop when multiple highlight-start/end directives * Add kitchen sink directive test * Remove built version * docs: better directive example * fix: existing highlight ranges behavior now working again * fix: JSX directive not removed after highlight * fix: highlight-range directive removing a line * Add comment explaining priority between top-level declaration and directives * fix lint error * Add more explicit example in README * Fix HTML opening comment not being stripped * Add `./highlight-line-range.js to .gitignore * Remove extraneous <span> tags * Add comment for big regex

- gatsby-remark-embed-snippet@3.1.0 - gatsby-remark-prismjs@3.1.0

Yep!

Closes #10135 Added license to `What's in this document section` linking it to corresponding section within the `README` file.

* Created XML Sitemap Post This was created using the package (gatsby-plugin-sitemap), I followed the guidelines and ran it through Hemingway (Just as a side note Where has this been all my life?!) - I do think it is a bit brief - Please do tell me how I can work to improve it! Really Appreciate it :) * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Ran it through Prettier and Applied Changes * Trying to debug the prettier issue. Maybe I am just doing this wrong 😬 * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update docs/docs/creating-a-sitemap.md Adding Dustin's suggestions Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update docs/docs/creating-a-sitemap.md Co-Authored-By: AnushPatel <33417205+AnushPatel@users.noreply.github.com> * Update creating-a-sitemap.md * Fixed the typo * Added the 'Connection' between the two clauses * Added the improvements to the code Ran it through Prettier to make sure Formatting is tip top. * Added the improvements to the code Ran it through Prettier to make sure Formatting is tip top.

@pieh

Closes #10067. Replaces #10149. Webpack started using terser instead of uglify, which broke our plugin's check for the uglify webpack plugin (to exclude it from our pipeline). But it seems that excluding terser isn't even necessary, can't find any bugs in dev or prod builds. The remaining plugin that needs to be avoided will be handled by name rather than instance. cc/ @pieh

- gatsby-plugin-netlify-cms@3.0.8

Got rid of the * as the link now isn't a stub

Add Gatsby + Bulma CSS starter kit.

* test: do not report coverage unless in CI In #10128, we added test report tasks to Azure pipelines. Unfortunately, this adds some additional overhead and coverage type stuff in _local_ development that we probably don't want. This PR addresses this issue, and conditionally detects whether running in CI. If running in CI (e.g. Azure Pipelines, Circle, etc.) it will add the additional coverage reporter and coverage functionality. Note: this is currently blocked by watson/ci-info#22 * add GENERATE_JEST_REPORT env var and use it with azure pipelines * use var to hold normalized (boolean) val from env var

graphql object is used for query but not imported from `gatsby` package.

* feat(blog): add gatsby days blog post * format

@mweststrate

- https://gatsby-starter-mobx.netlify.com/ - https://github.com/borekb/gatsby-starter-mobx Features: - Gatsby v2 + TypeScript - MobX with decorators - Two examples from @mweststrate's Egghead course - .editorconfig & Prettier - TSLint - Jest

Didn't find this anywhere in the docs, think that's a good spot for it. The Promise is not needed actually, but I left it in the upper example.

* feat(www): rebase Ecosystem and Blog sections feat(www): add Ecosystem section to Homepage feat(www): homepage WIP wip feat(www): finish sections style for mobile feat(www): add Ecosystsem featured items to Hompage feat(www): homepage ecosystem section styling WIP feat(www): add arrow to action button fix(www): fix code formating fix(www): fix code formating and eslint errors fix(www): fix hovering effect on Featured Item fix(www): fix hovering effect sequel fix(www): fix hover bug fix(www): update texts (intro & link labels) feat(www): add scroller observer to Home page refactor(www): use imported scrollers observer fix(www): change link labes on Ecosystem page fix(www): fix some small style issues refactor(www): refator combineEcosystemFeaturedItems and reorder some css properties feat(www): add Blog section to Homepage feat(www): mobile styles for Blog section feat(www): mobile styles for Blog section feat(www): desktoop style for Blog section WIP feat(www): desktoop style for Blog section WIP feat(www): desktop style for Homepage Blog section WIP feat(www): finish desktop style of Blog section feat(www): finish desktop style of Blog section * fix(www): fix stylelint error * feat(): finish styles of Blog section * fix(www): add cover to one post for development * fix(www): update margins for section action btns * fix(www): update margins of Blog section * refactor(www): email-cature-form * refactor(www): email-cature-form * feat(www): add ornaments to assets * feat(www): update colors palette * feat(www): add Homepage variant style to newsletter form * feat(www): add Homepage variant style to newsletter form * feat(www): mobile style for Homepage Newsletter section * refactor(www): refactor homepage-section * fix(www): fix homepage section padding * refactor(www): refactor ecosystem scroollers * fix(www): fix some styles * fix(www): add cover image to one post * fix(www): add border-radius to cover image * fix(www): add automaticExcerpt if the handwritten one does not exists * feat(www): add conditional formating to post dates * fix(www): fix hover effect on Blog cards * fix(www): remove 'Submit an article button'

This is the beginnings of a fix for #4459 Right now, the fix works when excerpt_separator is provided. I have not yet implemented a fix for when the excerpt is generated using the `pruneLength` setting, though I have thoughts on how to solve it. My plan to is do a pre-order traversal over the html AST, accumulating nodes until the pruneLength is reached. I would love some preliminary feedback to get a sense of how the contributors feel about this PR so far. Here are some of my initial thoughts: 1. The work in the `excerpt` resolve function is a little hacky. We are directly invoking a variety of functions get our HTML. I'm curious if anyone has a more streamlined approach for this. 2. We are invoking `getMarkdownAST` (previously getAST) twice, once for the excerpt and once for the entire page. I'm worried that this is going to break non-idempotent existing plugins since they will now run twice. 3. I tore apart the `getAST` function a bit and think I did a good job simplifying it. The big change is that we don't generate multiple promises anymore. i think this goes a long way towards improving readability. I'd love to hear people's thoughts.

- gatsby-image@2.0.21 - gatsby-transformer-remark@2.1.13 - gatsby@2.0.56

@greglobinski

@greglobinski @amberleyromo Currently the second "View all posts" links to the homepage instead of the blog

Added jacobdcastro.com to site showcase. 'Featured' set to 'false' and all possible YAML entries are filled out, even optional ones.

…0107) Without destructuring `activeClassName`, the <a> element will receive the prop and react will throw an error along the lines of `React does not recognize the `activeClassName` prop on a DOM element.`.

Update docs to show how state is passed through the location object.

Revert unintentional braking changes to style of the Newsletter form on Blog post pages applied during implementation of the same form presented on redesigned Hompage Newsletter section. - broken style ![screenshot from 2018-11-28 13-54-21](https://user-images.githubusercontent.com/32480082/49153447-0b58d000-f316-11e8-9e75-213f74830768.png) - fixed style (with this PR), the form looks the same as before refactoring of `www/src/components/email-capture-form.js` ![screenshot from 2018-11-28 13-53-55](https://user-images.githubusercontent.com/32480082/49153446-0ac03980-f316-11e8-929b-40e800ced254.png)

- Check if resources fail (as before) - Upon any failure, render static HTML instead of dynamically rendering the children - Upon initial failure, reload the page and mark the path as failed - Upon second failure, don't reload the page and unflag it (since it might have just been a temporary failure and we want it to retry the next time) Fixes #10074

- gatsby@2.0.57

…ials.com (#10189) Add two educational sites to showcase.

to pull changes added in #10141

…ubplugins (#9972) This allow `gatsby-remark-*` subplugins to not have special error handling - `gatsby` will properly panic on build, but dev server won't crash anymore

…idget (#9565)

- babel-plugin-remove-graphql-queries@2.5.2 - babel-preset-gatsby-package@0.1.3 - babel-preset-gatsby@0.1.5 - gatsby-cli@2.4.6 - gatsby-codemods@1.0.8 - gatsby-dev-cli@2.4.8 - gatsby-image@2.0.22 - gatsby-link@2.0.7 - gatsby-plugin-canonical-urls@2.0.8 - gatsby-plugin-catch-links@2.0.9 - gatsby-plugin-coffeescript@2.0.7 - gatsby-plugin-create-client-paths@2.0.3 - gatsby-plugin-cxs@2.0.3 - gatsby-plugin-emotion@2.0.7 - gatsby-plugin-facebook-analytics@2.0.2 - gatsby-plugin-feed@2.0.10 - gatsby-plugin-fullstory@2.0.2 - gatsby-plugin-glamor@2.0.7 - gatsby-plugin-google-analytics@2.0.8 - gatsby-plugin-google-gtag@1.0.8 - gatsby-plugin-google-tagmanager@2.0.7 - gatsby-plugin-guess-js@1.0.3 - gatsby-plugin-jss@2.0.5 - gatsby-plugin-layout@1.0.10 - gatsby-plugin-less@2.0.8 - gatsby-plugin-lodash@3.0.3 - gatsby-plugin-manifest@2.0.11 - gatsby-plugin-netlify-cms@3.0.9 - gatsby-plugin-netlify@2.0.6 - gatsby-plugin-nprogress@2.0.7 - gatsby-plugin-offline@2.0.18 - gatsby-plugin-page-creator@2.0.5 - gatsby-plugin-postcss@2.0.2 - gatsby-plugin-preact@2.0.8 - gatsby-plugin-react-css-modules@2.0.4 - gatsby-plugin-react-helmet@3.0.3 - gatsby-plugin-remove-trailing-slashes@2.0.6 - gatsby-plugin-sass@2.0.5 - gatsby-plugin-sharp@2.0.14 - gatsby-plugin-sitemap@2.0.3 - gatsby-plugin-styled-components@3.0.4 - gatsby-plugin-styled-jsx@3.0.3 - gatsby-plugin-styletron@3.0.3 - gatsby-plugin-stylus@2.0.3 - gatsby-plugin-subfont@1.0.3 - gatsby-plugin-twitter@2.0.8 - gatsby-plugin-typescript@2.0.2 - gatsby-plugin-typography@2.2.2 - gatsby-react-router-scroll@2.0.2 - gatsby-remark-autolink-headers@2.0.12 - gatsby-remark-code-repls@2.0.2 - gatsby-remark-copy-linked-files@2.0.7 - gatsby-remark-custom-blocks@2.0.2 - gatsby-remark-embed-snippet@3.1.1 - gatsby-remark-graphviz@1.0.4 - gatsby-remark-images@3.0.1 - gatsby-remark-katex@3.0.1 - gatsby-remark-prismjs@3.1.1 - gatsby-remark-responsive-iframe@2.0.7 - gatsby-remark-smartypants@2.0.7 - gatsby-source-contentful@2.0.16 - gatsby-source-drupal@3.0.12 - gatsby-source-faker@2.0.3 - gatsby-source-filesystem@2.0.10 - gatsby-source-graphql@2.0.7 - gatsby-source-hacker-news@2.0.7 - gatsby-source-lever@2.0.2 - gatsby-source-medium@2.0.2 - gatsby-source-mongodb@2.0.9 - gatsby-source-npm-package-search@2.0.2 - gatsby-source-wikipedia@2.0.3 - gatsby-source-wordpress@3.0.16 - gatsby-transformer-csv@2.0.5 - gatsby-transformer-documentationjs@2.0.2 - gatsby-transformer-excel@2.1.4 - gatsby-transformer-hjson@2.1.3 - gatsby-transformer-javascript-frontmatter@2.0.5 - gatsby-transformer-javascript-static-exports@2.1.4 - gatsby-transformer-json@2.1.6 - gatsby-transformer-pdf@1.0.15 - gatsby-transformer-react-docgen@2.1.3 - gatsby-transformer-remark@2.1.14 - gatsby-transformer-screenshot@2.0.9 - gatsby-transformer-sharp@2.1.9 - gatsby-transformer-sqip@2.0.9 - gatsby-transformer-toml@2.1.3 - gatsby-transformer-xml@2.0.5 - gatsby-transformer-yaml@2.1.6 - gatsby@2.0.58 - graphql-skip-limit@2.0.2

This PR adds a feature flag `GATSBY_DB_NODES` that can be used to change the storage engine for the gatsby data layer (`nodes`). - `redux` (default) which uses the existing redux implementation, and `sift` for querying. Or, you can use - `loki` which uses the loki in-memory database to store and query. This PR re-implements functionality in #9338, but with all tests passing and addressing previous feedback. It should also be easier to review since it builds on several refactorings. Some things to note: 1. I [submitted a PR to lokijs](techfort/LokiJS#718) which still hasn't been merged, though the author says he'll start working on it soon. Therefore, in in interim, I've published [@moocar/lokijs](https://www.npmjs.com/package/@moocar/lokijs). 1. I haven't implemented auto indexing of query fields yet. I'll attack that next. 1. I suggest we ask the community to try out the feature flag once it's merged to get feedback. All the tests pass, but this is such a big change that we'll want to test it gradually 1. While loki uses the same mongo query language as sift, they do have different behavior. Most of my time on this PR was spent ensuring that loki behaves **exactly** like sift. See [db/loki/nodes-query.js](https://github.com/gatsbyjs/gatsby/blob/cddbe893a4ce638babb1cbe5e5da4c13b6f5e57d/packages/gatsby/src/db/loki/nodes-query.js). But there's a chance a few edge cases have slipped through the cracks. 1. the feature flag works with the tests too `GATSBY_DB_NODES=loki yarn test`. We should perhaps look into running this on all PRs

- gatsby@2.0.59

…10197)

…than assign it. (#9924) The trailing slash stripping plugin [executes the function](https://github.com/gatsbyjs/gatsby/blob/f9714a5646523bc728586e3692190507ad68e6c1/packages/gatsby-plugin-remove-trailing-slashes/src/gatsby-node.js#L9) rather than just assigning it, so I'd imagine that's what the example code should be doing too.

* Created the page. * Page content. * Link in the blog post. * Source attribution, language tweaks * Fixed Prettier error.

…ing (#10209) * fix(gatsby-remark-prismjs): prevent additional blank line from appearing * chore: don't use template literals; not needed * test: update snapshots

#10196) * track markdown properties * fix image markdown

- gatsby-remark-embed-snippet@3.1.2 - gatsby-remark-prismjs@3.1.2 - gatsby-transformer-remark@2.1.15

They removed Helmet from "layout.js" and moved it to "site-metadata.js"

…apping error (#10216) hello! this is a fix for #10138! that issue contains all the details of the issue, so i won't repeat them here! i've copied the error avoidance approach from the `exports.mapElementsToParent` function just below this block!

I'd like to add my portfolio website to the gatsby showcase. Thanks for all the great work you're doing! 💪 Thank you.

a simple starter for how to use Gatsby and the Ghost CMS together

) Based on the dependencies brought in from this present, the following updates were added to the README: - Removed reference to `@babel/plugin-proposal-optional-chaining` - Added reference to `@babel/plugin-syntax-dynamic-import` - Updated ordering to move babel-core plugins above community ones. Resolves #10214

* feat(www): create Pullquote custom component * fix(www): add explanatory comment * feat(www): add styles to Pullquote * feat(www): add styles to Pullquote * fix(www): fix typo in css code * feat(www): add variants of styles * refactor(www): remove variant class names logic from template-blog-post * fix(www): remove unused const

* Add date example to readme * Add note to readme for custom feed queries This should make it clearer what the correct keys are for custom queries (e.g. should be *date*, not *pubDate*).

* Update Installation Section This PR changes the prose related to setting up your `setup-test-env.js` file. Because it's assumed the user followed the unit-testing section, they should have a `jest.config.js` file. If they do, they need to add the `setupTestFrameworkScriptFile` to the jest config, rather than the `package.json` otherwise, their `setup-test-env.js` will be run correctly. I've added the instructions for `jest.config.js` but also kept the original instructions related to adding it to the `package.json` * Cut old part * Update docs/docs/testing-react-components.md Co-Authored-By: jsjoeio <jjprevite@gmail.com> * Update docs/docs/testing-react-components.md Co-Authored-By: jsjoeio <jjprevite@gmail.com> * Fix linting

Before the change it was possible to enter all sorts of parameters. Also Numbers threw a weird error. Both fixed now.

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

Closes #10236

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Starter showcase card layout update #8117

Starter showcase card layout update #8117

Commits on Nov 6, 2018

Commits on Nov 7, 2018

Commits on Nov 8, 2018

Commits on Nov 9, 2018

Commits on Nov 10, 2018

Commits on Nov 11, 2018

Commits on Nov 12, 2018

Commits on Nov 13, 2018

Commits on Nov 14, 2018

Commits on Nov 15, 2018

Commits on Nov 16, 2018

Commits on Nov 17, 2018

Commits on Nov 18, 2018

Commits on Nov 19, 2018

Commits on Nov 20, 2018

Commits on Nov 21, 2018

Commits on Nov 22, 2018

Commits on Nov 26, 2018

Commits on Nov 27, 2018

Commits on Nov 28, 2018

Commits on Nov 29, 2018

Commits on Nov 30, 2018

Commits on Dec 1, 2018

Commits on Dec 2, 2018

Commits on Dec 3, 2018