New digikam website source available from KDE's git server

[AndriusWild]

On a separate note I would like to suggest adding some videos of how digiKam works.

If something simple will do (record screen, add some text comments and background music) I can help with that.

I guess we would need to determine the top 5-10 features first.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Pat David <[hidden email]>

Date: 2017-04-01 6:56 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: New digikam website source available from KDE's git server

On Fri, Mar 31, 2017 at 11:19 PM Gilles Caulier <[hidden email]> wrote:

On the download section, there are too much text to read to find the right version.

Agreed!  This is one of the pages I was hoping to rewrite soon to be a little clearer.  I had written some small OS detection script I use on www.gimp.org to show the most likely relevant download to users when they visit the page - I could possibly re-use that here if you wanted.

Either way, the page is on the to-do list to re-write to be more direct and clear. :)

To resume :

- screenshots stored in local or not ?

- If stored in local (git), this is acceptable by KDE team to overload the repository with this kind of huge data ?

Re: Screenshots

I know that historically you've hosted your photos on Flickr.  This is fine, but I would personally suggest hosting them locally if possible.

The reason is that if Flickr, for any reason, goes dark - then you'll have a huge amount of dead images across your site.  I'd hate for that to happen!  Even worse, if the images aren't stored anywhere else then there's a chance you'll lose the mapping of what those images should be. :(

In git, we'll have them and won't have to worry about it (and we don't have to worry about a database not liking them on the backend anymore).

I don't think there's a _huge_ amount of files/sizes to worry about, but I guess it's up to Ben to let us know if that'll be ok.

pat

--

[patdavid]

On Sat, Apr 1, 2017 at 9:49 AM Andrey Goreev <[hidden email]> wrote:

On a separate note I would like to suggest adding some videos of how digiKam works.

If something simple will do (record screen, add some text comments and background music) I can help with that.

I guess we would need to determine the top 5-10 features first.

This is an awesome idea! It really could help folks get a feel for what's capable. 

I'd probably defer to the feature highlight list once it's decided to help consistency and cohesiveness. That way the vids could be linked or embedded right on the front page. 

--

[Gilles Caulier-4]

The video are a good way to explain how the application work. I vote for this feature.

Gilles Caulier

[Gilles Caulier-4]

2017-04-01 14:56 GMT+02:00 Pat David <[hidden email]>:

On Fri, Mar 31, 2017 at 11:19 PM Gilles Caulier <[hidden email]> wrote:

On the download section, there are too much text to read to find the right version.

Agreed!  This is one of the pages I was hoping to rewrite soon to be a little clearer.  I had written some small OS detection script I use on www.gimp.org to show the most likely relevant download to users when they visit the page - I could possibly re-use that here if you wanted.

Yes i vote for. OS detection will simplify user life. 

Either way, the page is on the to-do list to re-write to be more direct and clear. :)

To resume :

- screenshots stored in local or not ?

- If stored in local (git), this is acceptable by KDE team to overload the repository with this kind of huge data ?

Re: Screenshots

I know that historically you've hosted your photos on Flickr.  This is fine, but I would personally suggest hosting them locally if possible.

The reason is that if Flickr, for any reason, goes dark - then you'll have a huge amount of dead images across your site.  I'd hate for that to happen!  Even worse, if the images aren't stored anywhere else then there's a chance you'll lose the mapping of what those images should be. :(

In git, we'll have them and won't have to worry about it (and we don't have to worry about a database not liking them on the backend anymore).

I don't think there's a _huge_ amount of files/sizes to worry about, but I guess it's up to Ben to let us know if that'll be ok.

So we wait Ben response for that.

Gilles Caulier

Le 01/04/2017 à 14:56, Pat David a écrit :
>
>
> On Fri, Mar 31, 2017 at 11:19 PM Gilles Caulier
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     On the download section, there are too much text to read to find the
>     right version.

Please, everybody, keep the link to the future web site to ùmakes it
easy to see it :-) thanks


> I don't think there's a _huge_ amount of files/sizes to worry about, but
> I guess it's up to Ben to let us know if that'll be ok.

I agree and every photo/kde user should be aware of "kim", the kde image
manipulation "plugin" that add to the image context menu a way to scale
the images to the exact size needed :-)

thanks for the good job done :-)

jdd

[patdavid]

On Sat, Apr 1, 2017 at 11:38 AM jdd <[hidden email]> wrote:

