i18n support

[lospringliu]

To use the built components, it does not have multi language support

To use the source directly, it is too tightly coupled with windicss

Is it possible to include i18n?

[davay42]

That's reasonable! With this we need a plan of some kind :)

Such mass of pug+windi is important on the first stage of rapid prototyping and then I plan to transition to a more traditional CSS class based approach for more flexible component styling.

With i18n it's the same problem. I have an experience of building my previous gin+vue app with i18n from the start, but it made development a little more conservative and slowed transformations.

So I see these things at some next level being implemented for a more stabilized code base. I.e. today I've renamed all post.descriptions to post.statements in order to make them more tweet-like and make users start new feeds more easily. It was just one search and replace.

May be we can bring it in gradually? Or make the interface less depending on the language (use descriptive icons and better UI design)?

[lospringliu]

sure, I see rapid changes

[davay42]

I think for now we can just use props and slots to make the button names easy to change.