What can the pixls.us photographic community help DigiKam?
richm+digikam at oldelvet.org.uk
Mon Mar 20 11:37:00 GMT 2017
On 20/03/2017 09:53, Dmitri Popov wrote:
> I would very much like to keep this discussion going forward, as
> digiKam is in a dire need of a new and improved website.
I agree with Dmitri. This is a good opportunity to utilise the skills of
a group who have a proven track record delivering top notch sites.
On a technical level I like the idea of static site generation. The live
site would have fewer dependencies and hence there is much less to go
wrong and/or exploit.
My only concern is whether the static site content management can be
made sufficiently straightfoward for non-technical digikam users to
contribute content to the website.
Mica/Pat can hopefully share their experiences here and guide towards a
workflow that would work for these users. I know that git is much more
user friendly these days with many graphical packages available. A
simple text editor can edit the markdown and a continuous integration
system can do all the magic to make the finished site appear in situ.
I'm not really one to judge what is simple given that I use git daily in
my non-digikam life.
> On Fri, Mar 17, 2017 at 7:04 AM, Mica Semrick <mica at silentumbrella.com> wrote:
>> Static sties operate very simply: there are a few templates and content
>> pages. The content is moved through the templates based on how the
>> templating logic is written. We would first do a little analysis to see what
>> content you want to migrate from the current site to the new site. Then we'd
>> identify any other necessary features. Then we'd use one of several export
>> and convert tools to move the content into files on the file system, clean
>> them up, then design the new site.
>> As for the history of the current site, we can migrate all applicable
>> content, but if you mean database history, most converters don't exporting
>> database history. You can always download a copy of the database in case it
>> is needed for further use.
>> As far as technical details are concerned, I am familiar with the static
>> site generators: middleman (ruby), hugo (go), and metalsmith
>> current host as all a static site requires is a webserver and a way to
>> upload the site. If you're in need of hosting, it can likely be done on the
>> same server as the main pixls.us site. The static site is maintained in git
>> or similar and access to add or alter posts and content is handled by a git
>> host such as githib or gitlab. If CI is involved, then we can build the site
>> on commits to the master branch and deploy the site via rsync or sftp if the
>> site builds successfully. Examples of sites completed are my own site
>> silentumbrella.com, pixls.us, and gimp.org.
>> On March 16, 2017 12:13:31 PM PDT, Gilles Caulier <caulier.gilles at gmail.com>
>>> 2017-03-16 5:00 GMT+01:00 <mica at silentumbrella.com>:
>>>> Greetings DigiKam Users,
>>>> Thank you for making such a fantastic application and congrats on the
>>>> 5.5.0 release!
>>>> My name is Mica and I'm a community member over at https://pixls.us. We
>>>> promote free software for photographers.
>>>> We have a forum at https://discuss.pixls.us where we are already
>>>> providing official support for RawTherapee, G'MIC, and Rapid Photo
>>>> Downloader, but we're willing to host any discussion around FOSS photography
>>>> applications. We can setup a category for digikam as well if you're
>>>> interested, though we understand if you have your own infrastructure.
>>>> I also read you're in need of a new website/web admin. If the project is
>>>> interested in moving away from Drupal and to a static site generator, we'd
>>>> be willing to assist in that project as well. Pat David recently helped GIMP
>>>> migrate to a new static site. Looking at the DigiKam website, I don't see
>>>> too much dynamic content.
>>> Right for the requirement. A new web site must be planed quickly (dixit
>>> KDE team request about security issues with old Drupal 6)
>>> You propose something about a static web site, so without a CMS. What's
>>> about the story of the site. All will be lost ?
>>> What do you propose as technical details for this static web site ? Where
>>> it will be hosted ? Did you have any example already done ?
>>> Gilles Caulier
>>> PS : I would like digiKam users imply a little bit with this topic as it
>>> can be managed without complexity. Web site is not like the one million of
>>> C++ code lines from digiKam...
More information about the Digikam-users