Please, everybody, keep the link to the future web site to ùmakes it
easy to see it :-) thanks

For future reference, the staging version of the website will be found at:

https://staging.digikam.org

thanks for the good job done :-)

Glad to help! :)

--

[Simon Frei]

The layout looks indeed pretty neat already. I really liked the grey & read combination on the old website, but maybe that's just habituation and it is time for something new.
On a side note: With the two column news layout we definitely need to produce more news. Having a "digiKam x.y.0 is released" entry beneath a "digiKam x.z.0 is released" entry isn't particularly interesting.

On 01/04/17 19:42, Pat David wrote:

On Sat, Apr 1, 2017 at 11:38 AM jdd <[hidden email]> wrote:

Please, everybody, keep the link to the future web site to ùmakes it
easy to see it :-) thanks

For future reference, the staging version of the website will be found at:

https://staging.digikam.org

thanks for the good job done :-)

Glad to help! :)

--

[Dmitri Popov-2]

It's a good idea only if someone will keep the videos updated. The
pace of digiKam's development will make most videos outdated in a
matter of months, and having obsolete videos on the website doesn't
make a good impression.

Best,
Dmitri

On Sat, Apr 1, 2017 at 4:48 PM, Andrey Goreev <[hidden email]> wrote:

> On a separate note I would like to suggest adding some videos of how digiKam
> works.
> If something simple will do (record screen, add some text comments and
> background music) I can help with that.
> I guess we would need to determine the top 5-10 features first.
>
>
> Sent from my Samsung Galaxy smartphone.
>
> -------- Original message --------
> From: Pat David <[hidden email]>
> Date: 2017-04-01 6:56 AM (GMT-07:00)
> To: digiKam - Home Manage your photographs as a professional with the power
> of open source <[hidden email]>
> Subject: Re: New digikam website source available from KDE's git server
>
>
>
> On Fri, Mar 31, 2017 at 11:19 PM Gilles Caulier <[hidden email]>
> wrote:
>>
>> On the download section, there are too much text to read to find the right
>> version.
>
>
> Agreed!  This is one of the pages I was hoping to rewrite soon to be a
> little clearer.  I had written some small OS detection script I use on
> www.gimp.org to show the most likely relevant download to users when they
> visit the page - I could possibly re-use that here if you wanted.
>
> Either way, the page is on the to-do list to re-write to be more direct and
> clear. :)
>
>
>>>
>>> To resume :
>>>
>>> - screenshots stored in local or not ?
>>> - If stored in local (git), this is acceptable by KDE team to overload
>>> the repository with this kind of huge data ?
>
>
> Re: Screenshots
>
> I know that historically you've hosted your photos on Flickr.  This is fine,
> but I would personally suggest hosting them locally if possible.
>
> The reason is that if Flickr, for any reason, goes dark - then you'll have a
> huge amount of dead images across your site.  I'd hate for that to happen!
> Even worse, if the images aren't stored anywhere else then there's a chance
> you'll lose the mapping of what those images should be. :(
>
> In git, we'll have them and won't have to worry about it (and we don't have
> to worry about a database not liking them on the backend anymore).
>
> I don't think there's a _huge_ amount of files/sizes to worry about, but I
> guess it's up to Ben to let us know if that'll be ok.
>
> pat
> --
> https://patdavid.net
> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

Le 03/04/2017 à 09:35, Dmitri Popov a écrit :
> It's a good idea only if someone will keep the videos updated. The
> pace of digiKam's development will make most videos outdated in a
> matter of months, and having obsolete videos on the website doesn't
> make a good impression.

since we have appimages, it should be much easier :-)

jdd

[Dmitri Popov-2]

> since we have appimages, it should be much easier :-)

Sure, but re-recording videos still requires time and effort.

Best,
Dmitri

On Mon, Apr 3, 2017 at 10:51 AM, jdd <[hidden email]> wrote:

> Le 03/04/2017 à 09:35, Dmitri Popov a écrit :
>>
>> It's a good idea only if someone will keep the videos updated. The
>> pace of digiKam's development will make most videos outdated in a
>> matter of months, and having obsolete videos on the website doesn't
>> make a good impression.
>
>
> since we have appimages, it should be much easier :-)
>
> jdd
>

Le 03/04/2017 à 11:53, Dmitri Popov a écrit :
>> since we have appimages, it should be much easier :-)
>
> Sure, but re-recording videos still requires time and effort.
>

