Topic on Talk:Reading/Web/Advanced mobile contributions/Flow

Param _website_ is undiscriminating?

2
Summary by AHollender (WMF)

wrong talk page for this issue

Omotecho (talkcontribs)

Could we remove “website” param from the cite-web template auto-generate feature on mobile visual editor? Maybe it is not working best when the auto-generating cite-web template is picking up “website” param. It picks up both the root part of the url, and as the publisher or the parent directory of the webpage displayed, but for me the choice is not predictable.

In jawp, people find it annoying when I add/did not empty the “website” param, especially when I apply mobile VE and my edits add any root address of the webpage; example a) is accepted as: website= Wikimedia; example b) is not appreciated/requested to omit values if website=www.wikimedia.org.

I support that “website” param is useful when it indicates that the website publisher and the actual child webpage producer/director have meaningful relationship, like a film festival committee as a 3rd-party organizer commissioned by a local government.

May I remind you that I am a strong supporter of mobile visual editor and can’t wait to see auto-generating function fir web citing to Desktop. But at the moment, I don’t have any page to point editors to when they are unhappy with “website” parameters.

Timid resolution would be to request that “website” param will be an option that I will add, but the system does not autofill value. Do you think it will be agreeable for single-byte language wikis?

AHollender (WMF) (talkcontribs)

@Omotecho thanks for raising this issue. This is the talk page specifically for the Advanced Mobile Contributions mode being developed by the Readers Web team. I think it would make more sense for you to start this discussion on the talk page for Visual Editor, or on the Visual Editor Phabricator board (whichever you are more comfortable with). @PPelberg (WMF) is the product manager for Visual Editor and would be a good person to engage with.

I'm going to mark this topic as resolved here. Thanks again for your concern.