Conserving the knowledge from the old site on the new site seems like an 
obvious good idea.

Is the new site also using Mediawiki so it can be copied without too much 
editing?


I can't promise anything, since Im up to my neck in work, but is seems like 
something us regular users could help with :)


Regards,


Claus


--------------------------------------------------------------

umount /dev/vodka && eject /dev/stomach

-Mplayer crew


________________________________
From: Ktechlab-devel <ktechlab-devel-boun...@kde.org> on behalf of Zoltan 
Padrah <zoltan.pad...@gmail.com>
Sent: Tuesday, August 14, 2018 4:35 PM
To: ktechlab-de...@kde.org; ktechlab-devel@lists.sourceforge.net
Subject: content for website: review of the old website?

Hello everyone,

probably you know that KTechLab's current official website is at:

https://userbase.kde.org/KTechlab
KTechlab - KDE UserBase Wiki<https://userbase.kde.org/KTechlab>
userbase.kde.org
Overview. KTechlab has been designed to be as easy to use and unintrusive as 
possible; all components and FlowParts have context sensitive help, and 
simulating electronics is as simple as dragging components onto the work area 
and creating connectors that autoroute themselves between their pins.


Currently it has very little content, so I propose an effort for adding content 
to it. As first step, it would be useful to review the content from the old 
website at:

https://github.com/ktechlab/ktechlab/wiki

and see what could be copied to the KDE wiki.

If anybody feels like doing that, please notify me.
Currently I'm hacking on KTechLab at Akademy 2018, getting rid of Qt3Support 
dependency.

Have fun,

 Zoltan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ktechlab-devel mailing list
Ktechlab-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ktechlab-devel

Reply via email to