-
Notifications
You must be signed in to change notification settings - Fork 897
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
posts snippets(Markdown) not converted before including in homepage(HTML) #43
Comments
Hi, Are you talking about Thanks |
Hi,
in the homepage, but |
Could you guide me how to truncate the text ? |
Hi @Pro-Panda what do you think of the actual? Is it what you wanted to achieve? |
I am using a quick hack by using a snippet variable and writing it along with post title and tags, in HTML. |
Ok I think I know what you mean, do you have the markdown of the post in http:https://pro-panda.tech? I have multiple request concerning the code layout, I would need to make some test. |
Well the problem is that I didn't want to get title on the excerpt (the small text in the home page). So I strip off all of the HTML and thus the markdown formating. However it is still rendered correctly in the post. With that extent I wanted to achieve a more uniform home page (with title, image or not and normal text beneath.) |
Sorry, this message got skipped. Do you want the code ?
I tried removing |
Well I am ok now, it was to better understand your problem. I will look into how to deal with it. |
…rmat's link" (sylhare#43) When rendering the site an error occurs: WARN 2019/07/02 12:11:16 Page's .RSSLink is deprecated and will be removed in a future release. Use the Output Format's link, e.g. something like: {{ with .OutputFormats.Get "RSS" }}{{ .RelPermalink }}{{ end }}. Related: - gohugoio/hugo#4427
* Remove unused directories * Fix broken links * Fix more links
Posts are written in markdown and their snippet is displayed on home takes it in html. Hence, the contents of the posts aren't properly displayed.
Eg: this post
On the homepage, this post looks a bit odd
The text was updated successfully, but these errors were encountered: