I'm having a bit of trouble understanding your request. Are you saying you want to preload a template into the editing interface and also pass parameters to that template via the URL? If so, there is no practical way to implement that as the edit page has no awareness of templates and their parameters, i.e. it wouldn't know where to plug in the parameter text. Could you explain more specifically what you are wanting to accomplish. Perhaps there is a better way to achieve it.

I believe that you misunderstood me and rereading my own bug report I understand why.

The API allows to add sections/text at the top of the page through the api call 'appendtext' this would be very helpful for some tasks at enwp if we can use that also by using the normal GUI.

This is in contrast similar to the &section=new only at the top of the page, because &section=-1 doesn't work (the first section is filled in the text field) nor is &section=0 always usable since preloaded text doesn't work in both cases

What we need (the TeaHouse and the AFC team) is that we can add sections at the top and or above all content. (best would be both)

Hope that clarifies the situation.

Ah, so you want to be able to post new sections to the top of the page. Why didn't you just say so :)

This bug is related to bug 15494 ("Add new sections to the top of a page on a site-wide basis").

I'm going to mark this as easy. Bug 15494 is about the ability to change the &section=new behavior on a site-wide basis (via a configuration variable). This bug is about the ability to change the &section=new behavior on a per-page basis.

I think a magic word is the most logical implementation for this. Something like REVERSEPOSTORDER or something, maybe? That way it would just do whatever the non-default behavior is. Or you could take a more explicit approach and have ALWAYSTOPPOST and ALWAYSBOTTOMPOST and the implicit value would be whatever the site-wide default is.

*** Bug 15494 has been marked as a duplicate of this bug. ***

Change 209853 had a related patch set uploaded (by Legoktm):
Have action=edit&section=new prepend if ALWAYSTOPPOST is set

https://gerrit.wikimedia.org/r/209853

The only question/concern about this is how is "top" defined for this patch? For AfC drafts, I can see top as defined as section 0; but for the WP:THQ, which is supposed to be top posting, top would be defined as the first section after the header which is section 1 on the page (don't think there are any header sections in templates).

In T33919#1274335, @Technical13 wrote:

The only question/concern about this is how is "top" defined for this patch? For AfC drafts, I can see top as defined as section 0; but for the WP:THQ, which is supposed to be top posting, top would be defined as the first section after the header which is section 1 on the page (don't think there are any header sections in templates).

top is defined as literally the top of the page, before any other content.

Another possible approach might be having a __POSTBELOWHERE__ magic word or similar that could be placed in an arbitrary position on the page.

I'm not sure how I feel about creating new magic words these days.

In T33919#1274939, @MZMcBride wrote:

Another possible approach might be having a __POSTBELOWHERE__ magic word or similar that could be placed in an arbitrary position on the page.

I'm not sure how I feel about creating new magic words these days.

That would certainly resolve the situation I mentioned.

Another silly idea: have a {{#post new sections:1}} magic word that can be used to specify per-page behavior of where new talk page posts should be posted. In this example, new talk page sections would be created in the 1st section (after the 0th) section. {{#post new sections:last}} or {{#post new sections:default}} or {{#post new sections:4}} could also be supported.

As @Rjd0060 pointed out to me in discussion of this feature generally, having individual pages behave differently with regard to post order may result in user confusion.

Change 209853 abandoned by Legoktm:
Have action=edit&section=new prepend if ALWAYSTOPPOST is set

https://gerrit.wikimedia.org/r/209853

Removing good first task; see review in now (abandoned) https://gerrit.wikimedia.org/r/c/mediawiki/core/+/209853/

We also need this to work with the DiscussionTools. For example, in all our forums, messages are posted at the top: https://ru.wikipedia.org/wiki/Википедия:Форум/Предложения. https://www.wikidata.org/wiki/Q10953400#sitelinks-wikipedia. As far as I can see, this mechanic is used in some projects (https://www.wikidata.org/wiki/Q10953400#sitelinks-wikipedia), maybe there are more of them, because they use a different template.

Perhaps @Trizek-WMF can help us with statistics (how many wikis use "new on top" scheme), since the GrowthExperiments-Help panel has implemented the function of adding topics from above.

Add idea for CWS2023: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Notifications,_Watchlists_and_Talk_Pages/Allow_posting_new_sections_to_top_of_Talk_pages

Hi, all. As a long-time user of Extension:PlaceNewSection, I'd look forward to seeing this functionality implemented in core.

Does the currently-proposed implementation handle the case where you'd like to insert new sections at the bottom of the article, but above (for example) "See also" and "References" sections? Or at the top of the article, but below some introductory text, notices, or tables of contents?

I need to do some testing to confirm, but I believe PlaceNewSection supports both of those use cases with its two magic words, __PLACENEWSECTIONABOVE__ and __PLACENEWSECTIONBELOW__.