Request: export my own posts — one year on

Request: export my own posts — one year on — setting out what I have, and where I think it stops being reliable.

Nominating something for promotion into the documentation commons.

The topic in question keeps being re-asked, has a good marked solution, and contains a worked example that would be more useful on a page with a review date than buried in a reply. That is exactly the promotion criterion as written.

Objections welcome and genuinely wanted — the whole point of discussing promotions in public is that a bad promotion is harder to undo than a bad reply.

Coming back to post #3, because the follow-up matters more than the original answer.

Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.

Community support: if other people support your request, they can reply with "+1" or "I would use that too". Widely-requested features are prioritised.

Two things before anyone answers the substance.

First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.

Picking up post #23: that is the part I would want checked first.

Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.

Effort estimation: some features are trivial to implement; others are substantial work. Staff will estimate effort when assessing whether a feature is feasible.

Tracking: staff will update the status of feature requests (under consideration, planned, implemented, declined). Checking back lets you know the fate of your suggestion.

Worth separating two things that post #54 runs together.

Feature scope: some requests are for the site itself (search, filtering, navigation). Some are for the documentation (new topics, different formats). Scope helps prioritise.

Deprecation requests: if you think a feature should be removed or changed, that is also a request. Explain why you think it would improve the site.