feat(sandbox): card retrieval for a unique editorial dashboard #1154
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
1 task
1 task
…024' of https://github.com/italia/designers.italia.it into feat-card-retrieval-for-an-unique-editorial-dashboard-2024
⚡ Lighthouse report for the home page 🏠
Other pages
|
Fupete
commented
Dec 21, 2023
…024' of https://github.com/italia/designers.italia.it into feat-card-retrieval-for-an-unique-editorial-dashboard-2024
Fupete
changed the title
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.
Working on it.
I am testing a way to create a single centralized configuration file where editors can control the dynamic content featured on the Web site. See the new
yamlof settings to understand my ultimate goal.Currently on the home page you can see a new section with 4 dynamic loaded cards rendering. I use a global pageQuery on allContnt filtered by page titles. Currently the titles are hardcoded in gatsby-node.js. We need to load them from the settings YAML and move them to a dedicated part of the graphql schema.
Then: create different views on different pages.
FYI @bfabio @astagi
Ps. the cards images are currently not working/shown... maybe something about assets preparation in gatsby-node too.