[00:46:25] Will it be parsed anywhere? If it's not parsed on the client wiki, will it be parsed on the repo wiki? (re @vrandecic: The future is wide and open, but the current plan is not to enable parsing on the client wikis -- the architecure for that just ...) [03:18:48] What's the repo wiki? (re @amire80: Will it be parsed anywhere? If it's not parsed on the client wiki, will it be parsed on the repo wiki?) [03:25:03] It’s an attempted clarification, really. Functions can emit wikitext already (because it’s just text), and this is not (and will not be) parsed as wikitext. However, Abstract Wikipedia content can form the basis of an article on a client Wikipedia edition. This, presumably, will be wikitext (maybe just as an option, so that it can be refined and extended in the client [03:25:03] wiki) a [03:25:04] nd this wikitext can contain Wikifunctions calls (because they are just text) but these will not be invoked until the wikitext is parsed (when the now-concrete Wikipedia content is required). Whether this contradicts @vrandecic, I cannot say. (re @Toby: I may be misunderstanding, but you seem to be saying that the unparsed wikitext should be generated by WF then parsed at [03:25:05] the poi [03:25:06] ...) [03:45:50] "this wikitext can contain Wikifunctions calls (because they are just text) but these will not be invoked until the wikitext is parsed" To be clear about my naiive hope... I hope that there will be two steps to the parsing. First, the function calls will be invoked, which may return wikitext markup as well as text, and will then sort of be transcluded into the main body [03:45:50] of the [03:45:51] other text. Then, the overall result of that will be parsed to give the HTML that displays to the reader. (re @Al: It’s an attempted clarification, really. Functions can emit wikitext already (because it’s just text), and this is not (and will...) [03:49:05] Whereas T368005 suggests that the current plan is that WF will do the conversion into html snippets to include in the final page. [04:10:45] Yes, I’ve not given any thought to templates. They may provide an opportunity to deliver two distinct parses, each of which may evaluate a Wikifunctions call. But they may not. I don’t think it would “just happen”, though. (re @Toby: "this wikitext can contain Wikifunctions calls (because they are just text) but these will not be invoked until the wikitext is ...) [10:55:35] wikifunctions dot org (re @Toby: What's the repo wiki?) [13:34:34] Headsup: I just recreated a change in the datamodel which broke Wikifunctions a few weeks ago: https://www.wikifunctions.org/wiki/Z40?uselang=en&diff=prev&oldid=133208 [13:34:58] If you notice weird behavior on Wikifunctions, please let us know, although we tested it extensively so it does not repeat [15:12:25] also gentle reminder that we are collecting feedback about the "About" widget at the Project chat, there are some questions that we asked and we would like to hear your opinion about it! [15:12:26] More info: https://www.wikifunctions.org/wiki/Wikifunctions:Project_chat#Feedback_on_the_%22About%22_widget_on_Wikifunctions [17:45:16] I asked back then, and I think I didn't get a response: Is the feedback required about the currently deployed widget, or is there an upcoming change? (re @Sannita: also gentle reminder that we are collecting feedback about the "About" widget at the Project chat, there are some questions that...) [18:12:00] Sorry, it seems I lost your question. The feedback is about the currently deployed widget (re @amire80: I asked back then, and I think I didn't get a response: Is the feedback required about the currently deployed widget, or is ther...)