thefrontside / thefrontside/frontside.com
improve content page curation strategy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently we are "manually" entering the information to curate specific podcast episodes, and merging it with curated articles. We want to continue curating, but make it easier to enter (and less prone to error, see the article array reference).
@jorgelainfiesta, should we expect to pick specific articles and podcasts? Or are you most interested in the most recent of both? I think if we want specific articles/podcasts, we could have an array of slugs in gatsby-node.js or gatsby-config.js (a matter of preference really).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/templates/blog-list.js, especially the podcast curation at lines 14-99 and article merge at lines 127-138. Compare the proposed curation locations in gatsby-node.js and gatsby-config.js, and clarify whether specific articles and podcasts or the most recent items should be selected. Done means curated content can be entered more easily with fewer reference errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100