forked from gatsbyjs/gatsby
-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(showcase): Add a+ saude (gatsbyjs#20531) #1
Merged
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
Added Personal Portfolio Co-authored-by: Sidhartha Chatterjee <[email protected]>
* Chore: Updates starters.yml * Update docs/starters.yml Co-Authored-By: Sidhartha Chatterjee <[email protected]> * fix indentation Co-authored-by: Sidhartha Chatterjee <[email protected]> Co-authored-by: GatsbyJS Bot <[email protected]> Co-authored-by: Lennart <[email protected]>
Added an install heading to instruct users to install the plugin.
Co-authored-by: Lennart <[email protected]>
* Add erichowey.dev * Fixed indentation * Updated categories Co-authored-by: Lennart <[email protected]>
Co-authored-by: Lennart <[email protected]>
* Update index.d.ts * fix wrong type
Co-authored-by: GatsbyJS Bot <[email protected]>
* Add Zeit * Update docs/blog/100days/free-hosting/index.md Co-Authored-By: Sarup Banskota <[email protected]> Co-authored-by: Sarup Banskota <[email protected]>
Co-authored-by: Dustin Schau <[email protected]> Co-authored-by: Dustin Schau <[email protected]>
…using identity widget (#20580)
This PR ensures that the current working directory on Windows always has an uppercase drive letter (i.e., C: vs. c:).
* Add dataLayerName check before push in event. * Update browser test after data layer name check change.
* Add challenge 3 of 100DaysOfGatsby * chore: format * Update docs/blog/100days/gatsby-image/index.md Co-Authored-By: LB <[email protected]> * Update docs/blog/100days/gatsby-image/index.md Co-Authored-By: LB <[email protected]> * chore: format Co-authored-by: GatsbyJS Bot <[email protected]> Co-authored-by: LB <[email protected]>
* docs: improve gatsby-plugin-offline SSR seo * Update seo.md * Apply suggestions from code review Thank you @laurieontech Co-Authored-By: LB <[email protected]> * don't use the word trick * fix commands in gatsby-plugin-offline readme Co-authored-by: LB <[email protected]>
#20581) * Add note about disabling frontend inclusion of widget * Update packages/gatsby-plugin-netlify-cms/README.md Co-Authored-By: LB <[email protected]> Co-authored-by: LB <[email protected]>
* point example to a demo REST API instead of a dummy URL * remove redundant flag * add missing pieces of config for a working default starter site * link to info about stopping and starting gatsby develop for total beginners * link to info about stopping and starting gatsby develop for total beginners * add missing key prop so React doesn't throw an error when this is copied in * add an actual demo URL instead of the same one we're using below * use the live pantheon site instead of the dev one. the dev url gets put to sleep after a period of inactivity and will throw a 503 error if someone tries to use it in this tutorial * add a demo url * switch from wordpress.com example to wordpress.org example this block of code shows `hostingWPCOM: false` below, so it doesn't make sense to use a wordpress.com url here * update protocol * Make clearer which file we're working with * Revert "link to info about stopping and starting gatsby develop for total beginners" This reverts commit 2b8a678. * Update using-wordpress readme to reflect that the code here works now Co-authored-by: GatsbyJS Bot <[email protected]>
* chore(recipe):Creating a new site using a theme * Updated Docs according to reviews
… using MiniCssExtractPlugin and HMR (#20589) * refactor preview styles handling during develop using MiniCssExtractPlugin * move replaceStyleLoader into replaceRule's scope
A Map is designed for this work where an object will deoptimize after a handful of different keys.
Noticed a site was going through the slow path even though there was no good reason for it. One of the reasons was that this check failed, even though it should pass. We use unique `id`s internally for nodes, so if a query finds a node it can't find more than one node. So the check for `firstOnly` is redundant here. This hopefully leads to a performance improvement for some other sites.
…tboundLink> (#20570) * feat(gatsby-plugin-google-analytics) Pass additional props to the <OutboundLink> Currently there is no way to pass event category, label, and action when one uses the <OutboundLink> component * Remove non standard attributes from the a tag * Add eventValue to prop types
* make sure to throw proper errors * update test to match error
* chore(gatsby-source-contentful): do not clobber `contentful_id` * chore(gatsby-source-contentful): make sure to visit _all_ nested properties * chore(gatsby-source-contentful): Do not choke on cycles
When @tavareshenrique was translating this page he spotted a incorrect link inside the text. I'm opening this PR to fix link.
* fix(dts): improve `gatsby` TS types for `sourceNodes` * fix(dts): add schema prop to `NodePluginArgs` * chore: resolve PR requests Use Record instead of object mapping.
* fix showcase redirects * revert change * fix redirect
…ar needed) (#20637) * add spanish files to source * disable spanish for now * add spanish again * aksldjasdf * get everything working * display spanish and portuguese pages * get all the links working! * a few more fixes * simplify * whats gatsby-cli doing here * i18n util file * update site metadata * disable translations by default * explain how to enable localizations in readme * add more languages
* changed deprecated method componentWillReceiveProps to getDerivedStateFromProps, checked for props changes to trigger updates * Removed unnecessary component state, used props instead
Updates Addy Osmani's The Cost Of JavaScript to the 2019 release.
The queue was retained for develop mode which led to the same event handlers being registered over and over again, which led to strange artifacts in the output. With this change the events are aggressively deregistered from the queue when it finishes or fails. Fixes #20787
Adding personal website for Adam Bowen https://adamcbowen.com
* remove processing and waiting queue * Remove filter Co-authored-by: Sidhartha Chatterjee <[email protected]>
A few various typos on this file (most likely due to haste in writing!). Have found and corrected all typos.
* Add challenge 4 * chore: format * Fix capitalization * Update docs/blog/100days/react-component/index.md Co-Authored-By: Marcy Sutton <[email protected]> * Add link to accessibility resource Co-authored-by: GatsbyJS Bot <[email protected]> Co-authored-by: Aisha Blake <[email protected]> Co-authored-by: Marcy Sutton <[email protected]>
* use-soft-line-wraps-for-docs/how-shadowing-works * use-soft-line-wraps-for-docs/add-404-page * use-soft-line-wraps-for-docs/add-custom-webpack-config * use-soft-line-wraps-for-docs/basic-hardware-software-requirements
* chore(starters): add gatsby-starter-flex * fix(starters): update tags for gatsby-theme-flex
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.
Description
Documentation
Related Issues