sure, but before one needed to compile the very last digikam version :-)

jdd

[AndriusWild]

We need to have some kind of a template for the videos then. Something to keep them consistent and easy to make / update.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: jdd <[hidden email]>

Date: 2017-04-03 3:57 AM (GMT-07:00)

To: [hidden email]

Subject: Re: New digikam website source available from KDE's git server

Le 03/04/2017 à 11:53, Dmitri Popov a écrit :
>> since we have appimages, it should be much easier :-)
>
> Sure, but re-recording videos still requires time and effort.
>

sure, but before one needed to compile the very last digikam version :-)

jdd

[pbhj-2]

FWIW as a long term KDE+digikam user I don't think much has changed in
what I do for several years. There's probably more value in slightly out
of date generic videos than in not having videos at all. But I'd agree
that you need someone to own the video production and be prepared to
update them, maybe every year, if there are significant changes.


On 03/04/17 10:53, Dmitri Popov wrote:

>> since we have appimages, it should be much easier :-)
> Sure, but re-recording videos still requires time and effort.
>
> Best,
> Dmitri
>
> On Mon, Apr 3, 2017 at 10:51 AM, jdd <[hidden email]> wrote:
>> Le 03/04/2017 à 09:35, Dmitri Popov a écrit :
>>> It's a good idea only if someone will keep the videos updated. The
>>> pace of digiKam's development will make most videos outdated in a
>>> matter of months, and having obsolete videos on the website doesn't
>>> make a good impression.
>>
>> since we have appimages, it should be much easier :-)
>>
>> jdd
>>

[AndriusWild]

Staging.digiKam.org already looking amazing!

Couple suggestions:
1. Link to google drive repo to download Pre-Release Bundles is missing.
2. Add an ability to subscribe to digikam news and posts on the website. This in combination with "digiKam tip of the day/week" will create more traffic on the website.

[Alexander Langley]

The website looks excellent! I'm very pleased that everything works without JavaScript enabled, which is increasingly uncommon these days :/

However, when I disable 3rd party resources, the Flickr images don't load, which reveals that the alt-text for those images is not very descriptive. Could someone work on describing the images appropriately so that people who use screen readers (or nutcases like me who disable 3rd party resources) can tell what the images are?

Also, some of the h3s on the Contribute page have anchor tags so that they can be linked to. Currently, those anchor tags enclose the headers, making them appear to be clickable links. This looks kind of confusing, so I think it would be prudent to either not enclose the h3, or to add a style rule that makes the foreground color for a[name] and a[name]:hover the same as for an un-wrapped h3. 

- Alexander

On Apr 8, 2017, 09:53 -0400, AndriusWild <[hidden email]>, wrote:

Staging.digiKam.org already looking amazing!

Couple suggestions:
1. Link to google drive repo to download Pre-Release Bundles is missing.
2. Add an ability to subscribe to digikam news and posts on the website.
This in combination with "digiKam tip of the day/week" will create more
traffic on the website.



--
View this message in context: http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-from-KDE-s-git-server-tp4695351p4695543.html
Sent from the digikam-users mailing list archive at Nabble.com.

[Sveinn í Felli-2]

Þann lau  8.apr 2017 14:05, skrifaði Alexander Langley:
> However, when I disable 3rd party resources, the Flickr images don't
> load, which reveals that the alt-text for those images is not very
> descriptive. Could someone work on describing the images
> appropriately so that people who use screen readers (or nutcases like
> me who disable 3rd party resources) can tell what the images are?

Also, the screenshots image on the landing page seems to be served by a
3rd party: <https://placehold.it/1920x1280>

Which is annoying, because it triggers many tracking defenses.

Best regards,
Sveinn í Felli

[Mica Semrick]

New posts will have their resources served from the digikam domain, however, there are ~350 old posts with images from flickr. That's a lot of migration work, as is adding alt tags.

We welcome patches for this effort. :) Otherwise it'll be a slow migration. If someone is interested in scripting it, please let me know so we can talk about folder structure.

-m

On April 8, 2017 7:05:15 AM PDT, Alexander Langley <[hidden email]> wrote:

The website looks excellent! I'm very pleased that everything works without JavaScript enabled, which is increasingly uncommon these days :/

However, when I disable 3rd party resources, the Flickr images don't load, which reveals that the alt-text for those images is not very descriptive. Could someone work on describing the images appropriately so that people who use screen readers (or nutcases like me who disable 3rd party resources) can tell what the images are?

