|
And yes, when found weakness in WP/Django, in many cases you will just need to transit to patched version, or recreate (if different major version). As I said, recreate for WP much cheaper than any other you asked. But when found weakness in some part of software, which you used in Flask, this could be big problem, because parts are supported by different persons, some may become just unsupported, or may be supported worse than others, and you will not have one subject to call, unlike case of pure Django. Same problem could happen with WP, because many custom plugins are practically just other separate big system, also not supported by main WP team.
But in many cases, SEO and leads tracker could be from official package. But, from what I seen myself, with WP typically you will end with few sites, each serve part of business, each consisted from 2-4 big chunks, which working good together, so you will depend from limited number of subjects (with Flask, number of parts will be more than 5, because there nearly all separate). With Django, it is possible, to make all in one site, and to not use anything from separate sources, except frontend framework and markup (for example in ideal world could be Django+React+Bootstrap, and nothing else, sure in real will be additionally some SEO addon, leads tracker addon). |