piranhacms / piranha.modules Goto Github PK

I don't have an immediate need for something like this, just seeing if this is a viable idea for a module. It would be a comments section that would go at the bottom of blog post pages. It would still feature OAuth logins for services like Facebook, Twitter, Github, etc., but could differ from something like Disqus in the following ways:

1. All of its data (comments, users, reactions, etc.) would live in the same database that the rest of Piranha uses instead of relying on an external service.
2. Much lighter weight, offering faster load times over Disqus, which often takes a very long time to load on sites.
3. Simpler admin system that isn't so complicated to use
4. NO ADS!

I don't know if it would be better to build this from scratch or to build a wrapper around an existing solution, but it's an idea.

Need to make this functionality for something I'm working on. Essentially, one package will generally allow embedding a text editor on supported documents, and then a separate component that can hook into SCSS ones and compile them for use in the pages/posts. The end result is a "skin" system for pages!

Have some basic ideas on how I want it to work and I'm planning on starting it but want to see if anyone's attempted this or would want to work on it, or would at least be willing to rubber-duck me.

Am probably gonna start my efforts in a week if something doesn't exist.

Even though Google Analytics or other equal services should be used for collecting usage metrics, a simple native view counter would give some simple analytics. These number would also give the possibility to query the most popular content in the site and use it for rendering the pages and make the content more interactive.

Personally, I find fully working examples the most effective way of understanding concepts and functionality. Fully working but as minimal as possible. There's always a balance between "feature X works like THIS" and a complete example that covers too much, I know. However - I often find myself scratching my head on all the things NOT mentioned in examples.

Promoting this repo and encouraging contribution would greatly enhance the understanding and usability of Piranha - and would put less demand on updating the docs (which I know is lacking in Piranha as well as pretty much every software project on the planet). I don't know how this would be done best but I think this might be a "low hanging fruit" thing to improve Piranha "documentation".

One thing this repo could use is a better overview of what the different modules do. Now we only have a few but if more are added - it would be very useful with some sort of categorization. Perhaps tags for each module, both indicating what parts of Piranha they cover but also what kind of problem they solve. My module, for instance, could have tags like: PIRANHA-MODULE, PIRANHA-HOOKS, IMPROVEMENT-COMMENTS, FEATURE-ANTISPAM, MANAGER-SUPPORT, and perhaps more. I can see contributions to this repo that is not a module too - since the concept of modules is somewhat loosely defined in the Piranha context (without saying that's a good or bad thing).

I won't do a PR for any changes like this but I do believe this repo could be more used and rich in content - with relative little effort from the Piranha team (so they can focus on Piranha itself).