Download gatsby options made simple

Gatsby-source-google-docs-team is a Gatsby plugin to use Google Docs as a data source.🔥 No need for a CMS anymore.🖋 Write your blog posts on Google Docs.🗂 Organize your documents in one or multiple folder in Google Drive (trees allowed)🤡 Add custom metadata fields to yours documentsSupports Team drivesOptional Flag to download images to gatsbyAdded folder name to node if a doc is inside a folderIt’s that simpleGetting startedDownload gatsby-source-google-docs-team packageYou can download gatsby-source-google-docs-team from the NPM registry via thenpm or yarn commandsnpm install gatsby-source-google-docs-team --saveTurn on the Google Docs API and set configurationFollow the Step 1: Turn ON the Google Docs APITurn ON the Google Drive APIGet a client_id and a client_secret from the Google console. If you downloaded credential.json file, you can extract them from itGet an api_key from the Google consoleFill the gatsby-source-google-docs gatsby config object.More info can be found on the official Google Docs quickstart guide.Generate a token fileRun gatsby develop to generate a token file.token_path can be customized in the configuration object (config/token_path).UsageAdd the plugin to your configuration:In your gatsby-node.js file, configure the gatsby-source-google-docs and the gatsby-transformer-remark plugins:module.exports = { plugins: [ { resolve: "gatsby-source-google-docs", options: { // Mandatory // -------- foldersIds: ["FOLDER_ID_1", "FOLDER_ID_2"], // folders Ids can be found in Google Drive URLs config: { api_key: "YOUR_API_KEY", client_id: "YOUR_CLIENT_ID", client_secret: "YOUR_CLIENT_SECRET", // Optional // -------- token_path: "google-docs-token.json", }, // Optional // -------- fields: ["createdTime"], // fieldsMapper: {createdTime: "date", name: "title"}, // To rename fields fieldsDefault: {draft: false}, // To add default fields values convertImgToNode: true, // To convert images to remote node files }, }, // Use gatsby-transformer-remark to modify the generated markdown // Not mandatary, but recommanded to be compliant with gatsby remark ecosystem { resolve: "gatsby-transformer-remark", options: { plugins: [], }, }, ],}Add an automatic slug generationModify your onCreateNode function in your gatsby-node.js to generate a slug field:exports.onCreateNode = ({node, actions}) => { // You need to enable `gatsby-transformer-remark` to transform `GoogleDocs` type to `MarkdownRemark` type. if (node.internal.type === `MarkdownRemark`) { const customSlug = node.frontmatter.slug // If you add extra data `slug` with description field actions.createNodeField({ name: `slug`, node, value: customSlug || node.frontmatter.path,

Runs. For example, setting CI=true as an environment variable will tailor output for dumb terminals.serveServes the production build of your site for testing prior to deployment. Should be run from the root of your project.Options include:OptionDescription-H, --hostSet host. Defaults to localhost-p, --portSet port. Defaults to 9000-o, --openOpen the site in your default browser for you--prefix-pathsServe site with link paths prefixed (if built with pathPrefix in your gatsby-config file).infoShow helpful environment information which is required in bug reports. Should be run from the root of your project.Options include:OptionDescription-C, --clipboardCopy environment information to your clipboardcleanDelete the .cache and public directories. Should be run from the root of your project.This is useful as a last resort when your local project seems to have issues or content does not seem to be refreshing. Issues this may fix commonly include:Stale data, e.g. this file/resource/etc. isn't appearingGraphQL error, e.g. this GraphQL resource should be present but is notDependency issues, e.g. invalid version, cryptic errors in console, etc.Plugin issues, e.g. developing a local plugin and changes don't seem to be taking effectreplOpen a Node.js REPL (interactive shell) with context of your Gatsby environment. Should be run from the root of your project.Gatsby will prompt you to type in commands and explore. When it shows this: gatsby >, you can type in one of these commands to see their values in real time:babelrccomponentsdataPathsgetNodes()nodespagesschemasiteConfigstaticQueriesTo exit the REPL:Press Ctrl+C or Ctrl+D twice, orType .exit and press EnterWhen combined with the GraphQL explorer, these REPL commands could be very helpful for understanding your Gatsby site's data.Disabling colored outputIn addition to the explicit --no-color option, the CLI respects the presence of the NO_COLOR environment variable (see no-color.org).How to change your default package manager for your next project?When you use gatsby new for the first time to create a new project, you are asked to choose your default package manager between yarn and npm.Which package manager would you like to use ? › - Use arrow-keys. Return to submit.❯ yarn npmOnce you’ve made your choice, the CLI won’t ask for your preference again for any subsequent project. If you want to change the preference, there are two ways to change the default package manager for your next project:Using options command from CLIEditing the config fileUsing options command from CLIYou can use the gatsby options command to change the default package manager. ]">gatsby options set [key> value>]ArgumentDescriptionkeySet the package manager gatsby new is using.

The Preview plugin allows you to assign your profile to specific audiences, experiences, and variants within preview and development contexts.Add plugin to the plugins prop of the NinetailedProvider and provide an array of all Ninetailed Experience and Ninetailed Audience entries to the plugin. Ensure that you are supplying both all published and all draft entries of each to the plugin. Additionally, you should ensure that you are not instantiating the plugin in production contexts.InstallationAdd the dependency: npm yarn npm install @ninetailed/experience.js-plugin-previewyarn add @ninetailed/experience.js-plugin-preview Then, add the plugin to the Ninetailed instance: React, Next.js Gatsby JavaScript import { NinetailedPreviewPlugin } from '@ninetailed/experience.js-plugin-preview' {}, // Optional: Callback to handle user forwarding to the audience entry in your CMS onOpenAudienceEditor: (audience) => {}, // Optional: Determine the visibility of the Preview Plugin ui: { opener: { hide: false } }, }) ]}> // ...import {audienceQuery, audienceMapper, experienceQuery, experienceMapper } from '@/lib/yourFunctions'plugins: [ // ... { resolve: `@ninetailed/experience.js-gatsby`, options: { clientId: NINETAILED_CLIENT_ID, environment: NINETAILED_ENVIRONMENT, ninetailedPlugins: [ { resolve: `@ninetailed/experience.js-plugin-preview`, name: "@ninetailed/experience.js-plugin-preview", options: { // Options specific to Gatsby - optional customOptions: { // Query all audiences audienceQuery, // Mapper function for audiences audienceMapper, // Query all experiences experienceQuery, // Mapper function for experiences experienceMapper, }, // Callback to handle user forwarding to the experience entry in your CMS - optional onOpenExperienceEditor: (experience) => { }, // Determine the visibility of the Preview Plugin - optional ui: { opener: { hide: false } }, }, }, ], }, },];Define the functions for retrieving and mapping Gatsby data so they can be used in gatsby-config.js. These example queries are compatible with gatsby-source-contentful; adjust your queries based on the content source you are using.import { ExperienceLike, ExperienceMapper,} from "@ninetailed/experience.js-utils";export const audienceQuery = ` query NinetailedAudienceQuery { allContentfulNinetailedAudience { edges { node { nt_audience_id nt_name nt_description { nt_description } } } } } `export const audienceMapper = audienceData => { return audienceData.allContentfulNinetailedAudience.edges.map(audience => { return { id: audience.node.nt_audience_id, name: audience.node.nt_name, description: audience.node.nt_description?.nt_description, } })}export const experienceQuery = ` query NinetailedExperienceQuery { allContentfulNinetailedExperience { edges { node { id: contentful_id name: nt_name type: nt_type audience: nt_audience { id: contentful_id name: nt_name } config: nt_config { distribution traffic components { baseline { id } variants { hidden id } } } variants: nt_variants { ... on ContentfulEntry { id: contentful_id } } } } } } `export const experienceMapper = (experienceData: any) => { return experienceData.allContentfulNinetailedExperience.edges .filter(({ node }: {