Also, some of the h3s on the Contribute page have anchor tags so that they can be linked to. Currently, those anchor tags enclose the headers, making them appear to be clickable links. This looks kind of confusing, so I think it would be prudent to either not enclose the h3, or to add a style rule that makes the foreground color for a[name] and a[name]:hover the same as for an un-wrapped h3. 

- Alexander

On Apr 8, 2017, 09:53 -0400, AndriusWild <[hidden email]>, wrote:

Staging.digiKam.org already looking amazing!

Couple suggestions:
1. Link to google drive repo to download Pre-Release Bundles is missing.
2. Add an ability to subscribe to digikam news and posts on the website.
This in combination with "digiKam tip of the day/week" will create more
traffic on the website.



--
View this message in context: http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-from-KDE-s-git-server-tp4695351p4695543.html
Sent from the digikam-users mailing list archive at Nabble.com.

[patdavid]

I was going to scrape all the old Flickr images locally - Mica, what should I do for folder structure?

I'll look into fixing the anchor headings styling to avoid confusion.

Need a bug tracker for the website to capture/track these. :)

On Sat, Apr 8, 2017 at 11:28 AM Mica Semrick <[hidden email]> wrote:

New posts will have their resources served from the digikam domain, however, there are ~350 old posts with images from flickr. That's a lot of migration work, as is adding alt tags.

We welcome patches for this effort. :) Otherwise it'll be a slow migration. If someone is interested in scripting it, please let me know so we can talk about folder structure.

-m

On April 8, 2017 7:05:15 AM PDT, Alexander Langley <[hidden email]> wrote:

The website looks excellent! I'm very pleased that everything works without JavaScript enabled, which is increasingly uncommon these days :/

However, when I disable 3rd party resources, the Flickr images don't load, which reveals that the alt-text for those images is not very descriptive. Could someone work on describing the images appropriately so that people who use screen readers (or nutcases like me who disable 3rd party resources) can tell what the images are?

Also, some of the h3s on the Contribute page have anchor tags so that they can be linked to. Currently, those anchor tags enclose the headers, making them appear to be clickable links. This looks kind of confusing, so I think it would be prudent to either not enclose the h3, or to add a style rule that makes the foreground color for a[name] and a[name]:hover the same as for an un-wrapped h3. 

- Alexander

On Apr 8, 2017, 09:53 -0400, AndriusWild <[hidden email]>, wrote:

Staging.digiKam.org already looking amazing!

Couple suggestions:
1. Link to google drive repo to download Pre-Release Bundles is missing.
2. Add an ability to subscribe to digikam news and posts on the website.
This in combination with "digiKam tip of the day/week" will create more
traffic on the website.



--
View this message in context: http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-from-KDE-s-git-server-tp4695351p4695543.html
Sent from the digikam-users mailing list archive at Nabble.com.

--

[Mica Semrick]

Something like /static/IMG/<post_file_name>/IMG.jpg would work. Or you could go by post year/month.

I'd like to avoid having a thousand images in one directory.

-,m

On April 8, 2017 2:51:58 PM PDT, Pat David <[hidden email]> wrote:

I was going to scrape all the old Flickr images locally - Mica, what should I do for folder structure?

I'll look into fixing the anchor headings styling to avoid confusion.

Need a bug tracker for the website to capture/track these. :)

On Sat, Apr 8, 2017 at 11:28 AM Mica Semrick <[hidden email]> wrote:

New posts will have their resources served from the digikam domain, however, there are ~350 old posts with images from flickr. That's a lot of migration work, as is adding alt tags.

We welcome patches for this effort. :) Otherwise it'll be a slow migration. If someone is interested in scripting it, please let me know so we can talk about folder structure.

-m

On April 8, 2017 7:05:15 AM PDT, Alexander Langley <[hidden email]> wrote:

The website looks excellent! I'm very pleased that everything works without JavaScript enabled, which is increasingly uncommon these days :/

However, when I disable 3rd party resources, the Flickr images don't load, which reveals that the alt-text for those images is not very descriptive. Could someone work on describing the images appropriately so that people who use screen readers (or nutcases like me who disable 3rd party resources) can tell what the images are?

Also, some of the h3s on the Contribute page have anchor tags so that they can be linked to. Currently, those anchor tags enclose the headers, making them appear to be clickable links. This looks kind of confusing, so I think it would be prudent to either not enclose the h3, or to add a style rule that makes the foreground color for a[name] and a[name]:hover the same as for an un-wrapped h3. 

