Hello!
Forem is known to be a developer-focused open source Forum, and I'm loving it.
However now I'm trying to implement it for a different Target Audience - Lawyers in Chech Republic.
Lawyers and Programmers work differently, therefore I'm experiencing some difficulties:
1) is Google oAuth support coming any soon?
Is there a reason all major omniauth providers are already included, except Google?
Does it make sence for me to write my own Google oAuth integration?
2) Tags supporting national symbols and spaces
I understand that there are problems with parsing tags in markdown with spaces/symbols...
Here are some examples of Czech national symbols: Γ‘, Δ, Δ, Γ©, Δ, Γ, Ε, Γ³, Ε, Ε‘, Ε₯, ΓΊ, Ε―, Γ½, ΕΎ
Without using them, you can't really use the language. Imagine writing in English without letters a, i, t. Not very cool, right? :)
I tried doing a workaround, but it's quite hard as Forem is a very big tool, and running tests, at least on my machine, takes 40+ minutes:
3) i18n support
I think a forum can really thrive, when it can be very local. Not each forum targets all english-speaking community in the world. Is 18n support planned any time soon? I can personally help translating en.yml files to ua.yml, cz.yml, ru.yml, if there will be an 18n feature.
4) WYSWYG support
Will it be available? I personally LOVE markdown, but it creates a barrier for non-tech-savvy people.
As a basic example, I really love how markdown is done with some wyswig elements in Github:
5) Customize forem on my own VS central changes?
Where would you suggest me to draw a line between customizing features on my own VS having something done centrally? I'm afraid of over-customizing and not being able to merge central changes :) But, I guess it is a general dilemma of forks...
Oldest comments (12)
Ahoj!
Work on this is in progress, see github.com/forem/forem/issues/14745
A PR laying the groundwork will be merged after Codeland (the conference we're running on Thursday and Friday) is over. Stay tuned for any follow-up announcements.
github.com/forem/forem/pull/14620
This is a frequent request, we're currently internally researching options.
If you think your ideas/customizations would make sense for a wider audience, please post a feature request here. As you said, maintaining a divergent fork is a lot of work and you may not be able to painlessly update your selfhosted Forem instance if it diverges too much from our one.
Did that help? π
4) WYSWYG support
This is a frequent request, we're currently internally researching options.
There was a promise to do something about the editor in the around Q3 2021 (forem.dev/lisasy/comment/1kl). Any news on this issue?
github.com/forem/forem/issues/14794
This is the newest issue and discussion around WYSWYG support.
We had a big change in our Product team recently and they are getting up to speed with all the requests from the community but have prioritized this one.
@citizen428 Re github.com/forem/forem/pull/14620, if this means the dev team is ready to accept actual i18n of the code base strings, and unless you already have extracted them, I'm willing to PR the whole bunch of locale files and i18n-converted code (covers almost all of views) we have so far. What would you say?
That sounds absolutely wonderful! Could you give us a few days though? We're currently hosting the CodeLand conference, so a lot of the team's attention is there. And we probably should have Ben's initial PR merged first.
Edit: we'll also need to update contributing docs, etc. to be explicit about not adding untranslated strings directly to views, etc. especially with Hacktoberfest being around the corner.
Yes, thank you. It's just good to know that i18n availability comes before long. Having some leeway is also good for me to prepare and organize the code for proposal.
If you need a mostly working i18n-supported instance now, we have one:
gitlab.com/yheuhtozr/forem
It is currently loaded with many site-specific customizations, but commits are separated and I can make a pure i18n-only branch if you need.
github.com/forem/forem/pull/14620
This seems very promising and I'm considering how to adapt for it, but it lacks support for Slavic languages by design in the current shape as I looked at it.
looks fantastic!
Actually I aws thinking there'd be more defaults to translate here. So if it gets merged, count me in - I'll translate couple of more languages! ;)
There will be π We used Ben's PR as a way to hash out the overall structure of our I18n approach. Once this is merged there'll be a lot more to translate eventually. We just want to get this right, as it will impact the workflow of everyone who contributes to the codebase, both external and internal.
Thanks a lot for the replies!!!
And what about google oAuth? I didn't find anything in the issues/PR section
Update: my mistake - tags should not generally have spaces. I've checked instagram, twitter - not tags with spaces:
my tag- bad.my_tag- good.I didn't answer this one because I have no information and have not been part of any discussions on this topic, so I'd rather say nothing than giving you wrong information.
What about Google OmniAuth login?