I've taken a first go at the customizable parts of the very first page users are supposed to read on the site — [the tour page (formerly known as /about)](https://softwarerecs.stackexchange.com/about), based on the [guidelines we've established so far](https://softwarerecs.meta.stackexchange.com/tags/faq).

We can customize two sections: “Ask about…” and “Don't ask about…”. Here's the current content (we [can't edit the title](https://softwarerecs.meta.stackexchange.com/questions/617/allow-moderators-to-customize-the-first-line-of-the-editable-parts-of-about)).

> 
> ### Ask about…
> 
> 
> Good software recommendation requests have two components:
> 
> 
> * A purpose — a task to accomplish, a user story
> * Some objective requirements — a minimum set of features
> 
> 
> Please read our [question quality guidelines](https://softwarerecs.meta.stackexchange.com/questions/336/what-is-required-for-a-question-to-contain-enough-information).
> 
> 
> We request that answers demonstrate how the recommended product meets the requirement and is suitable for the intended purpose. Please read our [answer quality guidelines](https://softwarerecs.meta.stackexchange.com/questions/356/what-is-required-for-an-answer-to-be-high-quality) for more information.
> 
> 
> ### Don't ask about…
> 
> 
> * Requests for lists of software with no defined purpose — our objective is to find the best fit for a task.
> 	+ Questions without concrete requirements — if some potential answer would lack a critical feature, we need to know.
> 
> 
> If you're [asking for alternatives](https://softwarerecs.meta.stackexchange.com/questions/48/how-to-ask-for-an-alternative-to-some-software), be sure to describe the features you're using and why what you have isn't up for the task.
> 
> 
> 

Feedback welcome.