- Alexander

On Apr 8, 2017, 09:53 -0400, AndriusWild <[hidden email]>, wrote:

Staging.digiKam.org already looking amazing!

Couple suggestions:
1. Link to google drive repo to download Pre-Release Bundles is missing.
2. Add an ability to subscribe to digikam news and posts on the website.
This in combination with "digiKam tip of the day/week" will create more
traffic on the website.



--
View this message in context: http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-from-KDE-s-git-server-tp4695351p4695543.html
Sent from the digikam-users mailing list archive at Nabble.com.

--

[AndriusWild]

I have noticed that it is only possible to see the latest news and there is no
way to open the full list of news...

On Saturday, April 8, 2017 6:27:18 PM MDT you wrote:

> Something like /static/IMG/<post_file_name>/IMG.jpg would work. Or you could
> go by post year/month.
>
> I'd like to avoid having a thousand images in one directory.
>
> -,m
>
> On April 8, 2017 2:51:58 PM PDT, Pat David <[hidden email]> wrote:
> >I was going to scrape all the old Flickr images locally - Mica, what
> >should
> >I do for folder structure?
> >
> >I'll look into fixing the anchor headings styling to avoid confusion.
> >
> >Need a bug tracker for the website to capture/track these. :)
> >On Sat, Apr 8, 2017 at 11:28 AM Mica Semrick <[hidden email]>
> >
> >wrote:
> >> New posts will have their resources served from the digikam domain,
> >> however, there are ~350 old posts with images from flickr. That's a
> >
> >lot of
> >
> >> migration work, as is adding alt tags.
> >>
> >> We welcome patches for this effort. :) Otherwise it'll be a slow
> >> migration. If someone is interested in scripting it, please let me
> >
> >know so
> >
> >> we can talk about folder structure.
> >>
> >>
> >> -m
> >>
> >>
> >> On April 8, 2017 7:05:15 AM PDT, Alexander Langley <
> >> [hidden email]> wrote:
> >>
> >> The website looks excellent! I'm very pleased that everything works
> >> without JavaScript enabled, which is increasingly uncommon these days
> >:
> >:/
> >:
> >> However, when I disable 3rd party resources, the Flickr images don't
> >
> >load,
> >
> >> which reveals that the alt-text for those images is not very
> >
> >descriptive.
> >
> >> Could someone work on describing the images appropriately so that
> >
> >people
> >
> >> who use screen readers (or nutcases like me who disable 3rd party
> >> resources) can tell what the images are?
> >>
> >> Also, some of the h3s on the Contribute page have anchor tags so that
> >
> >they
> >
> >> can be linked to. Currently, those anchor tags enclose the headers,
> >
> >making
> >
> >> them appear to be clickable links. This looks kind of confusing, so I
> >
> >think
> >
> >> it would be prudent to either not enclose the h3, or to add a style
> >
> >rule
> >
> >> that makes the foreground color for a[name] and a[name]:hover the
> >
> >same as
> >
> >> for an un-wrapped h3.
> >>
> >> - Alexander
> >>
> >> On Apr 8, 2017, 09:53 -0400, AndriusWild <[hidden email]>, wrote:
> >>
> >> Staging.digiKam.org already looking amazing!
> >>
> >> Couple suggestions:
> >> 1. Link to google drive repo to download Pre-Release Bundles is
> >
> >missing.
> >
> >> 2. Add an ability to subscribe to digikam news and posts on the
> >
> >website.
> >
> >> This in combination with "digiKam tip of the day/week" will create
> >
> >more
> >
> >> traffic on the website.
> >>
> >>
> >>
> >> --
> >
> >> View this message in context:
> >http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-f
> >rom-KDE-s-git-server-tp4695351p4695543.html>
> >> Sent from the digikam-users mailing list archive at Nabble.com.
> >>
> >> --
> >
> >https://patdavid.net
> >GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
>
> _______________________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-f
> rom-KDE-s-git-server-tp4695351p4695553.html
>
> To unsubscribe from New digikam website source available from KDE's git
> server, visit
> http://digikam.1695700.n4.nabble.com/template/NamlServlet.jtp?macro=unsubsc
> ribe_by_code&node=4695351&code=YWVnb3JlZXZAZ21haWwuY29tfDQ2OTUzNTF8Mjg0NjkwN
> jE5