Thread:SamwiseFilmore/@comment-30645975-20170607023329/@comment-25101690-20170612145913

A nice accomplishment for a markup language would be Markdown compatibility, i.e. if Markdown code would be rendered the same in your markup. I'm not sure if that's even practicable, since Markdown has quite different goals than a wiki markup language.

What makes Mediawiki great is, imo, the transclusion features. It's easy to create templates, to use any page (or parts of it) as template, pass parameters etc. Some other templating engines have a great caching system. Re-rendering pages when their contents didn't change is a waste of server resources and time. But some pages might contain dynamic content that should be re-rendered every time, such as the online status of other users. In these cases it's best to only render the dynamic content and insert it in the static part. That's what top websites do for maximum performance.

UX/HTML experts say we shouldn't use HTML tags like    or    but use for example  and  , because a HTML document should be about semantics, not appearance. For example this helps screenreaders for blind people.

Wikia has a really bad mobile version. Many users prefer the desktop version even on mobile devices. Neither the mobile version nor the desktop version are fully functional on mobile devices. Part of the problem could be that Mediawiki gives too much freedom to the code. Some helpers in the code and a more strict architecture might help the CSS to make the resulting page responsive.