@dansup@pixelfed It looks nice, but sometimes people will throw in a tag in the middle of a sentence. If this parses it out, now you've created a grammatical issue with their sentence.
As you can see, you're only addressing the tags as #labels following a post, whilst most folks tend to #hashtag their #articles inline as they type out their posts.
Having a facility to integrate those two methods is of great benefit and note that in my example not all #tags are duplicates between the two methods of presenting them.
@dansup@pixelfed Like the second one much more, looks cleaner, nicer and more organized too. The improve readability is a plus and it can help with accessibility too! I'd say go for the 2nd option, limiting the amount of hashtags visible will also help reduce post clutter and make it a much more enjoyable viewing experience
Looks very nice, but it looks like you are removing the capitalization of the hashtags. Please don't do that because it is important for accessibility.
Screen readers need the capitalization to pronounce the hashtags correctly.
@dansup@pixelfed I much prefer the new version, but as others pointed out, I think maintaining the case is important.
I would also like for the # signal to be kept to make it more explicit, which I feel is specially more relevant when the hashtag is in the middle of the text for example (which I assume would still be possible, it would be horrible to not be able to use hashtags in the middle of the description).
@dansup@pixelfed I prefer the clean approach myself so the 2nd is my choice. But technically it doesn't matter if I happen across something similar to what I'm looking for and it catches my eyes. I'll most likely check it out.
@dansup@pixelfed I like it, I think it's way easier to read. Maybe hiding them by default could be nice. Or even make the amount shown configurable lol.
Would it affect inline #hashtags too? Or just end-of-the-post dumps?
@dansup@pixelfed I would caution against lowercasing tags since concatenated CamelCase words are useful for legibility and accessibility.
Visually this style is more pleasant, but might cause people to new to the platform to not know how to create tags (i.e. by prefixing words/phrases with a #).
You'll also have to contend with how this content appears in feeds or via the API.
@dansup@pixelfedStrongly prefer the separated hashtags where they're parsable (I've mixed thoughts on how to handle inline #hashtags as opposed to ones put at the end).
@dansup@pixelfed The buttons are significantly more readable, but they aren't really recognisable as hashtags anymore. How about adding a # symbol in light grey to the beginning of each button?
@dansup@pixelfed I love this, but my primary concern is losing the context when users rely on inline hashtags. By pulling a tag out of context it can completely break the flow of the post.
If you could identify inline tags and leave the content in place, but add the tag to the footer. It would work fine.