DominoKit and SEO

[jsfan3]

If I understand correctly, a website created with DominoKit is basically a Single Page Application (SAP). Is this correct?

Since all content is generated by Javascript, does it mean that it is invisible to search engines? Maybe not, because this search shows your v1 demo on Google:

https://www.google.com/search?q=%22Java+based+lightweight+UI+library+that+in+addition+to+performance+and+functionality+brings+elegance+to+enterprise+web+applications%22&sca_esv=1e35dc1f4110e681&source=hp&ei=EGShZ6ySC7ywi-gPguac6QY

I would like to know if you have analyzed this problem and if you have any answers.

[niloc132]

Two misconceptions:

While Domino-UI can be used to produce a SPA, it need not be used that way. Domino UI is a widget library, rather than a framework that drives how your application must be built/structured, or drives how you write code or interact with pages. With that said, it frequently is used for rich webapps, often hidden behind authentication (so SEO can't reach it anyway) - but that isn't a requirement, plain webpages can be enhanced as well.

Second, SEO hasn't required for many years that content be visible in plain html, with no running JS. There are certainly limitations to what JS can run, and if a page/app might be penalized due to the perception of usability issues, but most search engines will index dynamically created content. If you prioritize all content being reachable, a server-side rendering (SSR) solution may be of interest instead (or in addition).

[vegegoku]

In addition to what @niloc132 said I would note that dominokit.com Is a website with static pages and make use of Domino-ui and other Dominokit tools, for example checking the domino-ui documentation and examples we render those inside static pages. it comes with some technical details on how to implement this, but I consider building a website and a web application are 2 different things, I had to use a technique to mix domino-ui in static pages because I wanted to add all those domino-ui samples there.

[Ri-gers]

As a side note, is the code available for how to build/structure the layout as you did for example in https://dominokit.com/solutions/domino-ui/v2/docs/getting-started? I especially like the NavigationBar and content menu on the left, would really help to learn how to effectivly use it

[vegegoku]

That is a little bit complicated, it is actually a static html content with some extra markup attribute, then on page load I apply some javascript (java ofc) that process the links to actually open/close menu items.

It is should be available here https://github.com/DominoKit/domino-site if you wish to study how it works, but it might need some effort and knowledge in different dominokit tools

[Ri-gers]

Ah okay, I didn't know you used static content, thought you built that using the domino-ui components directly as in the source code examples on the demo site, which I planed to do as well. Thank you for the info though

[vegegoku]

That is doable with domino-ui too, but my reasoning for doing it with static content is that I wanted everything that is not an actual demo sample to be a static content,

[Ri-gers]

Yeah I thought so thx, tried to do that a while ago, but couldnt get it to look like yours - for example for some reason the bar below the navbar separated the navbar in two parts by default somehow. The navbar items would then show up above the bar and nothing below it, wasting space and making it look off

[FrankHossfeld]

Thanks to @TDesjardins Nalu has some SEO-features. Might be an helpful: https://github.com/NaluKit/nalu/wiki/17.-SEO#seo-support