Hi all, yes, thanks Otto for that hint.
But I still think that exactly like Edgent (I never ever touched the website build as I didn't want to learn how to do and setup everything) What I really really like with our setup is the simplicity of being able to contribute. If you want to add a page, simply add an adoc-file, if you want it in the menu add an entry and commit&push the changes and wait a few minues. It seems the Nifi page doesn’t use bootstrap, but jquery directly. The Edgent page uses bootstrap. I think it should be pretty easy to whip up a template that uses bootstrap to generate the site. And if in contrast to all of the general purpose skins, we just build one for us, there is no need for complicated configuration as we simply build the skin for us and us alone. I just whipped up a simple skin using the maven-archetype-site-skin and it seems to be very simple to do so. I'll commit and push that in the develop branch of the build-tools as it doesn't have any side effects. All you need to do to use it, is to replace the skin dependency in the site.xml of the plx4x-parent module. So with a custom PLC4X skin we can build a skin exactly a we need it, we can dramatically simplify our pom configuration in the plc4x-parent project (as we don't need to customize and patch everything) So I am in extremely strong favor to build our own skin. And a colleague of mine at codecentric expressed his will to work on something like that (Well ... let's see if the will is strong enough to actually do something and it doesn't end at expressing the will to do something) Chris Am 27.09.19, 15:19 schrieb "Julian Feinauer" <[email protected]>: Hi Otto, thanks fort he hint... just checked their repo https://github.com/apache/nifi-site (which has a really nice readme). I think Edgent was done similar. And I have to agree with Chris that our current flow is WAY easier so we really have to think about this and I see lots of advantages to stick with what we currently have as its really nice, easy and (!!!) Agile (!!!). : ) Julian Am 27.09.19, 14:59 schrieb "Otto Fowler" <[email protected]>: You could look at nifi.apache.org and metron.apache.org. The metron site isn’t too hard to update from my experience, but I think the nifi site is better overall. On September 27, 2019 at 08:54:36, Christofer Dutz ( [email protected]) wrote: Hi Julian, well I do like how the page of IoTDB looks like, however I'm not fond of the workflow needed to update it. With this we would rid ourselves of the easy contribution way we currently have. Thinking about how much we need fresh content on the page I wouldn't like having to make this more complicated. And with VueJS it has one big disadvantage (The same we had with Apache Flex Websites and all "fat client websites") ... Google has problems indexing them. I just tried searching for some of the text on the IoTDB website and was confirmed that the website is completely invisible to Google ... I don't think that's a good idea. I guess I would make the Skin a pet project which I'll work on after work hours. But only if you agree that this is worth doing. The maven fluido-skin is based on a really old bootstrap version and I would simply start with this. Chris Am 27.09.19, 14:32 schrieb "Julian Feinauer" <[email protected]>: Hi Chris, thats tough and I dont have much knowledge about Websites (look at ours __). I like what the IoTDB guys did with vue as it gives you lots of possibilities but I also like the ease of our current approach. I agree that we should make the site a bit nicer but I'm unsure on how to do it : / Perhaps we should lurk arount other Projects a bit (with nice websites) to checkout how they do it / did it... Julian Am 27.09.19, 14:20 schrieb "Christofer Dutz" <[email protected]>: Hi all, I am currently working on making our website look nicer … a few things I would like to do are made particularly difficult by existing skins. Making the output great would require patching on several places. Therefore I think it might be the better idea to take an Apache licensed skin such as one released by the maven team and to create our own based on that. We’ll have to bootstrapify that, but I guess in the end we’ll have soething we can customize to our needs 100% the way we want it to. What do you think? Chris
