@Ralph I'm interested in improving the documentation too. I've followed this project for years, but didn't manage to drum up support for adding more newbiew-user-targeted up front and center on the web pages, and don't yet understand enough to contribute much to the documentation that's (I guess?) generated from the source code. Possibly related, my own perkeep usage is also very limited.
I plan to create a hand-written javascript configuration if I find time to understand how the config format works. Tthere was also talk about changing config file format from .js(on) to .toml or another nicer option. How the config files can be used is crucial to document, but before that, I agree we need a list of use-cases and some hint on how well-tested and supported various uses are. Maybe we could start a wiki to hash out some ideas and then make a joint PR? As I understood, you'd like to document / list: - use cases - importers - backends It seems Perkeep deserves to be better known and more widely used > amongst programmers, but the website is probably losing a lot of them at > the `top of the funnel'. > Yes. Let's fix this :) -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
