We have several shared resources in our github organization, but we don’t get man commits at all.
You’re totally free to put this in an article on the main website (also a git repo) or I can start a separate repo for it. I’d prefer the former, though.
Maybe it could be under the “awesome” umbrella as well?
I like this idea alot as well, but am not versed in github. Looks like a wiki, kinda…
When you’re using github for editing a guide in markdown you might take a look at Grav CMS. It’s a open-source lightweight (no database) flatfile CMS that uses markdown files for its pages.
There is an git-sync plug-in available that can connect to git and make a website out of git’s markup files.
One example is the Grav CMS documentation at https://learn.getgrav.org/
On top of the page you see a “edit this page” link that opens the corresponding markdown file in git.
Grav just needs PHP, so you can put the files of one instance in a subdirectory of your website and place the documentation there
you can also just submit articles to the pixls.us page 
we do not have a CMS yet, but IIRC @patdavid was playing around with netlify for the RT page, which uses a similar processing as the pixls.us page.
For now we just need markdown files + images at GitHub - pixlsus/website: The PIXLS.US website
Or you add more documentation directly to darktable’s documentation documentation or the website
Hey thanks everybody for the tips on how to make this markdown file a bit more easy to read.
The thing about adding it to DT’s official docs is that somebody need to approve it/publish it/etc… I mean I am trying to use github also for collaboration but it still work in progress for me and I’m not that good with pull requests etc.
Anyway, all of this will come later, first I need to at least clean up this first draft, add a few more tips etc.
And this is the draft I have compiled with the help of @Claes (we were debating about which format to write the tips, i.e. simple bullet points vs tables etc), I will gladly accept any sort of tips and meta-tips (=tip on how to write a tip)
Hey @pphoto thanks for this, now I wonder how is Grav different from pelican () that I use for my blog()?
(*) just realized that also DT’s website is built on Pelican!
After a first short view on pelican it seems that both do have a similar approach. File- and markdown based, both with a template system.
Pelican uses python, Grav uses PHP which makes it compatible with many webhosters.
Pelican seems to be more command-line oriented, while Grav does have own GUIs for editing pages and administration including updates, themes and plugins.
Thanks, @darix. I did now know about these repositories and possibilities for everybody to contribute.
As I see we’ve got the following resources:
As @paperdigits mentioned, all of these resources could need more input. But for darktable-specific tricks or tutorials we would mix this content with other types. DT documentation contains explanations of the program, DT blog release notes and other info, Pixls.us got content for other programs than DT.
So I think that starting a new repo for DT tips and tricks would be the best option. For making usable output like a searchable website or PDF document there seem to be various possibilities.
As mentioned before, Grav CMS is able to do that. Moreover, I did a quick search for open-source Knowledge Base systems which use markdown and found:
https://ourcodeworld.com/articles/read/782/top-5-best-node-js-based-open-source-self-hosted-web-wiki-knowledgebase-applications
Moreover, we could need a repository of example RAW files for that. So everybody who reads a tutorial would be able to follow and reproduce. I suggest keeping the number of files as low as possible (preferably one image for multiple tutorials) and the image’s filesize too for easier handling (shoot the picture with lower resolution)
I’ve also been trying to scrape tips and tricks for many software for a freely licensed photo book that I’ve yet to git push to any end point.
I’d suggest not using a table for this, as the information is not tabular in nature. Perhaps a list, or paragraphs…
I agree. There should be a defined content structure. An example:
TBH: why not help e.g. here on pixls.us to provide more content instead of starting yet another island of knowledge.
well my idea was just to make more manageable/readable instead of scrolling through an endless series of posts. What I did with my initial draft was to keep the links to the actual posts on this discussion thread (when applicable) as to provide more context.
If you want automated before and after images, that is a whole other level of complexity and you’ll likely need some build script. I think the simpler it is, the better.
I am sure you can have your own category with tips&tricks on pixls.us and your own RSS feed for them. and then people can also provide the same for RT or other relevant programs. Maybe we even manage 1 tip a day!
Hey community … 1 tip a day … do you accept the challenge?
The problem is that if the information is good, you get a series of posts anyway, because everyone chips in with their own little variation, thought, or comment.
There are wiki posts here on the forum, where anyone can edit a post. We can certainly do that. Or as @darix suggested, your own subcategory. The problem with all these approaches, and with crowd-sourced content in general, is finding what is good and what is not (and even that is subjective).
Content needs curiation. And that is a lot of work.
oh yeah I forgot about wiki posts… 1 wiki post per tip would also work
Where do I find these wiki posts?