Spaces:
Running
[Support] Community Articles
Share you feedback and questions about the community Articles feature.
Is this the same as community blog posts?
Yes with some nice updates coming!
I just finished my first blog on blog-explores: https://huggingface.co/blog/xingxm/svgdreamer
I'm enjoying it. Thank you for everything! โค๏ธ
@tux I have no clue then.. Maybe related to a 'pro' account or a free one?
yes i was also wondering about that, maybe it's limited to paid accounts, or not included in "community blogposts". I just wanted to verify here because the User Interface is misleading.
https://huggingface.co/spaces/blog-explorers/README/discussions/5#6979bbb4af3bb737305de5dc
I can see the blog articles I wrote on my own homepage, but others cannot see them when visiting my homepage, even in the blog article section, they cannot find my article either. Is my article been blocked? The blog article is https://huggingface.co/blog/imnotkitty/tencent-hy-image-v30-i2i
check if it is private
I tried to put a line break in my title, but was unable to, because this header syntax is not accepted:
You do the work.\
Big Tech takes the model.
=
Blog content must start with a title that is markdown heading level 1 (example: # My First Blog)
That's weird. This is perfect MD, and it's equivalent to:
# You do the work.<br>Big Tech takes the model.
I think both should be accepted, and HF should also strip the title of any markup tags like <br>.
Or maybe just allow the user to type their title in a separate field, like how the thumbnails are attached.
Line breaks aren't allowed in titles
Sorry, I wasn't very clear. Let me clarify.
Currently, HF actually renders the Markdown of the title verbatim when you're viewing the article.
So something like this:
# Title with<br>line break
is accepted, and it renders fine!
The problem is that, in other places on HF, the title will read "Title with<br>line break".
So there's an inconsistency.
Additional header styles seem to be allowed, but they're not parsed correctly on other parts of the website.
In my opinion, the best fix is one of these: either
- allow users to stylize headers as they wish, but automatically parse and clean them so a 'raw text' version can be displayed elsewhere, or
- stop extracting the title from a Markdown header, and create a separate UI where users can enter their article titles.
If HF truly wants to ban additional stylization like line breaks, they should go with the second option.
The other part of my complaint was that a perfectly syntactic header was not accepted.
This is a header
=
This syntax is equivalent to # This is a header, but for some reason it doesn't count.


