-
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
Sorted blogs by date in graphql #28
base: master
Are you sure you want to change the base?
Conversation
@Kameshwaran is not the right way to do it. eventually i want to move the /posts /services out of this repo. |
filter: { | ||
sourceInstanceName: { eq: "posts" } | ||
ext: { in: [".md", ".mdx"] } | ||
frontmatter: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you keep this filtered based on folder. I am not sure what the right architecture is. eventually content should be in a seperate repo or a headless CMS.
We can do some research on that, and suggest a good architecture at a later point in time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it is good for us to prefer headless cms here. If we choose headless cms, then again it requires our team members to have an account for adding/altering the content which I eventually don't want to happen.
I think, if we manage the content alone in another repo, we should be good to go. Serverless is doing the same! What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might be the best idea to have every person run our website to add a blog.
anyways, this is not important now. so letting this be for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically anyone who has github account and part of codebrahma team in github, should be able to update content on website by raising a PR.
@Kameshwaran We should check out the following three CMS headless, to learn what the new trend is, and what they offer |
@sanandnarayan We can use a separate repo for all the content and fetch it from there, instead of paying for a headless CMS. Since there are no non-technical people in CB anyone can add their content to that repo by raising a PR, instead of using a headless CMS. I have created a temporary repo with all the content and raised a PR #39 which fetches content from that repo, please check and let us know what you think. |
No description provided.