Tom Wor

Ha, in a way that's even better as I can look at that code in isolation. Thank you!

The "tel:" link type is not recognized by ParseDown as it's not in the whitelist. Easily fixed, I made a pull request. https://github.com/erusev/parsedown/pull/771

I'd strongly suggest going with PSR-1 & PSR-2. https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md Some important points: PSR-2 - Code MUST use 4 spaces for indenting, not tabs - Opening braces for classes MUST...

It might be related, so I'm posting this here: After browsing the code a bit I noticed a couple of odd design decisions. - $this->utils->ensure_logged_in() should definitely be handled by...

@bojidar-bg I completely get this - I also stay with some older technologies, because I'm more productive in them; and a project maintainer / main dev should always feel comfortable...

btw.: What about using a template engine? (Smarty/Twig) I know all the arguments around it (and been through the holy wars) - but I'm generally in favor of template engines,...

I'd volunteer for integrating the template engine if you like. I'm a bit more in favor of Smarty, because I've used it extensively in the past, it's said to be...

The PHP short tag syntax

As I'm said I'm rather agnostic about it, but I prefer Smarty syntax. Small example: ### Twig ``` {% for color in myColors %} {{ color }} {% endfor %}...

@bojidar-bg Yeah, those % signs make my eyes bleed and I don't like them for readability. As for Smarty Docs: Yes, we are definitely not in cool-town here, but to...