Hi! I'm one of the happy KVision users and I use it with Fomantic-UI (<https://fomantic-ui.com>) ins...

# kvision

[Osmium]

Hi! I'm one of the happy KVision users and I use it with Fomantic-UI (https://fomantic-ui.com) instead of Bootstrap. I think about writing package that brings Fomantic elements to KVision.

A few questions:
• Is someone interested in Fomantic-UI support at all?
• How would I better contribute it? Via fork of main/master branch and creating pull request with module, or it's better to create completely separate repository with its own versioning?

[lorefnon]

Unrelated to KVision, but curious why you prefer fomantic over bootstrap ? Used semantic-ui in past, but this is the first time I have heard of this fork.

[Osmium]

Semantic/Fomantic is more rich in terms of variety of available styles, components etc. It allows to build pages that are more complex than bootstrap. IMO.

[Robert Jaros]

Hi, have you any experience with Fomantic and accessibility (WCAG)?

[Robert Jaros]

Bootstrap is not 100% accessible but it can be made quite easily wcag compatible with custom color theme.

[Robert Jaros]

I've read Fomantic has accessibility issues.

[Robert Jaros]

But of course creating fomantic module would be great. It's always better to have choice 🙂

[Robert Jaros]

The decision whether to create separate repo or just making PRs is up to you. I think both ways should generally work fine. But it's possible you will need to make some changes in the core module as well. You could have more problems with version compatibility with a separate repo.

[Osmium]

I have experience with Fomantic itself, but I didn't searched what it offers in accessibility. I'll learn more about WCAG tomorrow and will be thankful if you provide some useful resources or pages.

Actually, I don't have a lot of experience with Fomantic, I'm about to learn custom theming etc, but I know enough to write a library.

I thought and I think that I don't want to mess with core internals and firstly create separate repo. And if project will succeed or benefits from working in the same repo and versions will be obvious, I'll make a PR.

[Robert Jaros]

I was just curious if you had some accessibility experience. No need to dive into this if you don't need - it's quite complicated topic 🙂

[Osmium]

Another small question -- what do you think about naming components -- it it better to name FomanticButton, for example, so it wouldn't clash with KVision's pl.treksoft.kvision.html.Button? and same for all other components

[Osmium]

Accessibility is complicated, yes, but important. I know people with disabilities and I think they'll be glad if I will keep their problems in mind 😃

[Robert Jaros]

For OnsenUI components I've followed the convention with Ons prefix. So there is OnsButton, OnsText, OnsRadio and so on. You could create FoButton for example.

[Robert Jaros]

Not as long as Fomantic but easy to remember.