It isn't linked yet, I need to make the page. The URL is http://staging.digikam.org/news/
-m On April 8, 2017 10:30:55 PM PDT, AndriusWild <[hidden email]> wrote:
I have noticed that it is only possible to see the latest news and there is no |
In reply to this post by AndriusWild
The page has been added to the main menu and pushed to
https://staging.digikam.org -m On 2017-04-08 22:30, AndriusWild wrote: > 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] [1]> > 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] [2]> >> > >> >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] [3]> 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] [4]>, > 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 > [5] >> >rom-KDE-s-git-server-tp4695351p4695543.html> >> >> Sent from the digikam-users mailing list archive at Nabble.com. >> >> >> >> -- >> > >> >https://patdavid.net [6] >> >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 > [5] >> 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 > [7] >> > ribe_by_code&node=4695351&code=YWVnb3JlZXZAZ21haWwuY29tfDQ2OTUzNTF8Mjg0NjkwN > >> jE5 > > ------------------------- > View this message in context: Re: New digikam website source > available from KDE's git server [8] > Sent from the digikam-users mailing list archive [9] at Nabble.com. > > > Links: > ------ > [1] > http://webmail.gandi.net/user/SendEmail.jtp?type=node&node=4695555&i=0 > [2] > http://webmail.gandi.net/user/SendEmail.jtp?type=node&node=4695555&i=1 > [3] > http://webmail.gandi.net/user/SendEmail.jtp?type=node&node=4695555&i=2 > [4] > http://webmail.gandi.net/user/SendEmail.jtp?type=node&node=4695555&i=3 > [5] > http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-f > [6] https://patdavid.net > [7] > http://digikam.1695700.n4.nabble.com/template/NamlServlet.jtp?macro=unsubsc > [8] > http://digikam.1695700.n4.nabble.com/New-digikam-website-source-available-from-KDE-s-git-server-tp4695351p4695555.html > [9] http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
On download page : MacOS 32 bits version do not exist. OSX is only 64 bits since many years now... Gilles Caulier 2017-04-10 1:19 GMT+02:00 <[hidden email]>: The page has been added to the main menu and pushed to https://staging.digikam.org |
I'm about to fix this, but it uncovers another question: On the /downloads/ page, there are currently links directly to each architecture/OS. I think this is a good idea personally, as it gets users directly to the most relevant version right away. However, the links would need to be updated manually to always point to the appropriate binaries. Is someone prepared to keep these links updated as needed? I know you're on a pretty quick release cycle, which is awesome (every 2-3 months it seems). Of course, we're happy to update them also as long as someone remembers to ping us when to! pat On Sun, Apr 9, 2017 at 11:40 PM Gilles Caulier <[hidden email]> wrote:
-- https://patdavid.net GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC |
One way to handle this is to have the build system created a symlink, such as digikam-latest-linux-appimage-x64.appimage, to the actual latest version, the we point the HTML link and the symlink and we are good.
-m On April 10, 2017 8:21:28 AM PDT, Pat David <[hidden email]> wrote:
|
In reply to this post by patdavid
2017-04-10 17:21 GMT+02:00 Pat David <[hidden email]>:
Yes, it's perfect.
For the moment, it's will be delayed a little bits. 5.6.0 must come with new web site (first suitable version not fully completed).
Well look the file name for tarball, appimage, PKG, and windows installer. It's always the same. Only the version number change as x.y.z (5.6.0 for the next one) As the place to store download files is always the same, a simple script with a regex to check the last available version can be easy to do to switch automatically on the right file depending of the detected OS. Gilles |
In reply to this post by pbhj-2
The website indeed looks amazing - thanks once again to everyone that
makes it possible! The following is already in nitpick mode, but I wanted to have it written down such that I don't forget (a new component in the bug tracker would probably be helpful, e.g. "Website"): - The Meta subchapters should not be hidden behind the main "Meta" topic in the bottom menu bar. - In my opinion the meta chapters would fit better under Documentation. - About subtopics should be alphabetically ordered (now it is maybe ordered by importance, but I think that's confusing). - In the download page the two-line "Linux AppImage" resulting in non-aligned 64-/32-bit links looks not so nice. I think it would look better if it was somehow squeezed into one line or all three titles (Windows, Mac, ...) aligned centrally and using the same amount of vertical space. |
2017-04-11 10:30 GMT+02:00 Simon Frei <[hidden email]>: The website indeed looks amazing - thanks once again to everyone that Done. digiKam/Website section in bugzilla is just created. Please use it for next report of missing parts/features or dysfunctions. Gilles - The Meta subchapters should not be hidden behind the main "Meta" |
In reply to this post by Simon Frei
Thanks for the notes, Simon. I welcome any other constructive criticisms, as I feel we are almost done; we just need a bit more polish.
We've been talking about where to keep notes and to does going forward; is the bug tracker the right place? -m On April 11, 2017 1:30:30 AM PDT, Simon Frei <[hidden email]> wrote:
The website indeed looks amazing - thanks once again to everyone that |
yes. bugzilla is the shell of the project. The section dedicated to website can be used to list main pending tasks. The only condition to use it is to close entries step by step when job is done. Gilles 2017-04-11 16:13 GMT+02:00 Mica Semrick <[hidden email]>:
|
In reply to this post by AndriusWild
> 1. Link to google drive repo to download Pre-Release Bundles is
> missing. This was link wasn't present on the drupal site, was it? My thoughts are that a link from the site to google drive isn't appropriate. If the link is shared via the mailing list then OK, at least the people who get it from the mailing list know where and how to report back. > 2. Add an ability to subscribe to digikam news and posts on the > website. Done. > This in combination with "digiKam tip of the day/week" will create more > traffic on the website. That'd be a fantastic contribution! -m On 2017-04-08 06:44, AndriusWild 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. |
In reply to this post by Alexander Langley
> However, when I disable 3rd party resources, the Flickr images don't
> load, We're looking at a script to grab all the flickr images and fix the links in the content, but I wouldn't consider this request a blocker to going live. > 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? Certainly we should work on this, but it's a lot of manual work that can't be automated if you want it done well :) > 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. I've styled the text so it's the same color as a non-linked header. Your cursor still changes on hover, but I don't think you can change that behavior. -m On 2017-04-08 07:05, Alexander Langley 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. |
In reply to this post by Simon Frei
> - The Meta subchapters should not be hidden behind the main "Meta"
> topic in the bottom menu bar. What else should it be called? > - In my opinion the meta chapters would fit better under > Documentation. I agree and I've moved the meta pages under documentation. > - About subtopics should be alphabetically ordered (now it is maybe > ordered by importance, but I think that's confusing). Done. All footer links are now ordered alphabetically. > - In the download page the two-line "Linux AppImage" resulting in > non-aligned 64-/32-bit links looks not so nice. Fixed. -m On 2017-04-11 01:30, Simon Frei wrote: > The website indeed looks amazing - thanks once again to everyone that > makes it possible! > > The following is already in nitpick mode, but I wanted to have it > written down such that I don't forget (a new component in the bug > tracker would probably be helpful, e.g. "Website"): > - The Meta subchapters should not be hidden behind the main "Meta" > topic in the bottom menu bar. > - In my opinion the meta chapters would fit better under > Documentation. > - About subtopics should be alphabetically ordered (now it is maybe > ordered by importance, but I think that's confusing). > - In the download page the two-line "Linux AppImage" resulting in > non-aligned 64-/32-bit links looks not so nice. I think it would look > better if it was somehow squeezed into one line or all three titles > (Windows, Mac, ...) aligned centrally and using the same amount of > vertical space. |
The daily tip is a great idea, but maybe a weekly tip is more
realistic? I'd be happy to contribute to this secton. Best, Dmitri On Thu, Apr 13, 2017 at 8:43 AM, <[hidden email]> wrote: >> - The Meta subchapters should not be hidden behind the main "Meta" >> topic in the bottom menu bar. > > > What else should it be called? > >> - In my opinion the meta chapters would fit better under Documentation. > > > I agree and I've moved the meta pages under documentation. > >> - About subtopics should be alphabetically ordered (now it is maybe >> ordered by importance, but I think that's confusing). > > > Done. All footer links are now ordered alphabetically. > >> - In the download page the two-line "Linux AppImage" resulting in >> non-aligned 64-/32-bit links looks not so nice. > > > Fixed. > > -m > > > On 2017-04-11 01:30, Simon Frei wrote: >> >> The website indeed looks amazing - thanks once again to everyone that >> makes it possible! >> >> The following is already in nitpick mode, but I wanted to have it >> written down such that I don't forget (a new component in the bug >> tracker would probably be helpful, e.g. "Website"): >> - The Meta subchapters should not be hidden behind the main "Meta" >> topic in the bottom menu bar. >> - In my opinion the meta chapters would fit better under Documentation. >> - About subtopics should be alphabetically ordered (now it is maybe >> ordered by importance, but I think that's confusing). >> - In the download page the two-line "Linux AppImage" resulting in >> non-aligned 64-/32-bit links looks not so nice. I think it would look >> better if it was somehow squeezed into one line or all three titles >> (Windows, Mac, ...) aligned centrally and using the same amount of >> vertical space. > > |
In reply to this post by Mica Semrick
2017-04-13 8:37 GMT+02:00 <[hidden email]>: 1. Link to google drive repo to download Pre-Release Bundles is missing. Yes, it is. I was add myself this url to shared the pre build bundles. My thoughts are that a link from the site to google drive isn't appropriate. If the link is shared via the mailing list then OK, at least the people who get it from the mailing list know where and how to report back. This si the repository of GDrive digiKam developer account. We use it to prevent to pass to Phabricator to just share a non official release of digiKam for testing. This is very important to verify quickly if a bug is fixed or not. We don't want to pass to the long mechanism of validation in KDE engine to share a bundle for testing purpose. I build myself the bundles. It take a time. Sometime i build more than one version by weeks. We need a quick system to share file. GDrive is perfect. I upload files and that all... No need to create an entry in phabricator and wait that something from KDE team process the job. Sometime it take 2 or 3 days. Best Gilles Caulier |
In reply to this post by Mica Semrick
Yep I think you are right. I will try to contribute too. I will post it here if I came up with any ideas. Let's try to keep the tips as brief as possible. Something that is very easy to read. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Dmitri Popov <[hidden email]> Date: 2017-04-13 1:11 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 realistic? I'd be happy to contribute to this secton. Best, Dmitri On Thu, Apr 13, 2017 at 8:43 AM, <[hidden email]> wrote: >> - The Meta subchapters should not be hidden behind the main "Meta" >> topic in the bottom menu bar. > > > What else should it be called? > >> - In my opinion the meta chapters would fit better under Documentation. > > > I agree and I've moved the meta pages under documentation. > >> - About subtopics should be alphabetically ordered (now it is maybe >> ordered by importance, but I think that's confusing). > > > Done. All footer links are now ordered alphabetically. > >> - In the download page the two-line "Linux AppImage" resulting in >> non-aligned 64-/32-bit links looks not so nice. > > > Fixed. > > -m > > > On 2017-04-11 01:30, Simon Frei wrote: >> >> The website indeed looks amazing - thanks once again to everyone that >> makes it possible! >> >> The following is already in nitpick mode, but I wanted to have it >> written down such that I don't forget (a new component in the bug >> tracker would probably be helpful, e.g. "Website"): >> - The Meta subchapters should not be hidden behind the main "Meta" >> topic in the bottom menu bar. >> - In my opinion the meta chapters would fit better under Documentation. >> - About subtopics should be alphabetically ordered (now it is maybe >> ordered by importance, but I think that's confusing). >> - In the download page the two-line "Linux AppImage" resulting in >> non-aligned 64-/32-bit links looks not so nice. I think it would look >> better if it was somehow squeezed into one line or all three titles >> (Windows, Mac, ...) aligned centrally and using the same amount of >> vertical space. > > |
Free forum by Nabble | Edit this page |