LukasJoswiak / LukasJoswiak/etch
Menu Items and Displaying Multiple Blog Posts in Different Blog Sections
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 307
- Forks
- 164
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I want to create a new section of my 'etch' blog titled 'links' which displays similarly to the 'posts' section, but with different blog posts than the 'posts' section. More or less, I want to have my main menu have the following items: "posts", "links", "about". The "about" page provided in the 'etch' defaults loads a single 'about' page. The 'posts' link simply displays all of the blog posts located in the content/posts directory. I want the 'links' section of the blog to have a collection of blog posts distinct from the set of blog posts in the 'posts' section.
I created a new directory in the 'content' directory named "links", created an entry in the config file named 'links", and created an entry in the [permalinks] section of my config as follows:
[permalinks] posts = "/:title" links = "/links/:title"
Yet when I click the new 'links' menu item on my blog page, the browser simply displays the same content as the 'posts' section of the blog. Is my goal achievable with etch, or is etch intended to be used with one section (the 'posts' section) being home to blog posts and the other menu items ('about' section) being single static pages?
Thank you.
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
Review the content/posts and content/links directories, the Hugo config entry for links, and the [permalinks] settings shown in the issue. Trace how the posts and links menu entries are rendered, then determine whether separate post collections can be supported and what configuration or theme changes would be required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hugo
- Domain
- content, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100