What can the pixls.us photographic community help DigiKam?
Locked
12
12
Re: What can the pixls.us photographic community help DigiKam?
 
|
2017-03-22 8:35 GMT+01:00 <[hidden email]>: Hello all, |
Re: [What can the pixls.us photographic community help DigiKam?] and [digikam.org : Webmaster wanted...]
|
|
In reply to this post by Jürgen Blumenschein
> Btw. Could a static site offer multilanguage support?
Yes it does! -m On 2017-03-20 05:00, [hidden email] wrote: > Hallo, > > I thought about how I can give back a little of my resources for using > DK a long time. I have some experiences with Typo3 but none with > Drupal. > > So I'll at this moment only my support in translating if you are going > to build a multilanguage Website. As I see there are at least some > german, > french and spanish speaking people on the list. The acceptance of DK > could > improve if there are more languages supported. > My help in administrating digikam.org could be a second step, but not > for now. > > Btw. Could a static site offer multilanguage support? > > Jürgen > > Zitat von Dmitri Popov <[hidden email]>: > >> I would very much like to keep this discussion going forward, as >> digiKam is in a dire need of a new and improved website. >> >> Best, >> Dmitri >> >> On Fri, Mar 17, 2017 at 7:04 AM, Mica Semrick >> <[hidden email]> wrote: >>> Hello, >>> >>> 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 >>> (javascript/nodejs). As far as hosting goes, you can continue to use >>> your >>> 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. >>> >>> Best, >>> Mica >>> >>> >>> On March 16, 2017 12:13:31 PM PDT, Gilles Caulier >>> <[hidden email]> >>> wrote: >>>> >>>> >>>> >>>> 2017-03-16 5:00 GMT+01:00 <[hidden email]>: >>>>> >>>>> 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 ? >>>> >>>> Best >>>> >>>> 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... >>>> >>>> >>> |
Re: What can the pixls.us photographic community help DigiKam?
|
|
In reply to this post by Gilles Caulier-4
I've started hacking on a template here:
https://github.com/pixlsus/digikam_website_theme. I registered a KDE Identity and I'll request developer access this weekend. Questions about the content: 1. About > Screenshots page: Are these up to date? Do we really need all of them? 2. FAQ page: Can we collapse this into one page? 3. I'd like to stream line some of the content pages, as there are many, what are the thoughts on this? 4. Is there any color scheme anyone had in mind? If possible, please provide hex codes. This far I've borrowed a few colors from the KDE website. Lastly, are there any additions that anyone would like to see to the website? Best, Mica On 2017-03-22 00:36, Gilles Caulier wrote: > Ben Cooksley email is <[hidden email]> > > Gilles Caulier > > 2017-03-22 8:35 GMT+01:00 <[hidden email]>: > >> Hello all, >> >> I can get in touch with Ben if someone would like to send me his >> contact information. >> >> A quick recap, so we're all on the same page: >> - drupal site being shut down on March 31 >> - migration to static site using Hugo (http://gohugo.io [1]) and a >> redesign proposed >> -- template based on Zurb Foundation 6 >> -- current URLs taken into account & can generate redirects >> - requires webhosting, which pixls.us [2] can provide, but pixls.us >> [2] members would like to use KDE/digikam's current hosting if >> possible >> -- static site requires only a webserver such as apache and rsync >> over SSH access to the webroot for digikam.org [3] >> - site maintained in git; authorization determined by hosting >> platform, e.g. github, gitlab, >> - continuous integration like TraviCI, can be used to build and >> deploy the site when a commit is pushed to master >> - current admin should back up the drupal database for posterity >> - current pages (but not page history) can be migrated >> >> Pat was kind enough to write a script to scrape all the news >> articles from digikam.org [3], which composed the bulk of content to >> be migrated, and format the results with the proper metadata for >> hugo. I set up the project scaffolding and migrated some of the >> non-news pages (there are pages that still need to be migrated). >> >> You can see the content we've migrated so far here: >> https://github.com/pixlsus/digikam_website [4] >> >> There probably isn't much more content to migrate. I'll follow up >> with some questions about the content and migrate the remaining >> necessary pages. >> >> You can run hugo locally to see the progress: >> $ wget >> > https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >> [5] >> $ tar -zxvf hugo_0.19_Linux-64bit.tar.gz >> $ git clone https://github.com/pixlsus/digikam_website [4] >> $ cd digikam_website/themes >> $ git clone https://github.com/tummychow/lanyon-hugo [6] >> $ cd .. >> $ ./path/to/hugo serve --theme=lanyon-hugo >> >> I can't say we'll have a 100% finished & beautiful website by March >> 31, but I believe we can be pretty close to finished & very >> functional by that date. >> >> Best, >> Mica >> >> On 2017-03-21 23:37, Gilles Caulier wrote: >> >> Note : when Ben said " I think it's best if they contact us with >> the >> details they require. I'd rather >> not read a long mailing list thread." : the "they" want mean >> Pixls.us >> team of course.... >> >> Gilles Caulier >> >> 2017-03-22 7:36 GMT+01:00 Gilles Caulier <[hidden email]>: >> >> Hi all, >> >> This is the response from Ben by private mail : >> >> // --------------------------------------------------- >> >> Hi Gilles, >> >> Given the amount of work which we've put in thus far and the time >> constraints Sysadmin is under in getting other things done, I think >> it's best if they contact us with the details they require. I'd >> rather >> not read a long mailing list thread. >> >> At this stage, i'll be shutting down the Drupal 6 instance on March >> 31 >> as we need to protect the security of KDE Infrastructure as a first >> priority. This migration has effectively been ready to go (theme >> aside) since early February, with the only reason for the delay >> being >> your requirement a theme be customised for Digikam and nobody being >> able to do it. >> >> Regards, >> Ben >> >> // >> ------------------------------------------------------------------- >> >> So it become urgent to switch to a new web site. "Static" proposal >> from pixls.us [2] [1] sound like the best solution. >> >> Comments are welcome. Please be constructive. >> >> Thanks in advance >> >> Gilles Caulier >> >> 2017-03-21 10:49 GMT+01:00 Gilles Caulier >> <[hidden email]>: >> >> The contact to KDE team about current www.digikam.org [7] [2] is >> Ben >> >> Cooksley <[hidden email]> >> >> I CC him to contribute to this thread... >> >> Gilles Caulier >> >> 2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>: >> Pat, >> >> Thank you for the detailed outline. If there is anything I can help >> you with, please do let me know. >> >> Best, >> Dmitri >> >> On Mon, Mar 20, 2017 at 10:13 PM, Pat David <[hidden email]> >> wrote: >> The intention here is to provide a new, modern website that is >> secure and >> maintainable. >> >> Let me address a couple of possible questions up front: >> >> 1. The existing site content can be ported over to a new site. >> This >> includes previous posts in news/blogs and all of the more static >> pages as >> they exist right now. >> >> The only thing we may have a problem with would be the comment >> system used >> by Drupal. In this case, old comments are likely not going to get >> brought >> over as actual _comments_. We can probably bring them over as >> plain content >> that gets appended to existing news/blog items. >> >> 2. I analyzed the existing site quickly, and noticed that as far >> as content >> pages go, we were looking (roughly) at: >> >> About >> Overview >> Features >> Awards & Reviews >> Related Projects & links >> Screenshots >> Testimonials >> News * >> Release Plan >> Changelog >> Events >> Developers Blogs * >> Download >> digiKam Recipes Book >> Documentation >> Wiki >> FAQ >> Support >> Donation & Sponsor >> Splash-screens >> Contribute >> Contact >> >> Items marked with (*) are the most likely candidates for more >> frequently >> published content. The rest of the pages are probably fairly >> consistent and >> don't change all that often (every release maybe?). >> >> 3. Contributing to the site is easy, just write your content in a >> plain-text >> markdown file. >> >> I assume that you don't want to let everyone publish material to >> your >> website? No matter what the system (CMS/Static/Whatever), you >> likely want a >> check step in the publishing process. In the case of a static >> site, it's >> handled by commit access to the repo. If someone w/o access wants >> to >> publish something, send the plain-text file to someone with commit >> access. >> >> At GIMP, we can accept patches, or someone can just email the >> plain-text >> files (+ assets) and one of us with commit access manages the >> rest. >> >> 4. Comments can be handled the same way we are currently doing it >> on >> pixls.us [2] [1], that is - an embed at the bottom of a post will >> display a threaded >> conversation about that topic hosted on https://discuss.pixls.us >> [8] >> [3]. >> >> --- >> >> At the end of the day we want to help, and we know that the dev >> team likely >> would rather be hacking on Digikam. As such, we're ready and >> willing to get >> a new site up and running, and to help manage things. >> >> Just let us know if we _shouldn't_ continue working on the site. >> :) >> >> Also, is there a contact person for the infrastructure your >> running the site >> on now? I'm assuming a server that the kde folks have somewhere? >> >> pat >> >> PS (interesting sidenote): >> I scraped the existing site quickly to get this, and it appears to >> me that >> over the past 5 years the _majority_ of the posts are from two >> submitters >> (digikam + Dmitri). >> A table of posts per person by year, since 2006: >> https://paste.gnome.org/pwbvlr6ha [9] [4] >> >> -- >> https://patdavid.net [10] [5] >> GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC > > Links: > ------ > [1] http://pixls.us [2] > [2] http://www.digikam.org [7] > [3] https://discuss.pixls.us [8] > [4] https://paste.gnome.org/pwbvlr6ha [9] > [5] https://patdavid.net [10] > > > > Links: > ------ > [1] http://gohugo.io > [2] http://pixls.us > [3] http://digikam.org > [4] https://github.com/pixlsus/digikam_website > [5] > https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz > [6] https://github.com/tummychow/lanyon-hugo > [7] http://www.digikam.org > [8] https://discuss.pixls.us > [9] https://paste.gnome.org/pwbvlr6ha > [10] https://patdavid.net |
Re: What can the pixls.us photographic community help DigiKam?
|
|
Hi Mica,
First of all, thank you for going ahead with the project! I don't have much to say about the structure and template, but I think that some content needs to be revised. For example, some entries in the FAQ section are outdated, while others need editing. I'd like to do that once the new website is operational, but I'd need an access to the new website and maybe some basic instructions on how to add and edit contents. Thanks, Dmitri On Fri, Mar 24, 2017 at 8:20 AM, <[hidden email]> wrote: > I've started hacking on a template here: > https://github.com/pixlsus/digikam_website_theme. I registered a KDE > Identity and I'll request developer access this weekend. > > Questions about the content: > 1. About > Screenshots page: Are these up to date? Do we really need all of > them? > 2. FAQ page: Can we collapse this into one page? > 3. I'd like to stream line some of the content pages, as there are many, > what are the thoughts on this? > 4. Is there any color scheme anyone had in mind? If possible, please provide > hex codes. This far I've borrowed a few colors from the KDE website. > > Lastly, are there any additions that anyone would like to see to the > website? > > Best, > Mica > > > On 2017-03-22 00:36, Gilles Caulier wrote: >> >> Ben Cooksley email is <[hidden email]> >> >> Gilles Caulier >> >> 2017-03-22 8:35 GMT+01:00 <[hidden email]>: >> >>> Hello all, >>> >>> I can get in touch with Ben if someone would like to send me his >>> contact information. >>> >>> A quick recap, so we're all on the same page: >>> - drupal site being shut down on March 31 >>> - migration to static site using Hugo (http://gohugo.io [1]) and a >>> redesign proposed >>> -- template based on Zurb Foundation 6 >>> -- current URLs taken into account & can generate redirects >>> - requires webhosting, which pixls.us [2] can provide, but pixls.us >>> [2] members would like to use KDE/digikam's current hosting if >>> possible >>> -- static site requires only a webserver such as apache and rsync >>> over SSH access to the webroot for digikam.org [3] >>> - site maintained in git; authorization determined by hosting >>> platform, e.g. github, gitlab, >>> - continuous integration like TraviCI, can be used to build and >>> deploy the site when a commit is pushed to master >>> - current admin should back up the drupal database for posterity >>> - current pages (but not page history) can be migrated >>> >>> Pat was kind enough to write a script to scrape all the news >>> articles from digikam.org [3], which composed the bulk of content to >>> be migrated, and format the results with the proper metadata for >>> hugo. I set up the project scaffolding and migrated some of the >>> non-news pages (there are pages that still need to be migrated). >>> >>> You can see the content we've migrated so far here: >>> https://github.com/pixlsus/digikam_website [4] >>> >>> There probably isn't much more content to migrate. I'll follow up >>> with some questions about the content and migrate the remaining >>> necessary pages. >>> >>> You can run hugo locally to see the progress: >>> $ wget >>> >> >> https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >>> >>> [5] >>> $ tar -zxvf hugo_0.19_Linux-64bit.tar.gz >>> $ git clone https://github.com/pixlsus/digikam_website [4] >>> $ cd digikam_website/themes >>> $ git clone https://github.com/tummychow/lanyon-hugo [6] >>> >>> $ cd .. >>> $ ./path/to/hugo serve --theme=lanyon-hugo >>> >>> I can't say we'll have a 100% finished & beautiful website by March >>> 31, but I believe we can be pretty close to finished & very >>> functional by that date. >>> >>> Best, >>> Mica >>> >>> On 2017-03-21 23:37, Gilles Caulier wrote: >>> >>> Note : when Ben said " I think it's best if they contact us with >>> the >>> details they require. I'd rather >>> not read a long mailing list thread." : the "they" want mean >>> Pixls.us >>> team of course.... >>> >>> Gilles Caulier >>> >>> 2017-03-22 7:36 GMT+01:00 Gilles Caulier <[hidden email]>: >>> >>> Hi all, >>> >>> This is the response from Ben by private mail : >>> >>> // --------------------------------------------------- >>> >>> Hi Gilles, >>> >>> Given the amount of work which we've put in thus far and the time >>> constraints Sysadmin is under in getting other things done, I think >>> it's best if they contact us with the details they require. I'd >>> rather >>> not read a long mailing list thread. >>> >>> At this stage, i'll be shutting down the Drupal 6 instance on March >>> 31 >>> as we need to protect the security of KDE Infrastructure as a first >>> priority. This migration has effectively been ready to go (theme >>> aside) since early February, with the only reason for the delay >>> being >>> your requirement a theme be customised for Digikam and nobody being >>> able to do it. >>> >>> Regards, >>> Ben >>> >>> // >>> ------------------------------------------------------------------- >>> >>> So it become urgent to switch to a new web site. "Static" proposal >>> from pixls.us [2] [1] sound like the best solution. >>> >>> Comments are welcome. Please be constructive. >>> >>> Thanks in advance >>> >>> Gilles Caulier >>> >>> 2017-03-21 10:49 GMT+01:00 Gilles Caulier >>> <[hidden email]>: >>> >>> The contact to KDE team about current www.digikam.org [7] [2] is >>> >>> Ben >>> >>> Cooksley <[hidden email]> >>> >>> I CC him to contribute to this thread... >>> >>> Gilles Caulier >>> >>> 2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>: >>> Pat, >>> >>> Thank you for the detailed outline. If there is anything I can help >>> you with, please do let me know. >>> >>> Best, >>> Dmitri >>> >>> On Mon, Mar 20, 2017 at 10:13 PM, Pat David <[hidden email]> >>> wrote: >>> The intention here is to provide a new, modern website that is >>> secure and >>> maintainable. >>> >>> Let me address a couple of possible questions up front: >>> >>> 1. The existing site content can be ported over to a new site. >>> This >>> includes previous posts in news/blogs and all of the more static >>> pages as >>> they exist right now. >>> >>> The only thing we may have a problem with would be the comment >>> system used >>> by Drupal. In this case, old comments are likely not going to get >>> brought >>> over as actual _comments_. We can probably bring them over as >>> plain content >>> that gets appended to existing news/blog items. >>> >>> 2. I analyzed the existing site quickly, and noticed that as far >>> as content >>> pages go, we were looking (roughly) at: >>> >>> About >>> Overview >>> Features >>> Awards & Reviews >>> Related Projects & links >>> Screenshots >>> Testimonials >>> News * >>> Release Plan >>> Changelog >>> Events >>> Developers Blogs * >>> Download >>> digiKam Recipes Book >>> Documentation >>> Wiki >>> FAQ >>> Support >>> Donation & Sponsor >>> Splash-screens >>> Contribute >>> Contact >>> >>> Items marked with (*) are the most likely candidates for more >>> frequently >>> published content. The rest of the pages are probably fairly >>> consistent and >>> don't change all that often (every release maybe?). >>> >>> 3. Contributing to the site is easy, just write your content in a >>> plain-text >>> markdown file. >>> >>> I assume that you don't want to let everyone publish material to >>> your >>> website? No matter what the system (CMS/Static/Whatever), you >>> likely want a >>> check step in the publishing process. In the case of a static >>> site, it's >>> handled by commit access to the repo. If someone w/o access wants >>> to >>> publish something, send the plain-text file to someone with commit >>> access. >>> >>> At GIMP, we can accept patches, or someone can just email the >>> plain-text >>> files (+ assets) and one of us with commit access manages the >>> rest. >>> >>> 4. Comments can be handled the same way we are currently doing it >>> on >>> pixls.us [2] [1], that is - an embed at the bottom of a post will >>> display a threaded >>> conversation about that topic hosted on https://discuss.pixls.us >>> [8] >>> [3]. >>> >>> --- >>> >>> At the end of the day we want to help, and we know that the dev >>> team likely >>> would rather be hacking on Digikam. As such, we're ready and >>> willing to get >>> a new site up and running, and to help manage things. >>> >>> Just let us know if we _shouldn't_ continue working on the site. >>> :) >>> >>> Also, is there a contact person for the infrastructure your >>> running the site >>> on now? I'm assuming a server that the kde folks have somewhere? >>> >>> pat >>> >>> PS (interesting sidenote): >>> I scraped the existing site quickly to get this, and it appears to >>> me that >>> over the past 5 years the _majority_ of the posts are from two >>> submitters >>> (digikam + Dmitri). >>> A table of posts per person by year, since 2006: >>> https://paste.gnome.org/pwbvlr6ha [9] [4] >>> >>> -- >>> https://patdavid.net [10] [5] >>> GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC >> >> >> Links: >> ------ >> [1] http://pixls.us [2] >> [2] http://www.digikam.org [7] >> [3] https://discuss.pixls.us [8] >> [4] https://paste.gnome.org/pwbvlr6ha [9] >> [5] https://patdavid.net [10] >> >> >> >> Links: >> ------ >> [1] http://gohugo.io >> [2] http://pixls.us >> [3] http://digikam.org >> [4] https://github.com/pixlsus/digikam_website >> [5] >> >> https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >> [6] https://github.com/tummychow/lanyon-hugo >> [7] http://www.digikam.org >> [8] https://discuss.pixls.us >> [9] https://paste.gnome.org/pwbvlr6ha >> [10] https://patdavid.net > > |
Re: What can the pixls.us photographic community help DigiKam?
|
|
In reply to this post by Mica Semrick
2017-03-24 8:20 GMT+01:00 <[hidden email]>: I've started hacking on a template here: https://github.com/pixlsus/dig yes a simple screenshots page is mandatory, but simplified to a single view and of course updated. This can be done later. An empty page is enough for the moment. 2. FAQ page: Can we collapse this into one page? yes sure. 3. I'd like to stream line some of the content pages, as there are many, what are the thoughts on this? Yes, this is the goal of the simplification. I need to llok what can be done exactly. 4. Is there any color scheme anyone had in mind? If possible, please provide hex codes. This far I've borrowed a few colors from the KDE website. Certainly. But a black color based theme will be better as digiKam is photo application. I'm not sure if KDE website use this kind of theme.
Nothing against the existing. So for the moment, to reproduce the current one is enough. We will see later for improvements. I need to ask to others developers, after a first pre-release version to review. best Gilles Caulier |
Re: What can the pixls.us photographic community help DigiKam?
|
|
In reply to this post by Dmitri Popov-2
Dmitri, You must ask to a KDE git account. web site source code will be hosted in git now. There is no CMS anymore. Gilles 2017-03-24 10:00 GMT+01:00 Dmitri Popov <[hidden email]>: Hi Mica, |
Re: What can the pixls.us photographic community help DigiKam?
|
|
Thanks, Gilles! I'll do that. Do you know whom I should contact to get
a KDE Git account? Best, Dmitri On Fri, Mar 24, 2017 at 11:25 AM, Gilles Caulier <[hidden email]> wrote: > Dmitri, > > You must ask to a KDE git account. web site source code will be hosted in > git now. There is no CMS anymore. > > Gilles > > 2017-03-24 10:00 GMT+01:00 Dmitri Popov <[hidden email]>: >> >> Hi Mica, >> >> First of all, thank you for going ahead with the project! I don't have >> much to say about the structure and template, but I think that some >> content needs to be revised. For example, some entries in the FAQ >> section are outdated, while others need editing. I'd like to do that >> once the new website is operational, but I'd need an access to the new >> website and maybe some basic instructions on how to add and edit >> contents. >> >> Thanks, >> Dmitri >> >> On Fri, Mar 24, 2017 at 8:20 AM, <[hidden email]> wrote: >> > I've started hacking on a template here: >> > https://github.com/pixlsus/digikam_website_theme. I registered a KDE >> > Identity and I'll request developer access this weekend. >> > >> > Questions about the content: >> > 1. About > Screenshots page: Are these up to date? Do we really need all >> > of >> > them? >> > 2. FAQ page: Can we collapse this into one page? >> > 3. I'd like to stream line some of the content pages, as there are many, >> > what are the thoughts on this? >> > 4. Is there any color scheme anyone had in mind? If possible, please >> > provide >> > hex codes. This far I've borrowed a few colors from the KDE website. >> > >> > Lastly, are there any additions that anyone would like to see to the >> > website? >> > >> > Best, >> > Mica >> > >> > >> > On 2017-03-22 00:36, Gilles Caulier wrote: >> >> >> >> Ben Cooksley email is <[hidden email]> >> >> >> >> Gilles Caulier >> >> >> >> 2017-03-22 8:35 GMT+01:00 <[hidden email]>: >> >> >> >>> Hello all, >> >>> >> >>> I can get in touch with Ben if someone would like to send me his >> >>> contact information. >> >>> >> >>> A quick recap, so we're all on the same page: >> >>> - drupal site being shut down on March 31 >> >>> - migration to static site using Hugo (http://gohugo.io [1]) and a >> >>> redesign proposed >> >>> -- template based on Zurb Foundation 6 >> >>> -- current URLs taken into account & can generate redirects >> >>> - requires webhosting, which pixls.us [2] can provide, but pixls.us >> >>> [2] members would like to use KDE/digikam's current hosting if >> >>> possible >> >>> -- static site requires only a webserver such as apache and rsync >> >>> over SSH access to the webroot for digikam.org [3] >> >>> - site maintained in git; authorization determined by hosting >> >>> platform, e.g. github, gitlab, >> >>> - continuous integration like TraviCI, can be used to build and >> >>> deploy the site when a commit is pushed to master >> >>> - current admin should back up the drupal database for posterity >> >>> - current pages (but not page history) can be migrated >> >>> >> >>> Pat was kind enough to write a script to scrape all the news >> >>> articles from digikam.org [3], which composed the bulk of content to >> >>> be migrated, and format the results with the proper metadata for >> >>> hugo. I set up the project scaffolding and migrated some of the >> >>> non-news pages (there are pages that still need to be migrated). >> >>> >> >>> You can see the content we've migrated so far here: >> >>> https://github.com/pixlsus/digikam_website [4] >> >>> >> >>> There probably isn't much more content to migrate. I'll follow up >> >>> with some questions about the content and migrate the remaining >> >>> necessary pages. >> >>> >> >>> You can run hugo locally to see the progress: >> >>> $ wget >> >>> >> >> >> >> >> >> https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >> >>> >> >>> [5] >> >>> $ tar -zxvf hugo_0.19_Linux-64bit.tar.gz >> >>> $ git clone https://github.com/pixlsus/digikam_website [4] >> >>> $ cd digikam_website/themes >> >>> $ git clone https://github.com/tummychow/lanyon-hugo [6] >> >>> >> >>> $ cd .. >> >>> $ ./path/to/hugo serve --theme=lanyon-hugo >> >>> >> >>> I can't say we'll have a 100% finished & beautiful website by March >> >>> 31, but I believe we can be pretty close to finished & very >> >>> functional by that date. >> >>> >> >>> Best, >> >>> Mica >> >>> >> >>> On 2017-03-21 23:37, Gilles Caulier wrote: >> >>> >> >>> Note : when Ben said " I think it's best if they contact us with >> >>> the >> >>> details they require. I'd rather >> >>> not read a long mailing list thread." : the "they" want mean >> >>> Pixls.us >> >>> team of course.... >> >>> >> >>> Gilles Caulier >> >>> >> >>> 2017-03-22 7:36 GMT+01:00 Gilles Caulier <[hidden email]>: >> >>> >> >>> Hi all, >> >>> >> >>> This is the response from Ben by private mail : >> >>> >> >>> // --------------------------------------------------- >> >>> >> >>> Hi Gilles, >> >>> >> >>> Given the amount of work which we've put in thus far and the time >> >>> constraints Sysadmin is under in getting other things done, I think >> >>> it's best if they contact us with the details they require. I'd >> >>> rather >> >>> not read a long mailing list thread. >> >>> >> >>> At this stage, i'll be shutting down the Drupal 6 instance on March >> >>> 31 >> >>> as we need to protect the security of KDE Infrastructure as a first >> >>> priority. This migration has effectively been ready to go (theme >> >>> aside) since early February, with the only reason for the delay >> >>> being >> >>> your requirement a theme be customised for Digikam and nobody being >> >>> able to do it. >> >>> >> >>> Regards, >> >>> Ben >> >>> >> >>> // >> >>> ------------------------------------------------------------------- >> >>> >> >>> So it become urgent to switch to a new web site. "Static" proposal >> >>> from pixls.us [2] [1] sound like the best solution. >> >>> >> >>> Comments are welcome. Please be constructive. >> >>> >> >>> Thanks in advance >> >>> >> >>> Gilles Caulier >> >>> >> >>> 2017-03-21 10:49 GMT+01:00 Gilles Caulier >> >>> <[hidden email]>: >> >>> >> >>> The contact to KDE team about current www.digikam.org [7] [2] is >> >>> >> >>> Ben >> >>> >> >>> Cooksley <[hidden email]> >> >>> >> >>> I CC him to contribute to this thread... >> >>> >> >>> Gilles Caulier >> >>> >> >>> 2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>: >> >>> Pat, >> >>> >> >>> Thank you for the detailed outline. If there is anything I can help >> >>> you with, please do let me know. >> >>> >> >>> Best, >> >>> Dmitri >> >>> >> >>> On Mon, Mar 20, 2017 at 10:13 PM, Pat David <[hidden email]> >> >>> wrote: >> >>> The intention here is to provide a new, modern website that is >> >>> secure and >> >>> maintainable. >> >>> >> >>> Let me address a couple of possible questions up front: >> >>> >> >>> 1. The existing site content can be ported over to a new site. >> >>> This >> >>> includes previous posts in news/blogs and all of the more static >> >>> pages as >> >>> they exist right now. >> >>> >> >>> The only thing we may have a problem with would be the comment >> >>> system used >> >>> by Drupal. In this case, old comments are likely not going to get >> >>> brought >> >>> over as actual _comments_. We can probably bring them over as >> >>> plain content >> >>> that gets appended to existing news/blog items. >> >>> >> >>> 2. I analyzed the existing site quickly, and noticed that as far >> >>> as content >> >>> pages go, we were looking (roughly) at: >> >>> >> >>> About >> >>> Overview >> >>> Features >> >>> Awards & Reviews >> >>> Related Projects & links >> >>> Screenshots >> >>> Testimonials >> >>> News * >> >>> Release Plan >> >>> Changelog >> >>> Events >> >>> Developers Blogs * >> >>> Download >> >>> digiKam Recipes Book >> >>> Documentation >> >>> Wiki >> >>> FAQ >> >>> Support >> >>> Donation & Sponsor >> >>> Splash-screens >> >>> Contribute >> >>> Contact >> >>> >> >>> Items marked with (*) are the most likely candidates for more >> >>> frequently >> >>> published content. The rest of the pages are probably fairly >> >>> consistent and >> >>> don't change all that often (every release maybe?). >> >>> >> >>> 3. Contributing to the site is easy, just write your content in a >> >>> plain-text >> >>> markdown file. >> >>> >> >>> I assume that you don't want to let everyone publish material to >> >>> your >> >>> website? No matter what the system (CMS/Static/Whatever), you >> >>> likely want a >> >>> check step in the publishing process. In the case of a static >> >>> site, it's >> >>> handled by commit access to the repo. If someone w/o access wants >> >>> to >> >>> publish something, send the plain-text file to someone with commit >> >>> access. >> >>> >> >>> At GIMP, we can accept patches, or someone can just email the >> >>> plain-text >> >>> files (+ assets) and one of us with commit access manages the >> >>> rest. >> >>> >> >>> 4. Comments can be handled the same way we are currently doing it >> >>> on >> >>> pixls.us [2] [1], that is - an embed at the bottom of a post will >> >>> display a threaded >> >>> conversation about that topic hosted on https://discuss.pixls.us >> >>> [8] >> >>> [3]. >> >>> >> >>> --- >> >>> >> >>> At the end of the day we want to help, and we know that the dev >> >>> team likely >> >>> would rather be hacking on Digikam. As such, we're ready and >> >>> willing to get >> >>> a new site up and running, and to help manage things. >> >>> >> >>> Just let us know if we _shouldn't_ continue working on the site. >> >>> :) >> >>> >> >>> Also, is there a contact person for the infrastructure your >> >>> running the site >> >>> on now? I'm assuming a server that the kde folks have somewhere? >> >>> >> >>> pat >> >>> >> >>> PS (interesting sidenote): >> >>> I scraped the existing site quickly to get this, and it appears to >> >>> me that >> >>> over the past 5 years the _majority_ of the posts are from two >> >>> submitters >> >>> (digikam + Dmitri). >> >>> A table of posts per person by year, since 2006: >> >>> https://paste.gnome.org/pwbvlr6ha [9] [4] >> >>> >> >>> -- >> >>> https://patdavid.net [10] [5] >> >>> GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC >> >> >> >> >> >> Links: >> >> ------ >> >> [1] http://pixls.us [2] >> >> [2] http://www.digikam.org [7] >> >> [3] https://discuss.pixls.us [8] >> >> [4] https://paste.gnome.org/pwbvlr6ha [9] >> >> [5] https://patdavid.net [10] >> >> >> >> >> >> >> >> Links: >> >> ------ >> >> [1] http://gohugo.io >> >> [2] http://pixls.us >> >> [3] http://digikam.org >> >> [4] https://github.com/pixlsus/digikam_website >> >> [5] >> >> >> >> >> >> https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >> >> [6] https://github.com/tummychow/lanyon-hugo >> >> [7] http://www.digikam.org >> >> [8] https://discuss.pixls.us >> >> [9] https://paste.gnome.org/pwbvlr6ha >> >> [10] https://patdavid.net >> > >> > > > |
Re: What can the pixls.us photographic community help DigiKam?
|
|
All must be described here : Gilles PS : the git repo for the web site is enable. We just need to populate to start to work. 2017-03-24 12:39 GMT+01:00 Dmitri Popov <[hidden email]>: Thanks, Gilles! I'll do that. Do you know whom I should contact to get |
|
|
All, I've enabled the repo (git clone [hidden email]) for those with dev access that's what i used to clone. It was an empty repo. I've initialized it with a copy of the .commit-template from kdelibs, and I've pushed, so first commit should be in. Dmitri, Mica or I would be happy to help you with writing content - we'll probably also write a meta post somewhere detailing the steps to take and how to use the new system (I did somethign similar with http://www.gimp.org/about/meta). pat On Fri, Mar 24, 2017 at 6:55 AM Gilles Caulier <[hidden email]> wrote:
-- https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC |
Re: What can the pixls.us photographic community help DigiKam?
|
|
2017-03-24 22:37 GMT+01:00 Pat David <[hidden email]>:
Yes, exactly. This is a good idea to resule well the procedure to maintain contents in Hugo web site. Gilles Caulier |
Re: What can the pixls.us photographic community help DigiKam?
|
|
Hi all again, The next stage to complet the Hugo migration is : - to setup the test website. - to patch the curretn Hugo implementation in KDE git repository - to test results. - to setup the target website with Hugo code in goal to publish final result on Internet. Q : - Where will be hosted test and new target web site ? The current one is hosted on KDE infrastructures. This will be always the case with Hugo port ? Best Gilles Caulier 2017-03-25 8:22 GMT+01:00 Gilles Caulier <[hidden email]>:
|
|
|
meta: This all seems more like a dev discussion, I'm getting this on
digikam-users ... whilst I appreciate it's good for users to be
involved in dev I'm not sure spamming them with dev discussions
will achieve that end. Apologies if I've erred I'm new on the
'users' mailing list. On 25/03/2017 09:25, Gilles Caulier
wrote:
|
Re: What can the pixls.us photographic community help DigiKam?
|
|
In reply to this post by patdavid
I'm not sure. There is nothing pushed here about Hugo port of digiKam.org yet ? Cloning into 'digikam-org'... remote: Counting objects: 3, done. remote: Compressing objects: 100% (2/2), done. remote: Total 3 (delta 0), reused 0 (delta 0) Receiving objects: 100% (3/3), done. Checking connectivity... done. [gilles@localhost digikam-org]$ git up From git.kde.org:websites/digikam-org = [up to date] master -> origin/master Current branch master is up to date. [gilles@localhost digikam-org]$ ls -al total 16 drwxr-xr-x 3 gilles gilles 4096 Mar 25 14:29 ./ drwxrwxrwx 71 gilles gilles 4096 Mar 25 14:29 ../ -rw-r--r-- 1 gilles gilles 1273 Mar 25 14:29 .commit-template drwxr-xr-x 8 gilles gilles 4096 Mar 25 14:30 .git/ [gilles@localhost digikam-org]$ Gilles 2017-03-24 22:37 GMT+01:00 Pat David <[hidden email]>:
|
|
|
Sorry, I didn't mean to give the impression that we had pushed the site code yet. Mica will be around a little later and I'll get with him to start moving things over.
On Sat, Mar 25, 2017 at 8:34 AM Gilles Caulier <[hidden email]> wrote:
-- https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC |
Re: What can the pixls.us photographic community help DigiKam?
|
|
ok. sorry for the noise (-:=))...
Gilles |
Re: What can the pixls.us photographic community help DigiKam?
|
|
In reply to this post by patdavid
ok. sorry for the noise (-:=)).... Gilles 2017-03-25 15:24 GMT+01:00 Pat David <[hidden email]>: Sorry, I didn't mean to give the impression that we had pushed the site code yet. Mica will be around a little later and I'll get with him to start moving things over. |
Re: What can the pixls.us photographic community help DigiKam?
|
|
In reply to this post by Dmitri Popov-2
Hi all,
I seem to have no been granted commit access to the digikam website repo yet, but hopefully that will clear up in the next few days and I'll push what I have so I can share it with you all. Porting all the site's content is getting very close to complete. If you have some free time and want to help, please take a look at the following things: 1. The 20 FAQs still in the drupal site, get the content and add it to the documentation > faq.md file. Even getting the FAQs in markdown format and posting them here to this thread would be a tremendous help. 2. Fix broken links, there are probably a lot of them that still use the drupal syntax. You can run hugo locally and use a link checker to find the broken links 3. Convert posts to markdown. Right now ever page still has HTML in it. It'd be nice if pages were in markdown, where possible. If you edit a page, please convert it to markdown and check to make sure it looks reasonable! 4. Update the screenshots, they're all old! 5. Add the `<!--more--> tag to news items. This controls what hugo shows on summary pages. Right now, nothing uses this tag. You can check the git repo out from KDE's source control using git: git://anongit.kde.org/websites/digikam-org and submit patches here on the list, on this thread please. Or if you have commit access to the project, go for it! You can run hugo's internal server to serve you the local website by first downloading and/or installing hugo (available as a binary for most platforms at http://gohugo.io), cloning the repo, cd into the digikam-org folder, and run "hugo serve" from your command prompt. If you'd like to request commit access to the project, you can do it by registering an account at identities.kde.org and requesting developer access. Again, sorry I haven't pushed yet, but hopefully that will happen tomorrow! Best, Mica On 2017-03-24 02:00, Dmitri Popov wrote: > Hi Mica, > > First of all, thank you for going ahead with the project! I don't have > much to say about the structure and template, but I think that some > content needs to be revised. For example, some entries in the FAQ > section are outdated, while others need editing. I'd like to do that > once the new website is operational, but I'd need an access to the new > website and maybe some basic instructions on how to add and edit > contents. > > Thanks, > Dmitri > > On Fri, Mar 24, 2017 at 8:20 AM, <[hidden email]> wrote: >> I've started hacking on a template here: >> https://github.com/pixlsus/digikam_website_theme. I registered a KDE >> Identity and I'll request developer access this weekend. >> >> Questions about the content: >> 1. About > Screenshots page: Are these up to date? Do we really need >> all of >> them? >> 2. FAQ page: Can we collapse this into one page? >> 3. I'd like to stream line some of the content pages, as there are >> many, >> what are the thoughts on this? >> 4. Is there any color scheme anyone had in mind? If possible, please >> provide >> hex codes. This far I've borrowed a few colors from the KDE website. >> >> Lastly, are there any additions that anyone would like to see to the >> website? >> >> Best, >> Mica >> >> >> On 2017-03-22 00:36, Gilles Caulier wrote: >>> >>> Ben Cooksley email is <[hidden email]> >>> >>> Gilles Caulier >>> >>> 2017-03-22 8:35 GMT+01:00 <[hidden email]>: >>> >>>> Hello all, >>>> >>>> I can get in touch with Ben if someone would like to send me his >>>> contact information. >>>> >>>> A quick recap, so we're all on the same page: >>>> - drupal site being shut down on March 31 >>>> - migration to static site using Hugo (http://gohugo.io [1]) and a >>>> redesign proposed >>>> -- template based on Zurb Foundation 6 >>>> -- current URLs taken into account & can generate redirects >>>> - requires webhosting, which pixls.us [2] can provide, but pixls.us >>>> [2] members would like to use KDE/digikam's current hosting if >>>> possible >>>> -- static site requires only a webserver such as apache and rsync >>>> over SSH access to the webroot for digikam.org [3] >>>> - site maintained in git; authorization determined by hosting >>>> platform, e.g. github, gitlab, >>>> - continuous integration like TraviCI, can be used to build and >>>> deploy the site when a commit is pushed to master >>>> - current admin should back up the drupal database for posterity >>>> - current pages (but not page history) can be migrated >>>> >>>> Pat was kind enough to write a script to scrape all the news >>>> articles from digikam.org [3], which composed the bulk of content to >>>> be migrated, and format the results with the proper metadata for >>>> hugo. I set up the project scaffolding and migrated some of the >>>> non-news pages (there are pages that still need to be migrated). >>>> >>>> You can see the content we've migrated so far here: >>>> https://github.com/pixlsus/digikam_website [4] >>>> >>>> There probably isn't much more content to migrate. I'll follow up >>>> with some questions about the content and migrate the remaining >>>> necessary pages. >>>> >>>> You can run hugo locally to see the progress: >>>> $ wget >>>> >>> >>> https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >>>> >>>> [5] >>>> $ tar -zxvf hugo_0.19_Linux-64bit.tar.gz >>>> $ git clone https://github.com/pixlsus/digikam_website [4] >>>> $ cd digikam_website/themes >>>> $ git clone https://github.com/tummychow/lanyon-hugo [6] >>>> >>>> $ cd .. >>>> $ ./path/to/hugo serve --theme=lanyon-hugo >>>> >>>> I can't say we'll have a 100% finished & beautiful website by March >>>> 31, but I believe we can be pretty close to finished & very >>>> functional by that date. >>>> >>>> Best, >>>> Mica >>>> >>>> On 2017-03-21 23:37, Gilles Caulier wrote: >>>> >>>> Note : when Ben said " I think it's best if they contact us with >>>> the >>>> details they require. I'd rather >>>> not read a long mailing list thread." : the "they" want mean >>>> Pixls.us >>>> team of course.... >>>> >>>> Gilles Caulier >>>> >>>> 2017-03-22 7:36 GMT+01:00 Gilles Caulier <[hidden email]>: >>>> >>>> Hi all, >>>> >>>> This is the response from Ben by private mail : >>>> >>>> // --------------------------------------------------- >>>> >>>> Hi Gilles, >>>> >>>> Given the amount of work which we've put in thus far and the time >>>> constraints Sysadmin is under in getting other things done, I think >>>> it's best if they contact us with the details they require. I'd >>>> rather >>>> not read a long mailing list thread. >>>> >>>> At this stage, i'll be shutting down the Drupal 6 instance on March >>>> 31 >>>> as we need to protect the security of KDE Infrastructure as a first >>>> priority. This migration has effectively been ready to go (theme >>>> aside) since early February, with the only reason for the delay >>>> being >>>> your requirement a theme be customised for Digikam and nobody being >>>> able to do it. >>>> >>>> Regards, >>>> Ben >>>> >>>> // >>>> ------------------------------------------------------------------- >>>> >>>> So it become urgent to switch to a new web site. "Static" proposal >>>> from pixls.us [2] [1] sound like the best solution. >>>> >>>> Comments are welcome. Please be constructive. >>>> >>>> Thanks in advance >>>> >>>> Gilles Caulier >>>> >>>> 2017-03-21 10:49 GMT+01:00 Gilles Caulier >>>> <[hidden email]>: >>>> >>>> The contact to KDE team about current www.digikam.org [7] [2] is >>>> >>>> Ben >>>> >>>> Cooksley <[hidden email]> >>>> >>>> I CC him to contribute to this thread... >>>> >>>> Gilles Caulier >>>> >>>> 2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>: >>>> Pat, >>>> >>>> Thank you for the detailed outline. If there is anything I can help >>>> you with, please do let me know. >>>> >>>> Best, >>>> Dmitri >>>> >>>> On Mon, Mar 20, 2017 at 10:13 PM, Pat David <[hidden email]> >>>> wrote: >>>> The intention here is to provide a new, modern website that is >>>> secure and >>>> maintainable. >>>> >>>> Let me address a couple of possible questions up front: >>>> >>>> 1. The existing site content can be ported over to a new site. >>>> This >>>> includes previous posts in news/blogs and all of the more static >>>> pages as >>>> they exist right now. >>>> >>>> The only thing we may have a problem with would be the comment >>>> system used >>>> by Drupal. In this case, old comments are likely not going to get >>>> brought >>>> over as actual _comments_. We can probably bring them over as >>>> plain content >>>> that gets appended to existing news/blog items. >>>> >>>> 2. I analyzed the existing site quickly, and noticed that as far >>>> as content >>>> pages go, we were looking (roughly) at: >>>> >>>> About >>>> Overview >>>> Features >>>> Awards & Reviews >>>> Related Projects & links >>>> Screenshots >>>> Testimonials >>>> News * >>>> Release Plan >>>> Changelog >>>> Events >>>> Developers Blogs * >>>> Download >>>> digiKam Recipes Book >>>> Documentation >>>> Wiki >>>> FAQ >>>> Support >>>> Donation & Sponsor >>>> Splash-screens >>>> Contribute >>>> Contact >>>> >>>> Items marked with (*) are the most likely candidates for more >>>> frequently >>>> published content. The rest of the pages are probably fairly >>>> consistent and >>>> don't change all that often (every release maybe?). >>>> >>>> 3. Contributing to the site is easy, just write your content in a >>>> plain-text >>>> markdown file. >>>> >>>> I assume that you don't want to let everyone publish material to >>>> your >>>> website? No matter what the system (CMS/Static/Whatever), you >>>> likely want a >>>> check step in the publishing process. In the case of a static >>>> site, it's >>>> handled by commit access to the repo. If someone w/o access wants >>>> to >>>> publish something, send the plain-text file to someone with commit >>>> access. >>>> >>>> At GIMP, we can accept patches, or someone can just email the >>>> plain-text >>>> files (+ assets) and one of us with commit access manages the >>>> rest. >>>> >>>> 4. Comments can be handled the same way we are currently doing it >>>> on >>>> pixls.us [2] [1], that is - an embed at the bottom of a post will >>>> display a threaded >>>> conversation about that topic hosted on https://discuss.pixls.us >>>> [8] >>>> [3]. >>>> >>>> --- >>>> >>>> At the end of the day we want to help, and we know that the dev >>>> team likely >>>> would rather be hacking on Digikam. As such, we're ready and >>>> willing to get >>>> a new site up and running, and to help manage things. >>>> >>>> Just let us know if we _shouldn't_ continue working on the site. >>>> :) >>>> >>>> Also, is there a contact person for the infrastructure your >>>> running the site >>>> on now? I'm assuming a server that the kde folks have somewhere? >>>> >>>> pat >>>> >>>> PS (interesting sidenote): >>>> I scraped the existing site quickly to get this, and it appears to >>>> me that >>>> over the past 5 years the _majority_ of the posts are from two >>>> submitters >>>> (digikam + Dmitri). >>>> A table of posts per person by year, since 2006: >>>> https://paste.gnome.org/pwbvlr6ha [9] [4] >>>> >>>> -- >>>> https://patdavid.net [10] [5] >>>> GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC >>> >>> >>> Links: >>> ------ >>> [1] http://pixls.us [2] >>> [2] http://www.digikam.org [7] >>> [3] https://discuss.pixls.us [8] >>> [4] https://paste.gnome.org/pwbvlr6ha [9] >>> [5] https://patdavid.net [10] >>> >>> >>> >>> Links: >>> ------ >>> [1] http://gohugo.io >>> [2] http://pixls.us >>> [3] http://digikam.org >>> [4] https://github.com/pixlsus/digikam_website >>> [5] >>> >>> https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz >>> [6] https://github.com/tummychow/lanyon-hugo >>> [7] http://www.digikam.org >>> [8] https://discuss.pixls.us >>> [9] https://paste.gnome.org/pwbvlr6ha >>> [10] https://patdavid.net >> >> |
Re: What can the pixls.us photographic community help DigiKam?
|
|
2017-03-27 9:57 GMT+02:00 <[hidden email]>: Hi all, What do you mean by Markdown exactly ? 4. Update the screenshots, they're all old! I will do it step by step. 5. Add the `<!--more--> tag to news items. This controls what hugo shows on summary pages. Right now, nothing uses this tag. I created an entry in Phabricator for that few days ago : Gilles Caulier |
|
|
On Tue, Mar 28, 2017 at 1:04 AM Gilles Caulier <[hidden email]> wrote:
Markdown is a very simple text styling method. The original spec was created by John Gruber: The syntax is very simple and straightforward. Hugo also supports using an extended version of the spec normally referred to "Github flavored Markdown": It just extends a few things (and isn't normally required). The important thing is that any valid HTML is still valid markdown, so you can still use <a href="https://www.digikam.org">these links</a> like normal. --- I also recently scraped and combined all of the FAQ entries into a single page. I'll look with Mica at adding a nice TOC to the top of the page for navigation (perhaps something similar to: https://www.gimp.org/docs/userfaq.html). -- https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC |
Re: What can the pixls.us photographic community help DigiKam?
|
|
2017-03-28 19:05 GMT+02:00 Pat David <[hidden email]>:
|
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |