Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Kameshwaran
Copy link
Contributor

No description provided.

@sanandnarayan
Copy link
Member

@Kameshwaran templateKey: { eq: "blog-post" }

is not the right way to do it.
We need another tag which says blog or services or something.

eventually i want to move the /posts /services out of this repo.
this repo should be only the gatsby code, and content should live elsewhere

filter: {
sourceInstanceName: { eq: "posts" }
ext: { in: [".md", ".mdx"] }
frontmatter: {
Copy link
Member

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

Copy link
Contributor Author

@Kameshwaran Kameshwaran Aug 6, 2019

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?

Copy link
Member

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

Copy link
Contributor Author

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.

@sanandnarayan
Copy link
Member

@Kameshwaran We should check out the following three CMS headless, to learn what the new trend is, and what they offer
https://www.contentful.com/
https://www.sanity.io/pricing
https://www.datocms.com/pricing

@sachinmjadhav
Copy link
Contributor

sachinmjadhav commented Aug 26, 2019

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants