Search Ideas
1824 ideas match your query.:
‘Articles’ are functionally no different than top-level ideas in a discussion thread.
It might make sense to have the new top-level idea form at the top, in the meantime. Compared to the current design, this would invite the creation of more top-level ideas.
Any progress on this? Scrolling to the bottom to submit new ideas is annoying.
The site isn’t at all big enough for this to matter yet.
Done for the search input as of 765ba05. It makes sense for that input because the user expects to be able to keep typing after submitting the form. For other inputs, the user will expect whatever default their browser implements.
Feature idea: private discussions only the creator and invited people can see. This could be a paid feature; $2 per discussion, say.
Top-level ideas can be structured any way you as author want them to be. (Any idea at any level can, but top-level ideas are presumably where articles could live.) The structure of any particular idea can be different from the structure of the discussion as a whole.
Proposed solution: ideas with pending criticisms could be archived automatically if they haven’t had any activity in the past 30 days, say.
I implemented #2659 and it’s much better now. In addition, there is now automated archiving (#2704) and manual archiving (#2711). Archived ideas live on a separate page, so the main page is faster.
I went ahead and implemented this feature since it was a good suggestion.
You can edit your discussion here.
Now that diffs are formatted, they don’t omit unchanged lines anymore.
Proposed solution: allow people to archive ideas. Maybe only their own.
That could just annoy people and cause them to unsubscribe from emails.
Could do it only for ideas with pending criticisms. If they have pending criticisms, how important can they be? This has the added benefit of creating an incentive for proponents of ideas to address criticisms.
This requires manual action. Could mean a lot of work depending on the discussion.
Proposed solution: ideas could be archived automatically if they haven’t been revised or criticized in 90 days, say.
This problem will surface rarely – users would have to hit cmd + f immediately upon opening the page. For most users, by the time they start typing, the page is already fully loaded. So this seems like a small price to pay in exchange for discussion pages that always render faster.
Now that parts of the page are purposely and visually disabled (see #2694), users may not expect everything to be working 100% during a loading state.
I now purposely prevent interactions with buttons and gutters, and gray them out, until the page is fully loaded. So instead of broken hover effects and interactions, the user gets intentionally disabled elements, and this intentionality is communicated to them.
Once the page is fully loaded, buttons and gutters are enabled and visually restored.
Since the browser’s loading indicator remains visible until then, this behavior shouldn’t violate user expectation.