-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
✨ Enhancement: Page in overview section to show Case Studies #440
Comments
Hey! |
Please go ahead. These cards is not going to be the standard ones. So no blockers expected here. |
@benjagm, Had a few questions related to this one. In order to add a custom card component which will read data from the specified JSON file, I would either have to use a .tsx file or a .mdx file. However, the present configuration for the pages/SideBar section specifies the use of only '.md' files. I tried finding out ways to implement components in .md itself, but conversion to .mdx is mandatory and based on the settings in [slug].page.tsx file (specifically, So, will it be okay to modify this function to include .mdx files or is there another way round that can be used? Also, for adding .mdx files, I will also need to configure the next.config.json file. So wanted to know your views before making such major changes. Thanks! |
Please see the [slug].page.tsx in each subfolder of pages. This can help you think about how you can have your own page without md. I will recommend you to take a look to implementers page but be careful, this page doesn't have sidebar. I hope this helps. We have multiple issues implementing similar features. Pleas see #429 |
Okay I will take reference from these issues! Thanks for the information. |
Can you please make sure the target branch of this PR is : https://github.com/json-schema-org/website/tree/web-release-3? |
Done from my side :) |
Hey @benjagm |
Make sure there is a title and intro paragraph and it will be enough. It can be "Loren impsum..." because I will be sending a PR with the texts before merging. |
okay thanks got it! |
@TamannaVerma99 please proceed with the integration if the component Card available in the parent branch. If you need to modify the component let's discuss first because others are integrating it. |
Hey @TamannaVerma99, |
This is already merged to in release-3 branch. Will be closed as soon as that goes to main branch. |
Closed as completed. |
Is your feature request related to a problem? Please describe
No
Describe the solution you'd like
it would be amazing to have a new page inside the overview section to show the case studies published in the blog.
This will be a data drive page reading results from a json file stored in our data folder. Each item of the file will have these fields:
Please see this prototype:
This is a prototype made by screenshot. Please complete the job using styles as per our site.
For the cards please consider using border shadows similar to the ones in the landing page:
The case studies are available in the blog:
https://json-schema.org/blog?type=Case%20Study
Describe alternatives you've considered
No response
Additional context
No response
Are you working on this?
No
The text was updated successfully, but these errors were encountered: