The tour page describes EOSIO SE as follows:
EOS.IO Stack Exchange is a question and answer site for users and developers of distributed applications built on top of the blockchain operating system, EOS.IO.
Above, it seems that "distributed applications" (dApps) are central to the purpose of the site, but many questions include protocol-level questions that may relate to the EOSIO code independent of a dApp.
For instance, questions about how to vote is not really dependent on dApps. Similarly, sending tokens between two users, implementing native private transactions, running a BP node, block validation algorithm, nodeos plugins, DPoS/BFT questions, and many others are not dApp-centric questions.
Granted, depending on one's definition of a dApp, someone may argue that a single contract such as eosio.system is a dApp, making most of EOSIO functionality an interaction among dApps. However, it may be the case that this would raise confusion as it does not appear to be a universally agreed upon definition, and even this extended interpretation would not cover questions such as e.g. DPoS algorithm or plugins.
Thus, I was wondering if it'd be possible for the EOSIO SE description to use a more general description. For instance, something along these lines:
EOS.IO Stack Exchange is a question and answer site for users of EOSIO, a performance-based blockchain that provides an operating system for building large-scale distributed applications.
The definition being from eos.io/introduction:
We propose EOSIO, a performance-based and self-governing blockchain that provides an operating system for building large-scale consumer-facing distributed applications.
