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.

Sign up for GitHub

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

Jump to bottom

Document homepage content workaround #2240

Closed
jzacsh opened this issue Jun 28, 2016 · 4 comments
Closed

Document homepage content workaround #2240

jzacsh opened this issue Jun 28, 2016 · 4 comments
Labels
Docs Outdated

Comments

@jzacsh
Copy link

jzacsh commented Jun 28, 2016 •
edited

tl;dr is markdown inclusion for homepage already being worked on? if not i'll just send a pull request to document that markdown (and in turn shortcodes) require a workaround hardcoding the page title in an if~ish statement.

If no one is working on it at the moment, and a patch would be welcome to fix some of this, I'd be happy to help. Would it be acceptable to just have a hardcoded file-check for a content/index.* file when rendering a homepage node?
@bep
Copy link
Member

bep commented Jun 28, 2016

Would it be acceptable to just have a hardcoded file-check for a content/index.* file when rendering a homepage node?

The problem needs a better solution, and a temporary solution like this is bad if we decide for some other naming scheme. A document patch about the workaround would be welcomed, though.

@bep bep added the Docs label Jun 28, 2016
@bep bep changed the title patch to either document homepage limitations or fix some? Document homepage content workaround Jun 28, 2016
@bep
Copy link
Member

bep commented Jul 21, 2016

Will be handled in #2297.

@bep bep closed this as completed Jul 21, 2016
@jzacsh
Copy link
Author

jzacsh commented Jul 21, 2016

thanks! (and sorry for the radio silence - i totally forgot about this)

@github-actions
Copy link

github-actions bot commented Apr 4, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Docs Outdated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jzacsh @bep