unstats / gatsby-themes Goto Github PK

Take over from https://unstats.un.org/unsd/undataforum/programme/index.html.

Figure out how https://github.com/apollographql/gatsby-theme-apollo does monorepo with npm and Lerna instead of yarn workspaces.

Just a page with default layout. Anyone who wants something fancy to show can shadow the page.

• Header without logo and title on homepage
• Header with logo on other pages

Theme does not only contain layouts but also fundamental plugins that are shared with all consuming themes.

• Add social icons.
• Make pages linked from footer easier to read.

As taught in this video: https://egghead.io/lessons/gatsby-set-up-yarn-workspaces-for-gatsby-theme-development

Error: <svg> attribute height: Expected length, "4,4,5".

Put project configs in place:

• Add lint-stage and husky
• Each package gets its own ESLint configuration
• Prettier is done globally
• Use eslint-plugin-shopify

Then fix lint errors:

• gatsby-theme-undataforum
• main-website-demo
• docs

Follow @undataforum/components.

Package @undataforum/tokens with its proprietary license currently is a dependency of gatsby-theme-undataforum. It should not be a dependency of the theme, but rather of the actual site.

By default profiles are type Mdx. Introduce new node type to make it easier to distinguish profiles form other MDX content.

• Same config as here: https://github.com/UNDataForum/components/blob/master/lerna.json
• Update README on how to publish theme

Every push to any branch should result in deployment of main-website-demo.

Support mapping of unordered lists in MDX.

• Migrate page creation logic out of gatsby-theme-undataforum.
• Path: /blog.
• Simple list of PostPreviews.
• Remove gatsby-theme-undataforum.

Container component from @undataforum/components.

• Add internal and external links as test case.
• Replace legacy Link with SmartLink in mapping.

Should be written as generic as possible to be used for sessions and webinars.

gatsby-plugin-profiles creates custom nodes of default type Profile that makes querying profiles very easy. In scenarios where the plugin is used more than once in a website or another theme, you need to be able to customize the type to manage separate collections of profiles, e.g. AuthorProfile and SpeakerProfile.

Same package, but with more consistent name.

Different .eslintrc files in each project do not work. You cannot use yarn workspaces run lint with lint-staged. The command used with lint-staged needs to lint one single files, not a bunch of files.

Consolidate ESLint configs in root folder.

https://github.com/UNDataForum/gatsby-themes/network/alert/yarn.lock/js-yaml/closed.

• purge task purges node_modules folders.
• clean task runs gatsby clean.

Ensure that plugin is transpiled when included as dependency. See https://www.gatsbyjs.org/packages/gatsby-plugin-compile-es6-packages/.

• Footer is currently configured in theme and there is no way to customize it (other than shadowing).
• links and social props should be configurable in theme options.

• gatsby-plugin-offline
• gatsby-plugin-manifest

https://dequeuniversity.com/rules/axe/3.1/html-has-lang?application=lighthouse

Lighthouse gives a performance penalty to page because VideoList does not lazy load. Check if this is supported in react-player.

Handling of videos with Gatsby: https://www.gatsbyjs.org/docs/working-with-video/.

• Update to @undataforum/components 0.26.0 in gatsby-theme-undataforum.
• Replace Provider with ThemeProvider.

• Videos to VideoList
• Profiles to ProfileList
• Posts to PostList

Add WebP support via gatsby-image.

Stop distinguishing between serif and sans-serif fonts.

• License
• Homepage
• Keywords

https://www.gatsbyjs.org/packages/gatsby-plugin-sitemap/

https://styled-system.com/guides/migrating/

Titles such a "Her Excellency" or "His Royal Highness".