Abstract Wikipedia abstractwiki https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page MediaWiki 1.47.0-wmf.1 first-letter Media Special Talk User User talk Abstract Wikipedia Abstract Wikipedia talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk TimedText TimedText talk Module Module talk Translations Translations talk 4 6 7550 7537 2026-05-11T14:32:29Z Dv103 1247 /* Proposals on the architecture of Abstract Content rendering */ new section 7550 wikitext text/x-wiki {{Shortcut|[[Project:PC]]|[[Project:VP]]}} __NEWSECTIONLINK__ [[Category:Abstract Wikipedia administration|Project Chat]] This is the Abstract Wikipedia Project chat. This is where discussions on the project happen. Add your discussion below this line. More technical issues should go to [[Abstract Wikipedia:Report a technical problem]]. For older conversations, see the archives ([[Abstract Wikipedia:Project chat/Archive 1|1]]). == Put this on ice == How are non-English speakers (who this project is specifically for) meant to develop this wiki's practices and policies if a) all project pages are only available in English, and discussion is largely done in English, and b) there's no attempt to get non-en.wiki communities onboard. At present this looks like it's just going to produce Anglocentric/Eurocentric content, which belies the whole point of having a wiki in one's native language. Yes it's early days and everyone is experimenting and bug-fixing, but the project has already been released to community control, with a predominantly English-speaking/European community. This needs to be put on ice until it can be launched properly with multilingual support and invitations to all wikis, particularly smaller ones. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 11:44, 28 March 2026 (UTC) :Just because it's not perfect doesn't mean it needs to be shut down. These are all gradual processes. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:58, 28 March 2026 (UTC) ::There’s being "not perfect" where things can be improved at a later date, and then there's having antithetical foundations. Also see [https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(WMF)#c-Warudo-20260327114000-Warudo-20260327113600] re functions. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 16:15, 28 March 2026 (UTC) :::You haven't named a single thing that can't be improved at a later date. We're hoping to be able to translate project pages. Non-enwiki communities can be gotten on board later. Function generation already works multilingually in many cases, and those where it does not can be improved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:57, 28 March 2026 (UTC) ::::When the practices and policies will have already been developed, and informal positions of authority already filled. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 17:04, 28 March 2026 (UTC) :::::@[[User:Kowal2701|Kowal2701]] Thank you for your concerns. We are already aiming at less-served communities through specific calls to action to create more language functions and abstract content in their language. Just give the time to actually see these changes happen. Cheers, [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 18:55, 28 March 2026 (UTC) ::::::Hi Sannita, I'm just wondering how are AW project pages planned to be translated in the future? Is there going to be use of some kind of automated tool such as DeepL or Google Translate, or will it be a custom-designed system? [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 20:39, 28 March 2026 (UTC) :::::::@[[User:EatingCarBatteries|EatingCarBatteries]] We will enable the Translate extension soon, so everyone will be able to translate project pages into their own languages. Sorry for keeping you waiting on this. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:41, 29 March 2026 (UTC) :@[[User:Kowal2701|Kowal2701]]: thank you for your concern and suggestion. When this Beta started, we have immediately [[:f:Wikifunctions:Status updates/2026-03-19|mentioned that there might be the possibility of restarting the project]]. So that might indeed happen. :But so far, this early start of the not fully polished project allows us to learn so incredibly much. In the last few days we have learned so much more than we would have been able without the launch in months! And it helps us to focus on where to put our limited resources, so that we can make the overall project better quicker than would have been possible otherwise. From that perspective, this has been quite a success. :I am trying to understand your suggestion: what do you think would need to be in place before a possible relaunch? Which requirements would need to be met? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 13:53, 29 March 2026 (UTC) ::Thank you, I wasn't aware of that. Some uninformed thoughts below. ::Re communication: ideally people would communicate using functions, and there'd be some kind of visual editor where people type in their native language and it gets translated into functions, but I realise that's a pipe dream. Something that allows people who don't have a mutual language to communicate is imo necessary, maybe there could be a tool that machine translates comments. Machine translation ''sucks'', but so long as people get the gist of what is being said, that'd be better than nothing. I dread to think what disputes would be like though. ::Re invitations, idk what has already been done, but I would've thought now would the time to get some people from smaller wikis editing and experimenting, just an invitation on a wiki's main noticeboard would probably do the trick (is there a [[meta:MassMessage]] service for updates re Abstract wiki that could be recommended?). Then a central or watchlist notice for the actual launch, hopefully by which time there'd already be a small group of editors able to assist the influx of newbies. An intuitive tutorial is also necessary, as well as an intuitive version of [[f:Wikifunctions:Catalogue]]. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 18:14, 29 March 2026 (UTC) :::What do you think about boilerplate templates. So writing a sentence and then marking the parts of the sentence what can be derived from Wikidataitems or the lexeme linked to it. This seems to me like an realistic approach for making it easier to contribute. I am happy you wrote about the predominantly English-speaking/European community involved in this project. It seems like it is different to contribute so far and I had the expectation people from small language versions come on their own and contribute also if they dont speak English. So far it seems to be not the case and I hope it will be easier to contribute. I think for the beginning the goal of Abstract Wikipedia should be generating sentences based on data. So supporting small language versions should be not the goal of the first phase as it seems to take some time and improvements of the structures to make it easier to contribute. Sharing the work and offering people help with creating an function for an specific sentence can be a important way of getting more content in Abstract Wikipedia. Maybe it is unrealistic to find a huge number of people who are interested in writing functions who generate text. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:58, 29 March 2026 (UTC) :::[[Abstract Wikipedia:Useful functions for article composition]] is already available, as is [[Help:How to create an article]], but they are not perfect. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:05, 29 March 2026 (UTC) :Wikidata has a project chat in many languages. We can do that in the future. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:28, 16 April 2026 (UTC) ::Anyone can write on this page in any language. Personally, I’d prefer to see the original and get it translated into English rather than trying to make sense of a poor machine translation without even knowing which language the original was in. For the same reason, I would generally reply in English. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:18, 16 April 2026 (UTC) == Gendered languages == I've created [[Q79097672]], an article for a woman singer. In gendered languages however, it defaults to using masculine words. An example: in Portuguese, it reads "Arlo Parks é um cantor", when it should be "Arlo Parks é uma cantora". Is there any fix to this? [[User:Skyshifter|Skyshifter]] ([[User talk:Skyshifter|talk]]) 23:49, 28 March 2026 (UTC) :Yes. But each language is handled separately. I think Italian is doing it. German was started but got stuck… it should be working here soon. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 00:48, 29 March 2026 (UTC) ::Italian is not doing it. It is just a happy coincidence that for some reason "cantante" is always treated as feminine (I have to investigate why). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:59, 7 April 2026 (UTC) == Why don't we just structure this with wikitemplates? == I feel like the project could be done a lot better by using templates kind of like how wikipedia does them. Just the entire thing is templates that can be rendered in many languages. So like [[Q106289265]] would have the content <nowiki>{{Z26039|Q7257}}</nowiki> and could even have some aliasing done across languages so it could be <nowiki>{{subject is|Q7257}}</nowiki>. Code would be editable with a regular visual editor or code editor. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:34, 29 March 2026 (UTC) :This is available in pages when Parsoid rendering is enabled. We don't use this becuase it doesn't make sense for constructing and editing massive articles. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:37, 29 March 2026 (UTC) ::How do you do parsoid rendering? And why wouldn't it make sense? With aliases and everything could work great. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:12, 29 March 2026 (UTC) :::I believe it is enabled by default. If you do have it on: {{#function:Z10000|you'll s|ee this}} [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:54, 30 March 2026 (UTC) :you may be interested in reading this old [[m:Abstract_Wikipedia/Google.org_Fellows_evaluation|Google report]]. [[User:BrokenSegue|BrokenSegue]] ([[User talk:BrokenSegue|talk]]) 14:32, 9 May 2026 (UTC) == Automatically querying wikidata == Is it possible in the future for this project to have things that automatically query wikidata? Like an infobox that gives people's spouses, or a function that queries a specific property on wikidata [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:10, 29 March 2026 (UTC) :Yes, that is the long term goal. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:37, 29 March 2026 (UTC) ::What’s “long term” about it? We already have functions that query specific properties on Wikidata, [[f:Z32431]] being a simple example. A list of spouses seems like a fairly simple function too, although there might be performance issues if there are a lot of spouses. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:01, 31 March 2026 (UTC) :I had exactly this question. One of the example here is [[Q1033]] where I read "Nigeria is the most populous country in Africa.". The problem is that this concept is hard-coded. What if its population will decrease and it will become the second-most populous country? [[User:Wiso|Wiso]] ([[User talk:Wiso|talk]]) 08:21, 20 April 2026 (UTC) == Searching for other namespaces in the search bar == Something that has always irked me with Wikidata, Wikifunctions, and now Abstract Wiki is that there are no search suggestions when you are searching in other namespaces in the search bar. For example, if I were to type "Abstract Wikipedia:", nothing shows up. Whereas on enwiki, you can do this just fine. Is this because these sites are using a more "modified" version of MediaWiki? [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 04:38, 30 March 2026 (UTC) :I also find this very annoying. I'm not sure if there's anything that can be done about it or if it is a result of technical limitations ({{ping|Jdforrester (WMF)}}?). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:41, 30 March 2026 (UTC) ::@[[User:EatingCarBatteries|EatingCarBatteries]], @[[User:Feeglgeef|Feeglgeef]]: The search interface indeed is designed to only search the Wikidata concepts that would take up the main namespace. This is conceptually the same as the search on Wikidata.org. We'd welcome Phabricator tasks for ideas on how to additionally provide wikitext community page search, though implementing that might not be a priority. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 12:11, 30 March 2026 (UTC) :::Hint: don’t use the Search bar… :::When it is empty, click the adjacent Search button. This takes you to the Search page. :::Type the namespace with final colon. You are prompted with available pages and the prompt is refined as you type. :::Click a page title in the suggestions or click Search for a full search in the entered namespace. :::A search with just a namespace will return no results. A search with a partial identifier will work only [[Special:Search/Talk:Q1*|with an appended asterisk]] (delete the asterisk to see page suggestions). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:11, 30 March 2026 (UTC) == List articles == I am interested in creating list articles ([[:de:Liste_der_Naturdenkmale_im_Bezirk_Mitte|like this one]]). But I have no idea what it needs and how to start. [[User:GPSLeo|GPSLeo]] ([[User talk:GPSLeo|talk]]) 19:58, 30 March 2026 (UTC) :An example I've created that you can copy and adapt is [[Q11750]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:27, 3 April 2026 (UTC) == Logo == {{Tracked|T424781}} In vector2009 and monobook, the logo shows as the standard enwiki logo. Which is confusing as this is technically a whole other sisterproject. I suggest [[:File:Wikipedia-logo-blank.svg|this]] be used as a temporary logo for these skins. [[User:Kinopiko|Kinopiko]] ([[User talk:Kinopiko|talk]]) 06:00, 31 March 2026 (UTC) :There's also the scalable favicon, [[commons:File:Abstract-Wikipedia-favicon.svg|Abstract-Wikipedia-favicon.svg]] [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 01:54, 3 April 2026 (UTC) :This still appears to be as of yet unfixed. I understand this wiki is still very early in its lifespan so I'm not particularly miffed about it, it looking identical due to the logo is rather confusing at first but with separation with tab groups in my browser it becomes manageable. I am personally excited to see what logo(s) will be devised for this project; seeing the same thing happen for the other sister projects has been very fun to watch in the past. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:49, 20 April 2026 (UTC) == Extra spaces between sentences == There should be no spaces between two sentences of Chinese and Japanese. —[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 12:38, 2 April 2026 (UTC) :I'm not sure how we plan to handle this. I'll bring it up on the Telegram/IRC. This applies to Korean too, yes? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:28, 3 April 2026 (UTC) {{tracked|T}} :Please link to the corresponding Phabricator ticket when it’s raised. (Or I will, when I raise it). I think the technical issue is that the space is inserted between function calls. There may be two, but HTML reduces their appearance to one, which is one too many for certain languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:58, 3 April 2026 (UTC) ::No, your sentences should not be individual fragments. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:40, 11 April 2026 (UTC) == community curation of abstract articles of the week/month/etc. == [[wikifunctions:wikifunctions talk:status updates/2026-03-26#Move Status Updates to Abstract Wikipedia?|this thread]] at WF mentions that WMF staff are refraining from content decisions at Abstract Wikipedia; so I thought that it might be a good idea to figure out if and how there will be editathons here focussed on a selection of articles. — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 20:38, 2 April 2026 (UTC) : I would support this. — [[user:Feeglgeef|Feeglgeef]] ([[user talk:Feeglgeef|talk]]) 01:29, 3 April 2026 (UTC) : now I notice [[abstract:featured article]] in the same category as the project chat, so there's a location for a related concept already! (coming at it the other direction: recognizing already good articles versus barnraising that quality) — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 01:48, 3 April 2026 (UTC) ::I think it will be quite a while before we can support a “good” article, let a “featured” one. At this stage, I’d settle for “technically interesting”, to include “of archaeological interest” (like the first use of a particular function or function-call pattern). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 3 April 2026 (UTC) :::one goal could be to make stubs and grow them for the basic concepts underlying Abstract Wikipedia, in an attempt to self-document. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 02:45, 7 April 2026 (UTC) == JSON format == The JSON format for Wikifunctions is described at [[:f:Wikifunctions:Function model]]. Is there such a documentation page for Abstract Wikipedia? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:19, 2 April 2026 (UTC) :I imagine that it would be identical? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 11 April 2026 (UTC) ::No, they aren't. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 02:50, 11 April 2026 (UTC) :::Oh, I see, you're talking about the underlying text format? That isn't and (from what I've gathered, though {{ping|Jdforrester (WMF)}} didn't respond last time I pinged him) will never be editable by users. The function model where the calls are actually made is identical to Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:36, 11 April 2026 (UTC) ::::I'm not asking whether it's editable. I'm asking whether there is a page that documents what it is. ::::The JSON of the function calls is perhaps the same as Wikifunctions compositions, but there are also other things there, which are not the same as Wikifunctions. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 22:40, 11 April 2026 (UTC) :::::I'm saying that I'm not sure why you'd ''need'' or ''want'' to understand it if you can't edit it and it doesn't impact the user experience in any way. Is there a specific problem that you are running into? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:28, 12 April 2026 (UTC) ::::::I'm a very curious person. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 01:19, 12 April 2026 (UTC) :This is an example JSON of an Abstract Wikipedia article, with only the [[f:Z801|Echo function]], if you're curious: { "qid": "Q27318", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z801" } ] } } }. :The base has two key value pairs, "qid" and "sections". "sections" currently only contains one key-value pair as of now, [[d:Q8776414]], aka lead section. "fragments" is where the Wikifunctions compositions are stored. I have no idea what "index" is. [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 02:35, 12 April 2026 (UTC) ::Yes, that's what I see. I can make educated guesses about those things, but if possible, I'd prefer to read an official reference documentation page. The one about Wikifunctions is fairly good. The one about Abstracts Wikipedia doesn't seem to exist. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:25, 12 April 2026 (UTC) :::I think the reason there's no documentation is that it's merely a curiosity, whereas the mainspace of the wiki is barely functional right now. Perhaps we'll get one later, or whenever/if ever we get the ability to edit it? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 12 April 2026 (UTC) ::Just to clarify (?), index is 0! I believe it can only be 0 at present, at least through the user interface, and I imagine [[:phab:T411699|this ticket]] is to allow a non-zero index to be set and modified (so long as it is positive and, in all likelihood, sequential). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:00, 12 April 2026 (UTC) :Not yet. I think such a page on Abstract Wikipedia would be for the community to create and maintain. I don’t know how [[:phab:maniphest/graph/411686|these things]] are decided upon, but I don’t see a task that would cover technical documentation of any kind. :The development team will no doubt respond with enthusiasm to any questions from the community on matters of technical detail, but I’d be inclined to let such interactions be led by the needs of on-wiki documentation, rather than a proliferation of Phabricator tasks and Project-chat topics. :Shall we ask once on [[Abstract Wikipedia talk:Frequently Asked Questions]] and see which questions should count among the frequently-asked? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:37, 12 April 2026 (UTC) ::@[[User:GrounderUK|GrounderUK]], this is quite definitely something that the extension developers are supposed to create and maintain. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 20:32, 12 April 2026 (UTC) :::Not as content on this wiki, was my point. Here, I suggest, we should reference any relevant technical documentation from whichever pages we, as a community, choose to create for such a purpose. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:06, 12 April 2026 (UTC) ::::I don't care very much where it is. I'd just like to read it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 23:25, 12 April 2026 (UTC) :@[[User:Amire80|Amire80]]: The Wikifunctions function model is documented (alongside its two JSON forms) because we anticipate people would (and should) build tools using it directly. Conversely, the vague expectation ("plan" would be too strong at this point) for Abstract Wikipedia, on the other hand, is that we'll provide APIs to interact with the content, but its serialisation will change over time as features are added to better support the Abstract Wikipedia community's wishes. :For a concrete example (''not a commitment!'') of how the serialisation might change, whilst the system kept working as before, we might in the future add a top-level concept for an abstract article's infobox, which would be shown, edited, and stored apart from the rest of the article's sections, and used differently downstream. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:27, 12 April 2026 (UTC) == Bot request == {{Tracked|T421151}} Can someone smarter than me please create a bot that connects local items to Wikidata equivalents? Right now, we are growing and there are [[Special:UnconnectedPages|hundreds of unconnected pages]] here that are just 1:1 main namespace entries that have identical names at [[:d:]]. I have connected several of these, but this seems like a very inefficient and silly thing to do manually. Can someone help here by making a bot that checks [[Special:UnconnectedPages]] regularly or even [[Special:NewPages]] and connects pages? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 06:17, 3 April 2026 (UTC) :This doesn't sound like something that should be a bot, but like something more automatic and built-in. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:27, 3 April 2026 (UTC) ::@[[User:Amire80|Amire80]] and [[User:Koavf|Koavf]]: Would a bot be a good idea in the interim period before that can be added to the software? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 14:31, 3 April 2026 (UTC) :::Yes, please. Granted, Amir, doing it automatically would be nice, but that feature doesn't exist. Until then, a bot would be very helpful and seems like it would be very difficult to cause problems. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 14:57, 3 April 2026 (UTC) ::::@[[User:Amire80|Amire80]] and [[User:Koavf|Koavf]]: I've written some code for this purpose [[gitlab:toolforge-repos/jjpmaster-bot-wd-t1|here]]. <code>Retrospective.py</code> is meant to be run once, and would connect all existing pages (once the trial run is over). <code>Prospective.py</code> would run once daily and connect any pages that have been created since the previous day. That is, until the Phabricator ticket is resolved, obviously. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 21:42, 3 April 2026 (UTC) :::::Boss. I'm so glad that you're smarter than me. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 03:25, 4 April 2026 (UTC) :::::{{ping|JJPMaster}} You might want to use <syntaxhighlight lang="python" inline>{ 'action': 'query', 'list': 'querypage', 'qppage': 'UnconnectedPages' }</syntaxhighlight> instead. That way, you won't have to maintain two scripts. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:58, 4 April 2026 (UTC) ::::::@[[User:NguoiDungKhongDinhDanh|NguoiDungKhongDinhDanh]]: This is [[gitlab:toolforge-repos/jjpmaster-bot-wd-t1/-/commit/415688aa6f9e1dcbafa21a8b3249899c07f298e9|done]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 05:01, 4 April 2026 (UTC) :::::::{{ping|JJPMaster}} One more problem: You seem to be linking non-mainspace pages as well. Don't forget to check <syntaxhighlight lang="python" inline>page['ns']</syntaxhighlight>. Also, why <syntaxhighlight lang="python" inline>if(i > 2): break</syntaxhighlight>? [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 05:27, 4 April 2026 (UTC) ::::::::@[[User:NguoiDungKhongDinhDanh|NguoiDungKhongDinhDanh]]: The <code>if not qid.startswith("Q")</code> bit was supposed to address the namespace problem. The break statement is for the trial of the bot. The integer in the if statement will change once the request is made. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 17:04, 4 April 2026 (UTC) :::::::::{{ping|JJPMaster}} [[Special:UnconnectedPages]] results are ordered by namespace, so checking for <syntaxhighlight lang="python" inline>page['ns']</syntaxhighlight> will also help prevent unnecessary iterations. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 19:54, 4 April 2026 (UTC) :::@[[User:Amire80|Amire80]], [[User:Koavf|Koavf]], and [[User:NguoiDungKhongDinhDanh|NguoiDungKhongDinhDanh]]: Is a Wikidata BRFA in order at this time? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 05:03, 4 April 2026 (UTC) ::::{{ping|JJPMaster}} Go ahead, please. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 05:25, 4 April 2026 (UTC) :::::See [[d:Wikidata:Requests for permissions/Bot/JJPMaster (bot)]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 18:00, 4 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #242 is out: Request for Discussion: Syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce a proposal for Natural Language Generation, we introduce a page for function suggestions from Abstract Wikipedia, we inform you that there will be a presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1776101400 April 13, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:37, 3 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Way to specify population == Hi! I was wondering if there was a function to specify the population of a place, possibly resembling the following: :N X live in Y. N would be the population size, X would be what comprises the population (e.g., humans, frogs, etc.), and Y would be the location. [[User:Babelball|Babelball]] ([[User talk:Babelball|talk]]) 15:43, 3 April 2026 (UTC) :I don't believe we do. Thinking about it now, we should probably have a page where users can request linguistic functions in a more viable format than [[f:WF:Suggest a function]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 11 April 2026 (UTC) == The problem of when "X is a Y" and Y is a phrase == Consider [[Q486972]], whose second sentence is supposed to be "A human settlement is a populated place," generated using the "Article-ful instantiating fragment" function. However, it fails, because the implementation [[f:Z23414|Z23414]] inherently checks for a lexeme linked to the superclass ("[[D:Q123964505|populated place]]"). However, since "populated place" is a phrase whose meaning is reducible to the sum of its parts, there is no lexeme for it. Therefore, it's virtually impossible to say "An X is a Y" where Y is a non-idiomatic phrase. Additionally, languages with grammatical gender are rendered particularly problematic. Consider [[Q6636]]. The first sentence of this article renders perfectly fine in English: "Homosexuality is a sexual orientation." However, it does not render at all in Spanish. That's because that language's NLG functions use lexicographic data to determine the gender of the phrase "sexual orientation." As there are no such data available for that phrase, it errors out. I did think about using [[f:Z29743|Z29743]] (description of class with adjective and superclass) instead, but that didn't work, since there's no item linked to the adjective "sexual"! Any ideas for how to avoid this? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 00:21, 4 April 2026 (UTC) :We'd the co-operation of Wikidata contributors here, I think. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:37, 11 April 2026 (UTC) == I made a desktop app that helps with editing == [[file:Abstract Wikipedia Editor v4.1.0.png|thumb|alt=screenshot|now there's a screenshot available]] I made a desktop app that helps with creating and editing Abstract Wikipedia pages. It pulls data from wikidata to form templates that it makes into wikitext, and it can round-trip articles into and from the wikitext. Here it is [[User:Immanuelle/Abstract Wikipedia Editor]]. I hope that it helps with editing. — [[user:Immanuelle|Immanuelle]] ([[user talk:Immanuelle|talk]]) 00:51, 6 April 2026 (UTC) : I've created [[Abstract Wikipedia:Tools]] for tracking these things. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:44, 7 April 2026 (UTC) : @[[User:Immanuelle|Immanuelle]] But the main namespace is not for wikitext. Are you publishing this content there anyway? <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 15:05, 7 April 2026 (UTC) :: It's not actual wikitext. It's a custom template syntax that's kind of like wikitext, which gets converted into abstract content when you press "Push to Abstract Wikipedia." [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 16:57, 7 April 2026 (UTC) ::: @[[User:Ainali|Ainali]]@[[User:JJPMaster|JJPMaster]] if you have syntax suggestions I am interested. I was in a rush with implementing this, and I want to in the future implement aliases for wikifunctions and possibly items, so that you can type things out yourself. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:53, 7 April 2026 (UTC) ::: Ah, I see. IT was just the announcement that was ambiguous then. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 20:03, 7 April 2026 (UTC) : FYI anything made by a clanker AI robot is not "made by you." Thank you for your attention to this matter. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:18, 7 April 2026 (UTC) :: Who, then? [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:16, 7 April 2026 (UTC) ::: The clanker AI robot. [[User:Babelball|Babelball]] ([[User talk:Babelball|talk]]) 16:42, 8 April 2026 (UTC) :::: I edited the Wikidata page for the tool to mention Claude. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:35, 8 April 2026 (UTC) ::::: FYI that LLM-generated code is not eligible for copyright, and therefore the MIT license by extension. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:59, 9 April 2026 (UTC) :::::: I think the statements that Wikidata could make are limited by what references can be found. [https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository This help page] makes it sound as if there are limited options for expressing a repo's licensing situation, so I am not surprised that MIT should be the blanket release, even if strictly speaking some of the code contained within is ineligible for copyright, or infringes on an existing copyright (which would need to be demonstrated). But I suppose [https://cpomagazine.com/cyber-security/taking-stock-of-the-anthropic-source-code-leak-ai-agent-compromise-signals-security-issues-claude-copies-ahead-of-massive-ipo turnabout] is fair play? — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 19:53, 9 April 2026 (UTC) ::::::: @[[User:Arlo Barnes|Arlo Barnes]] I like the idea of the wikidata content being restricted based on sources provided. I will try to implement something like this in the next release. Any ideas of which particular statements are useful and should be imported more readily? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:28, 9 April 2026 (UTC) :::::::: I meant in [[d:Q138963952|the Wikidata item]] ''for'' AWE, but in general I think our articles should incorporate references early on, since even abstract content needs justification. [[d:help:sources#Language-independent general principles|This help page]] may be handy; '[[d:property:P3680|statement supported by]]' could be useful for linking to biographical articles in the manner "According to [source], [claim]" (obviously adjusted to the relevant language structures in each language for saying such things). — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 20:42, 9 April 2026 (UTC) :::::::::@[[User:Arlo Barnes|Arlo Barnes]] oh that makes sense. But as for the wikidata sources, actually providing the sources is something that is trivially easy as far as accessing wikidata is concerned, but I am not sure how to give sources for claims in wikilambdas. Do you know how? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:44, 9 April 2026 (UTC) ::::::::::I don't. Currently the distinction between content and format is unclear to me. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:48, 9 April 2026 (UTC) :::::::::::@[[User:Arlo Barnes|Arlo Barnes]] what do you mean by content vs format? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 21:52, 9 April 2026 (UTC) ::::::::::::In the most 'abstract' sense, an article would have as irreducible parts semantic content only (from Wikidata), with syntax handled by the group of functions responsible for getting things looking right in a given target language. In practice, the overall structuring of the article largely defines or limits the syntactic structures of language produced. This is sensible for an encyclopedia which has a fairly conventional or constrained sort of prose. Of course, a web encyclopedia needs more than prose. Hence the functions for making links and formatting text (right now directly to HTML, bypassing wikitext). Although this is a MediaWiki installation, no article has had media content added to it yet, since the formatting functions that would enable that aren't in place. So I would say that content and formatting are entangled, currently. A reference could be considered either: the text that provides the sourcing of a statement, or the formatting that enables this semantic content to read as a reference, perhaps inline or as a footnote, end note, or marginal note. [[f:WF:type proposals#Representing abstract content]] has a couple RfCs about this. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 01:45, 10 April 2026 (UTC) :::::::::::::Yeah I am very confused about what the intention of Abstract Wikipedia is and how much it lines up with the reality. I had thought that the articles would be mostly directly generated from wikidata. :::::::::::::Only particular direction I see clearly is that I think we need articles on all of these pages [[d:Wikidata:List of articles that Abstract Wikipedia should have]] since they will likely bring a lot of traffic to the site and since they have a lot of information, people will have a lot of reason to come to this site and come up with new ways of expressing things on the pages. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:06, 10 April 2026 (UTC) ::::::::::::::I am however really liking section headers like the one here [[Q12539]] and I am going to include them in the next release [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:13, 10 April 2026 (UTC) :::::::::::::::Yes I think that adding sections to articles might be really the first part of the journey towards actually having somewhat readable articles. Although a lot of this is dependent on the article text actually rendering at all [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:21, 10 April 2026 (UTC) ::::::::::::::::Yeah I think I am getting the hang of things. Adding sections and paragraph breaks to the new versions. Denoted by ::::::::::::::::<nowiki>{{p}}</nowiki> ::::::::::::::::for a paragraph break ::::::::::::::::and ::::::::::::::::==QID== ::::::::::::::::for a subheading ::::::::::::::::All content is now generated within paragraphs, and the <nowiki>{{p}}</nowiki> splits the paragraphs up. Feeglgeef mentioned that the paragraphs are a significant accessibility feature, and the paragraphs are also easier to insert with the methods of the app. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:36, 10 April 2026 (UTC) :::::::::::::::::I am also implementing "it" to avoid repeating the name of the article constantly, and I am implementing citation preservation on certain things.Meanwhile also trying to fix the accessibility issue that was criticized. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 05:25, 10 April 2026 (UTC) ::::::::::::::::::New release is out [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 07:42, 10 April 2026 (UTC) ::::::::::::::::::I would suggest not to use [[d:Q6091500]] at the moment. In some languages, there might be multiple words for different uses of "it". If you are editing with only the English logic, it won't help build a multilingual wiki. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 17:42, 11 April 2026 (UTC) :::::::::::::::::::@[[User:Sun8908|Sun8908]] fair. I had thought it would be dropped in pro-drop languages but I do not think that was a reasonable assumption. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:47, 11 April 2026 (UTC) ::::::::::::::::::::I asked at the Monday meeting. Not sure if anything is being done about it though. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:15, 15 April 2026 (UTC) :Nice work. I for one don't care how you made the tool, the important part to me is how it works and if it helps me/us edit AW. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:23, 11 April 2026 (UTC) :[[File:AWE split paragraphs.png|thumb|Article on wheat]] {{ping|Immanuelle}} your tool is back at it again! I've asked you to test it before you use it to create a bunch of articles twice now. You, evidently, haven't listened! I understand you're probably acting in good faith, but you ''have'' to test your tool before you unleash it on the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:38, 18 April 2026 (UTC) ::No, I did listen. I am not sure what your objection is, but this looks like intended behaviour. I was asked to make every single sentence into its own paragraph to make it easier to debug maintaining accessibility. Previous the tool grouped many sentences into a single paragraph. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 02:49, 18 April 2026 (UTC) :::@[[User:Immanuelle|Immanuelle]]: You were asked to make each actual paragraph into a call of the "paragraph" function. You were not asked to make every individual sentence a paragraph. That is probably even less accessible than what we started with. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 03:06, 18 April 2026 (UTC) ::::The content itself needs refining. As it is, most articles have no value-added over the Wikidata triples plus labels; basically just slight readability improvements. We require complex structures sooner rather than later. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 03:08, 18 April 2026 (UTC) ::::I thought that the rule was that we put every single sentence into a paragraph of its own because text readers need a paragraph to read the text. We cannot debug things if there are multiple sentences within a paragraph, because these sentences go up to the top and make it so that the paragraph itself fails to render. ::::So this was specifically an accessibility concern for people who are visually impaired, with an accepted reduction in readability for people with regular vision so that it can also be debugged. ::::Like this: ::::"What we might try is wrapping each sentence as a paragraph, with occasional pairing of closely related sentences. That keeps failure isolated while preserving at least some natural flow. ::::We could consider also implementing a “sentence” or “content unit” function that simply calls “paragraph”, so we can later tell where the intended paragraphs are." [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:11, 18 April 2026 (UTC) :::::We need to import the quote template [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:12, 18 April 2026 (UTC) :Does anybody want any other changes to be made to this tool? Things are still relatively up in the air about what an optimum article even is, and as a result it kind of makes us limited in what we can do with it. I'm changing the way that the paragraphs work to fit what I now perceive as the consensus. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:11, 18 April 2026 (UTC) : I tried to run it on macOS 14.5, but it errored out when I clicked "Pull from Wikidata." It appears that this was because you hardcoded your Python path. <code>Error: Error invoking remote method 'generate-wikitext': Error: spawn C:/Users/Immanuelle/AppData/Local/Programs/Python/Python313/python.exe ENOENT</code> — [[user:JJPMaster|JJP]]_{[[user talk:JJPMaster|Mas]]_{[[special:contribs/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 11:56, 6 April 2026 (UTC) :: For the record, the solution is to go into <code>src/main.ts</code> and change the Python path to something other than <code>C:/Users/Immanuelle/...</code> — [[user:JJPMaster|JJP]]_{[[user talk:JJPMaster|Mas]]_{[[special:contribs/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 12:05, 6 April 2026 (UTC) : TYSM!! I did have to debug the code a little first to get it working, but this will be so helpful for me. — [[user:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[user talk:ChaoticVermillion|converse]], [[special:contribs/ChaoticVermillion|contribs]]) 11:59, 6 April 2026 (UTC) :: I am so sorry and I fixed it so the new release should avoid that problem in the future. — [[user:Immanuelle|Immanuelle]] ([[user talk:Immanuelle|talk]]) 17:55, 6 April 2026 (UTC) ::: @[[User:ChaoticVermillion|ChaoticVermillion]] btw there is an update that has a lot more functions and I am not sure if you are using it. The new one allows you to undo edits or restore revisions. Something that I cannot figure out how to do in regular Abstract Wikipedia. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:55, 8 April 2026 (UTC) == Wikiprojects == Are there wiki projects here? Can I just make some in this namespace? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 15:12, 10 April 2026 (UTC) :I don't see why not. It's a wiki, after all :). Please just don't flood the talkspace with templates that don't exist. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:51, 10 April 2026 (UTC) ::I've created a first Wikiproject ([[Abstract Wikipedia:WikiProject Core articles]]) and an explainer page ([[Abstract Wikipedia:WikiProject]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:11, 10 April 2026 (UTC) :::I made this one too [[Abstract Wikipedia:WikiProject Quality Prose]] [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:39, 10 April 2026 (UTC) ::{{ping|Feeglgeef}} Are WikiProjects for specific languages OK? Responsibility seems to be stretched between maintaining Wikidata labels and lexemes alongside creating and maintaining functions on Wikifunctions, so I'm unsure if Abstract Wikipedia would be considered a good place to coordinate these things. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:56, 20 April 2026 (UTC) :::There's no community consensus for or against, so, since this is a wiki, I don't see any reason why anyone would stop you :). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:46, 20 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #243 is out: Community proposals for capturing meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-10|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on three community proposals on syntactic approaches, we introduce a new Type (Complex numbers), we report on current hiccups on Abstract Wikipedia, we share more information about a presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1776101400 April 13, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:35, 10 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Numerous errors have been introduced, possibly due to the "AWE" tool == As [[User:Fram|Fram]] has [[w:Wikipedia:Village_pump_(WMF)#c-Fram-20260410163000-Fram-20260408131600|pointed out]] over on the English Wikipedia in his usual style, [[User:Immanuelle]] has been breaking pages such as [[Q711]] with edits such as [[Special:Diff/4383]]. I was able to [[Special:Diff/4415|fix this]] by changing "it" to Wikidata item reference in "defining role sentence". @[[User:Immanuelle|Immanuelle]]: Judging by your edit history, you have introduced this error to a lot of pages. Before continuing with your work to make the rest of the articles from your list, [[d:Wikidata:List of articles that Abstract Wikipedia should have]], I kindly ask you to fix the pages you've already made. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 17:16, 10 April 2026 (UTC) :This is, of course, what happens when you use a slop-machine to write code. See existing discussion on [[User talk:Immanuelle/Abstract Wikipedia Editor#Creates inaccessible content]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:19, 10 April 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]] I thought you wanted everything nested in the paragraph things. That's why I did that, following your request that you linked to. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:45, 10 April 2026 (UTC) :::I know. In the future, can you test whatever the slop-machine gives you ''on-wiki'' to ensure you don't mass-vandalize it again? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:52, 10 April 2026 (UTC) ::::@[[User:Feeglgeef|Feeglgeef]] the problem I faced is that I do not know how to actually understand error messages on this wiki. When every page fails to render, it is very difficult to know if I introduced an error, or the program introduced an error. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:18, 10 April 2026 (UTC) :::::@[[User:Warudo|Warudo]] I guess my question for you would be how did you figure out that this was an error on the page? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:19, 10 April 2026 (UTC) ::::::That's a fair question. The way things are now you can't be sure if the error is because of technical issues with the site or a bad page. In this case it was rather easy though. The "dependency" parameter of [[f:Z28016]] expects a reference to a Wikidata item but you passed the string "it" to it. That is an obvious mistake so it was easy to tell that it's not a random error. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 19:23, 10 April 2026 (UTC) :::::::That makes sense. I will try to be a lot more careful with error detection in the future. Hopefully the technical issues with the site are fixed and I can see the content issues more soon [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:08, 10 April 2026 (UTC) ::::I suggest that “vandalize” is an inappropriate choice of word in this case. Whatever your feelings about the quality of the code or the care with which it is being deployed, I think you could manage to assume good faith on the part of a fellow contributor. Thank you. ::::At a technical level, there is an issue with simply bracketing multiple calls together to yield a paragraph, since a failure in any one call will lead to the loss of the whole paragraph. In [[:f:Wikifunctions:Status updates/2026-03-26]], the advice given was: ::::::“By the way, here’s one tip: currently, caching for Abstract Wikipedia happens on the level of the “fragment”. This means that by putting several sentences into a single paragraph, the paragraph as a whole is being run, may cause time-outs, and will be cached. Instead, if, for now, you put one sentence into each fragment, caching and evaluation can be more spread out and should allow for more content.” ::::[[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:00, 10 April 2026 (UTC) :::::@[[User:GrounderUK|GrounderUK]] would you suggest removing the paragraph by default behavior in the editor over this? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:50, 10 April 2026 (UTC) ::::::What we might try is wrapping each sentence as a paragraph, with occasional pairing of closely related sentences. That keeps failure isolated while preserving at least some natural flow. ::::::We could consider also implementing a “sentence” or “content unit” function that simply calls “paragraph”, so we can later tell where the intended paragraphs are. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 21:23, 10 April 2026 (UTC) :::::::This is not accessible for users with screen-readers, and thus not a viable work-around. Each paragraph must be in a paragraph tag. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:31, 10 April 2026 (UTC) ::::::::It’s sub-optimal, I agree, but every unit of meaning would be wrapped in p tags, which is more accessible than a series of bare fragments or failed function calls. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:07, 11 April 2026 (UTC) :::::::::If you do need to make inaccessible articles, please at least give them a category on the talk page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:21, 11 April 2026 (UTC) ::::::::::We’d need to agree an accessibility standard first, but I’m not planning on creating any articles until there are suitable functions available. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:36, 11 April 2026 (UTC) :::::::::::I agree. Accessibility standards need to be established and not just assumed. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:28, 11 April 2026 (UTC) :::::::::::I definitely do agree that we need accessibility standards, but this isn't really a nice-to-have that you debate about but rather the floor. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:27, 12 April 2026 (UTC) ::::::::::::I took this thread as consensus that we need to have every sentence as its own paragraph. Is that incorrect? Do people want me to change it back to one paragraph per paragraph break? I removed that one because it covered up errors. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:21, 18 April 2026 (UTC) :::::When someone "vandalizes" it is not necessarily intentional, see [[wikt:vandalise]]. I do understand that Immanuelle has good faith, but at the same time, the "deployment" caused tens of articles to be broken, and furthermore I don't suspect something this bad would have slipped through had a human carefully reviewed the code. When a contributor deploys a semi-automated tool and uses it to make edits at the rate {{ping|Immanuelle}} was at this rate, you are morally obligated to test it. This wasn't the first time the slop-machine that they used caused them to mess up tens of articles, and if Immanuelle doesn't exercise extreme care in the future, I don't suspect it will be the last. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 10 April 2026 (UTC) ::::::It was a silent error that was only discovered by chance. What kind of testing would you have done to avoid this? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:37, 10 April 2026 (UTC) ::::::@[[User:Feeglgeef|Feeglgeef]]": On Wikipedia, "[[:en:WP:VAND|Vandalism]]" is a technical term that means "editing (or other behavior) '''''deliberately''' intended to [[:en:Wikipedia:DE|obstruct or defeat]] the [[:en:Wikipedia:Five_pillars|project's purpose]]''". Accidental disruptive editing is not considered vandalism. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 22:52, 10 April 2026 (UTC) :::::::@[[User:Warudo|Warudo]] on the topic of this glitch. I think I have removed it from all pages that had it. Please tell me if there are more that you see. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:29, 10 April 2026 (UTC) ::::::::Thanks for cleaning up :) [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:29, 11 April 2026 (UTC) :::::::This isn't the English Wikipedia, or even a wikipedia at all, despite the domain. Unless a defined technical term related to Wikifunctions I'd consider words to have their natural language meaning. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:28, 11 April 2026 (UTC) ::::::::@[[User:Feeglgeef|Feeglgeef]]: Last time I checked, this was the Abstract ''Wikipedia''. But in any case, this is the definition provided in [[f:Wikifunctions:Vandalism|Wikifunctions]] as well as [[meta:meta:Vandalism|meta]]. Vandalism has to be deliberate. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 08:50, 11 April 2026 (UTC) :::::::::It's not ''the'' Abstract Wikipedia like ''the'' English Wikipedia, but just Abstract Wikipedia. It isn't a Wikipedia in and of itself (as in, it's not supposed to be viewed by end readers), but rather a tool for Wikipedias. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:33, 11 April 2026 (UTC) ::::::::::It still has an independent editing community. Just because it draws from Wikidata and Wikifunctions doesn't mean content decisions aren't made here; it necessarily has to have some autonomy just like any language edition. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 19:18, 11 April 2026 (UTC) :::::::::“Deliberately” is also the first word of section 3.3 of our Code of Conduct, linked at the foot of every page. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:11, 11 April 2026 (UTC) :::::+1 Please assume good faith and keep it civil. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:27, 11 April 2026 (UTC) :@[[User:Warudo|Warudo]] will hold off on page creation [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:43, 10 April 2026 (UTC) :Just a note @[[User:Immanuelle|Immanuelle]], the project is a Beta version, so, in my opinion, it's not a good idea to flood it with a large number of [{{fullurl:Special:Contributions|target=Immanuelle&namespace=0&newOnly=1&limit=250&end=2026-04-10}} article stubs]. Additionally, the natural language functions are still limited.--[[User:Mdktb|Mdktb]] ([[User talk:Mdktb|talk]]) 18:58, 10 April 2026 (UTC) ::@[[User:Mdktb|Mdktb]] okay that is a good point. I think I was confused since I thought that we were more on the trying to get new users stage. I will stick to fixing up my errors and only making pages on things that I have a lot of stuff to say on. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:20, 10 April 2026 (UTC) :::@[[User:Mdktb|Mdktb]] and here is a wikiproject I made and tagged some pages with that is specifically related to developing more natural language [[Abstract Wikipedia:WikiProject Quality Prose]] [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:27, 10 April 2026 (UTC) ::Would you be willing to raise this in the project chat? I'm thinking we are in an experimentation state that will keep improving incrementally just like the first edition of Wikipedia did since January 15, 2001. Just like back then I don't think it's a good idea to arbitrarily limit good faith editing. We probably will have to revisit these articles later as more and better functions become available but that in itself is not a valid argument for refraining from edits. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:36, 11 April 2026 (UTC) :::Already here ;) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:05, 11 April 2026 (UTC) ::I agree with your stub-flooding comment, I don't think it's particularly useful to have a bunch of articles that say nothing. The concern right now should be testing. I expect that the way in which we write abstract articles will change drastically eventually, so writing hundreds of articles is not only a waste of time but a debt. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 11 April 2026 (UTC) :::We can always use [[Special:AncientPages]] to find them later on. :::My expectation is that things will change, but we’ll be able to change the articles. They aren’t set in stone. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 03:21, 18 April 2026 (UTC) :The error in question was that "it" ended up getting into the jsons as a string instead of the id for "it". This occurred due to an error with the program with function aliasing, functions and items can have aliases that are used to be human readable, and replaced with their codes during insertion. But apparently when you try to insert a nonexistent alias then it just inserts the text and there is no server side validation at all of edits. :My guess is that basically they do not have an api since they have no server side validation and were relying on solely client side, and did not anticipate someone building such a tool that accidentally bypassed client side validation through a cache injection which was motivated by UX purposes :I plan on attending the Monday volunteer meeting and asking about this issue. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:45, 10 April 2026 (UTC) ::> But apparently when you try to insert a nonexistent alias then it just inserts the text and there is no server side validation at all of edits. ::This sounds like a bug. Would you be willing to create a ticket in phab with details? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:38, 11 April 2026 (UTC) :::The team has already declined (or indicated that they had no plans) to do validation in this form, so I don't think a new ticket would be ideal. Either way, this shouldn't affect anyone besides those using a headless browser (or anyone using good, human-reviewed code and a headless browser), so I don't think it would be a priority anyway. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:19, 11 April 2026 (UTC) ::::Not sure what you are talking about. At the meeting they did not seem to be opposed to doing server side validation. They just said that they had a bit of concerns about infrastructure that was stopping it as an immediate thing. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:14, 15 April 2026 (UTC) :::::The volunteer's corner? I unfortunately missed that, but it was more than a year ago that I believe they decided not to pursue it, so you're probably right. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:46, 16 April 2026 (UTC) :So I have resolved this issue, as I have resolved most of the issues that people brought up. The whole paragraph debate is something I am returning to the older version of. Does anybody want other changes to the way that it makes articles? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:09, 18 April 2026 (UTC) == Sandbox page == The previous discussion about bot-created pages does raise a question: is it possible to have sandbox pages here? As far as I can tell, one can only create pages in the main namespace, and it has to be one page per Wikidata item. So there's no good place to experiment. Or am I missing something? The only other thing I can think of is to write the whole abstract article (or a part of it) as a function with a composition implementation on Wikifunctions and then to call it from a user-space sandbox page here. That, however, doesn't actually seem to work: [[User:Amire80/sandbox|I've just tried to call a function from my user space]], and I just see "⏳ Function is being called…". That is possibly a bug that can be fixed (maybe [https://phabricator.wikimedia.org/T422299 T422299]?), but even if it's fixed, it doesn't look like the best user experience. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:48, 10 April 2026 (UTC) :[[phab:T421417]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:52, 10 April 2026 (UTC) ::For now [[Q3938]] can be used for test edits . [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 02:06, 11 April 2026 (UTC) :We have [[Q138864867]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 23:30, 11 April 2026 (UTC) == I propose Q10693 for featured article == I think [[Q10693]] is the best article here. Can I propose it for [[Abstract Wikipedia:Featured article]] [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:24, 10 April 2026 (UTC) :We'd to come to a consensus on criteria first before we nominate anything. Anyway, the talk page of [[Abstract Wikipedia:Featured article]] would be a better place to decide this, not ''everything'' belongs on the project chat. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:36, 11 April 2026 (UTC) == REST API for editing? == Hi, does anyone know if there is a ticket in phab for a public API endpoint that allows editing of AW content? It would be very useful to improve tooling and content. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:41, 11 April 2026 (UTC) :I don't believe so. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:03, 11 April 2026 (UTC) :I do not know why there isn't a REST API, but I had to [[Abstract Wikipedia:Project chat#I made a desktop app that helps with editing|specifically work around it with my editing tool]]. It will be very nice in the future to have a REST API. :I think that right now there isn't actually any server-side verification of whether an article is well-structured, and that might be the reason why there isn't a REST API yet. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:46, 11 April 2026 (UTC) ::What rest api are you talking about? Checkout [[Special:RestSandbox]]. [[User:Tanbiruzzaman|Tanbiruzzaman]] ([[User talk:Tanbiruzzaman|talk]]) 16:50, 12 April 2026 (UTC) :I would like to proudly announce that it can be done. See [[Special:Diff/6102]]. Here was my request: :<syntaxhighlight lang="json">{ "source": "{\"qid\":\"Q100000\",\"sections\":{\"Q8776414\":{\"index\":0,\"fragments\":[\"Z89\"]}}}", "title": "Q100000", "comment": "Hello from MediaWiki REST API", "content_model": "abstractwiki", "token": "[token]" } </syntaxhighlight> [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 04:43, 20 April 2026 (UTC) == Spaces between sentences == In abstract articles with two sentences or more, I usually see two spaces between the sentences. Why two? I usually write one space, and that's probably what most people do in English. I know that some people write two; I don't like it myself, but this practice does exist. But here, it raises a few more nuanced questions: # Where is it actually defined that there are supposed to be ''any'' spaces between the sentences? I might be wrong, but it probably comes from the extension code and not from the functions. # Can this be customized per language? I don't know all the rules for all the languages, but I strongly suspect that some languages use spaces between sentences differently, and no default is good for all the languages. I'd especially check if it's good for Thai, Burmese, Japanese, and Chinese. # When I examine the HTML code of the rendered sentences, each of them is a <code><nowiki><div></nowiki></code>. It's a bit odd—I'd expect <code><nowiki><span></nowiki></code> there. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 21:07, 14 April 2026 (UTC) :Can you give an example article, please? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:01, 15 April 2026 (UTC) ::[[Q833]], [[Q11361384]], and probably every other abstract article whose rendered English text has more than sentence. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:34, 15 April 2026 (UTC) :::No, not every single one (see [[Q333]]), but most of them. This has happened because Denny promoted separating sentences into individual fragments and Immanuel used an AI slop-machine to create an editing tool. Essentially, they're being treated as separate elements (like how one paragraph is different from a section heading), so the UI adds a space. This, of course, should not be done, because it breaks screen-readers and looks weird, but apparently everyone is just OK with it. Like a thousand articles have been created by the afforementioned slop-generated tool (because the person who oversaw the bot that created it seems to care more about quantity than quality), whereas I've only created three myself (because I care more about quality and shaping the direction of the wiki in preparation for when abstract content becomes actually viable). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 15 April 2026 (UTC) ::::If I understand correctly, [[Q333]] has one fragment, which is one function call, which in turn creates two sentences and joins them using a hardcoded space. If each sentence was created using a separate fragment, they would probably appear with two spaces in practice. Neither option is very good. ::::The mass creation of abstract articles using that tool is probably not really related to this. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:52, 15 April 2026 (UTC) :::::No, one of them is objectively wrong and one of them is correct. You're not ''supposed'' to split two sentences into two fragments. That's the point. The mass creation of articles using that tool ''is'' related, because it's responsible for the proliferation of articles that follow the wrong one. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:36, 15 April 2026 (UTC) ::::::Why not split sentences into fragments? I can easily imagine some functions that produce several sentences, but it's not universal. ::::::And why is it ''correct'' to join sentences using a hardcoded space? Joining sentences shouldn't be done using a hardcoded space, but with a generic "join sentences" function, which will be one space for many languages, but probably not for all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 17:55, 15 April 2026 (UTC) :::::::Yes, not having to hardcode is the eventual goal. Splitting sentences into fragments is bad because it adds extra spacing (this is a feature, and a good one!), because it's bad for screen-readers, and because it would be impossible to distinguish between paragraphs, the article would just be a collection of sentences. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:03, 15 April 2026 (UTC) ::::::::I still don't understand why splitting into fragments is bad. What is good about extra spacing? It looks like a bad feature, not a good one. It sounds like a rendering and presentation issue, not a logical issue. Fragments can be inline, and the inline ones should be <code><nowiki><span></nowiki></code>s, not <code><nowiki><div></nowiki></code>s. And there should also be an option for <code><nowiki><div></nowiki></code> fragments. And maybe some others. Forcing every fragment to be a <code><nowiki><div></nowiki></code> sounds like a bad feature. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:46, 15 April 2026 (UTC) :::::::::Again, the spacing is good because the correct reason to split is to create two separate paragraphs. Even if the spacing ''was'' removed, it would still not work for screen-readers, and blocking out blind people when the mission is to spread knowledge to neglected languages is incredibly ironic. I'm not sure how else I'm supposed to communicate this to you. It's like asking "why is magma so hot! I want to drink magma instead of water, but it's too hot and not refreshing!" [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:07, 15 April 2026 (UTC) ::::::::::Maybe I understand what a "fragment" is supposed to be differently. Where is defined what is it supposed to be? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 20:22, 15 April 2026 (UTC) == Archiving discussions on this page? == We're soon coming up to having a month old messages here, and considering the current length of it and size of the community, perhaps 30 days is a good limit for archiving them. Does anyone know how to get an archive bot running here? <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 06:44, 16 April 2026 (UTC) :+1 [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 09:55, 16 April 2026 (UTC) :+1 [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:41, 16 April 2026 (UTC) :+1. I think SpBot does archiving on Wikifunctions. Maybe it could be brought here as well? [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 14:18, 16 April 2026 (UTC) :+1 [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:24, 16 April 2026 (UTC) == Importing the q template == I really want the <nowiki>{{q}}</nowiki> template here imported from wikidata. It is very helpful with qids. Linking to here instead of wikidata. Might be able to be expanded for lexemes and wikifunctions too. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:26, 16 April 2026 (UTC) :I've copied it and its dependencies from Wikifunctions: see {{Q|1}} It may need some tweaking to work well here, because we also use QIDs. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:51, 17 April 2026 (UTC) ::Great! I think we need [[Template:Quote]] too [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:13, 18 April 2026 (UTC) == Caching issues (hopefully) fixed == Hey all, I know the caching issues have been a real pain for you. I've just now deployed what (I hope) is a fix that works for calls on Wikifunctions.org, fragments here, and embedded Wikifunctions calls. See for example [https://abstract.wikipedia.org/view/en/Q1344227 view/en/Q1344227] which should load fragments near-immediately for you (not need a retry or time out). You'll also see e.g. that https://test.wikipedia.org/wiki/Wikifunctions now has "stable" results, not just endless "please wait" comments. That said, please tell me where I'm wrong and you're having issues! Much better to hear now than assume it's fixed and start all over again tomorrow. I appreciate your feedback and patience over this; it has been very generous of you all. Our next work in this area is to make the cache much more scalable and resilient over time, so it's faster and more reliable for you, and cheaper for us to support. Thank you again. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:47, 16 April 2026 (UTC) :Thank you (and the rest of the team) for your efforts for this new wiki! We really appreciate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:58, 16 April 2026 (UTC) :Wow this is great! Now we can do a lot more verification on whether created pages are working well! Gotta look over a bunch of pages. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 15:20, 16 April 2026 (UTC) ::Yes I tried to fix up a bunch of pages. Many of them actually render properly now. But I did need to change quite a few [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:36, 16 April 2026 (UTC) :::Yes, please give your attention to the quality of pages you've already created rather than expanding the quantity. For example, on [[Q153]] I notice that you used Z28016 a lot, but that "defining" should only be used when it is the only instance of that class in that location (which works fine for a capital city), but not e.g. for hydrogen being "the" part of ethanol. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:43, 17 April 2026 (UTC) == Importing templates from wikipedias == I think it would be a good idea to set something up so that templates from wikipedia can be represented as wikifunctions. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:59, 16 April 2026 (UTC) :Already {{done}} on WF, see [[f:WF:MediaWiki parser functions]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:08, 16 April 2026 (UTC) == Idea for the project chat == I've been thinking of some ideas that we could implement related to the project chat. I'm not saying I endorse anything, just throwing out an idea. There's been a ''lot'' of activity on here, I'm not sure if this is going to be a permanent thing or if it's just because the wiki just started. If it maintains its activity, we might want to divide it up like the English Wikipedia does, perhaps into "Proposals", "Technical and Wikifunctions", and "Miscellaneous." [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:19, 16 April 2026 (UTC) :Simple english wikipedia has almost all discussion happen on its Project chat. I think we should only add nerw things once we really need more chats. Having everything here makes it easier for people to keep up with the news of abstract wikipedia. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 16:31, 16 April 2026 (UTC) ::The place to keep up with news for "abstract [sic] wikipedia [sic]" is the newsletter. I think that separating might actually make it easier to follow the specific discussion that you want, as you can choose which of the three to subscribe to. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:58, 16 April 2026 (UTC) ::We should at least have a talk page archiving bot, like [[:en:User:lowercase sigmabot III]]. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 20:18, 16 April 2026 (UTC) == What to do with Z26955 == There are a lot of articles with [[:f:Z26955|Z26955]] in them, since it has this obvious warning on it, what should we do with existing articles that have it? Just remove it on sight? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 15:33, 16 April 2026 (UTC) :We should only improve articles by fixing the problems, not by removing them. If you can replace a function by a better one, that’s great. Otherwise, please leave it for now so that we can see what needs fixing. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:04, 16 April 2026 (UTC) == Representing "part of" == How do I represent that something is part of another thing? I used to use the spo sentence without understanding that it did not work. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 16:30, 16 April 2026 (UTC) :I think [[f:Z32982]] can be used, with the role as [[d:Q1310239]]. [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 18:55, 16 April 2026 (UTC) :See Q307, perhaps :https://abstract.wikipedia.org/view/en/Q307 :Middle finger of Galileo's right hand is the part of of Galileo Galilei. [[Special:Contributions/&#126;2026-25174-74|&#126;2026-25174-74]] ([[User talk:&#126;2026-25174-74|talk]]) 03:07, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #244 is out: Milestones; Some major issues hopefully resolved == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we celebrate 4000 functions on Wikifunctions and 1000 abstract articles on Abstract Wikipedia, we announce that we should have fixed some major issues with the websites, we inform you on our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:22, 17 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == AceWiki: Abstract Wikipedia before Abstract Wikipedia? == For those of you not in the know, ACE is [[w:Attempto Controlled English|Attempto Controlled English]]. This is a special subset of English that, unlike regular English, is entirely grammatically unambiguous and is machine-readable. For example, the sentence "Every person has a cat" is ACE, as a computer could easily parse that into a logical structure of the form "for any person P, P has a cat." Well, I found a semantic wiki software called AceWiki, whose articles are written entirely in Attempto Controlled English (see [https://acewiki.petapico.org/acewikigeo/ AceWikiGEO]). The sentence structures seen in AceWiki articles (while I can't link directly to any article, the article on the United States of America, which can be found in the Index in the sidebar, is a good example) are quite similar to those in our existing abstract articles. Using a tool called [https://github.com/Attempto/ACE-in-GF ACE-in-GF], ACE text could be translated into any language. I've been thinking about the idea of a tool that allows an editor to write Attempto Controlled English text, and have that text turned into an abstract article. As an example: '''ACE''' -- "Every antelope is a mammal." &rarr; '''Abstract content''' -- [[f:Z26627|Classifying a class of nouns (Z26627)]]: [[d:Q25894|antelope (Q25894)]], [[d:Q7377|mammal (Q7377)]] This tool would not be optimized for mass article creation, since it would not include an option to generate articles directly from Wikidata, but I think it could be interesting to see how being able to write abstract articles in natural language might lower the barrier to contributing to this project. Thoughts? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 01:59, 20 April 2026 (UTC) :I'm not sure how we'd actually do the conversion step. If you'd be willing to attempt to make a prototype I'd love to look at it, but I'm skeptical. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:12, 21 April 2026 (UTC) == Help with the news section on main page == Hi all, I would like to have some help in importing [[:f:Template:Main page/News]] here and inserting it in the main page's module. Can someone help me to do it? [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:26, 20 April 2026 (UTC) :I believe [[Template:Main page/News]] is already set up and visible on the main page, unless you mean importing the history of the WF template over. [[User: Tenshi Hinanawi|Tenshi!]] ([[User talk: Tenshi Hinanawi|Talk page]]) 11:12, 20 April 2026 (UTC) ::Ah, that's great, thanks! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:53, 20 April 2026 (UTC) == Layout guidelines? == One thing I'm noticing is that there are a ''lot'' of ways to do the same thing. I'd like to know which is preferred in the simple case of making single-sentence articles that just say what they are. Take [[Q503]] for example. If you look at the edit history of the article, you'll see it went through a few changes: * Initially, it was a [[f:Z14396|''string of monolingual text'']] call wrapped inside of a [[f:Z27868|''string to HTML fragment'']] call. The innermost function got the monolingual text returned from [[f:Z26095|''subject is kind of'']], converted it to a string, and then to a HTML fragment. * Afterwards the two topmost functions were removed until only the ''subject is kind of'' function call remained, and this was wrapped in a call to [[f:Z29749|''monolingual text as HTML with visible language tag'']]. * Finally the ''subject is kind of'' call was placed into a typed list provided as an argument to the [[f:Z32234|''join text-like objects into HTML fragment'']] call, which in turn was made into a proper paragraph rather than a standalone <code>&lt;div&gt;</code> as it was previously. None of these seem like a particularly bad way to approach things, and I have seem all of them in the wild; the first thing I tried I did so as it was the way the first article I stumbled upon chose to render its text. Since [[Abstract Wikipedia:Useful functions for article composition]] only goes over linguistic functions, and doesn't seem to provide any guidance on ''composition'' functions (i.e. building the HTML contents itself, as you have to do in the plain visual editor online), I thought I'd ask here if there is a preferred way to do things, and if it could perhaps be made clearer on the website if so. It is rather bothersome wanting to build e.g. a wikitable, and needing to peruse the available functions on Wikifunctions instead of having an easily-accessible way to see what is generally recommended for the particular circumstance. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:36, 20 April 2026 (UTC) :I'm partial to paragraph(join text-like objects into HTML fragment(your sentences)), as not using a paragraph tag is bad for those who use screen readers, and I designed join text-like objects to reduce function calls and therefore speed up the article processing step. The long-term problem with this method is that Japanese and Chinese both do not have spaces between sentences, so I plan to soon create a function that takes a list of text-like objects and then converts it into a paragraph under the correct style of each language. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:51, 20 April 2026 (UTC) ::That sounds good, I have grown more fond of that method as well. What you described would be great to have, I have been adding [[f:Z13128]] references inbetween each sentence to counteract the lack of spacing but something that would do this automatically for English while also obeying the sentence rules of other languages it renders in would be very ideal. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:33, 21 April 2026 (UTC) ::{{ping|Feeglgeef}} I noticed [[f:Z33068]]. I decided to hack up an implementation of it that aligns with what you said, I don't know if this is what your original intention for the function was and I apologize if I misconstrued it. At the moment, it just runs the ''join text-like objects'' function I mentioned earlier wrapped in a call to ''paragraph'', but adds spaces if the language is not Japanese or Chinese. I'm not sure if, in this scope, a lack of spaces is the only difference between how certain languages arrange their sentences. This also only accounts for the ZObjects for Chinese and Japanese specifically, I think some sort of switch statement or separate configuration object would be better suited for this—not to mention that there are separate natural language objects for the different scripts of Japanese, so those would have to be blanketed under Japanese when considering the language passed in (which I don't want to chain a bunch of ORs to do at the moment). For now, though, it seems to work fine. I added two different test cases and they both pass, and I have also utilized the function on [[Q241691]]. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 03:31, 23 April 2026 (UTC) :::Ah, thank you for implementing that, it looks good to me. I've created a persistent object for storing the languages that don't use spaces, [[f:Z33984]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:47, 23 April 2026 (UTC) == Wikidata problems == Sorry for posting two questions here in a row. I'll try to make this brief. On the bottom of [[Q247237]] is what ''should'' be a list of albums, but on my end it appears as just "''PLUS''" repeated fourteen times. This seems to occur any time I use [[f:Z13464]] on a list of Wikidata item references... is anyone else seeing this? I'm not sure what I could be doing wrong. Related to this, I wonder if I can avoid needing to explicitly state each of these items? I moved the list to a separately-defined object on Wikifunctions to avoid having to constantly transfer it between websites since I don't think the clipboard works cross-site. Ordinarily, if I were trying to get all Autechre studio albums, I would use Wikidata's SPARQL query feature to do this, by finding every entity whose [[wikidata:P31|P31]] is [[wikidata:Q482994|Q482994]] and whose [[wikidata:P50|P50]] is [[wikidata:Q247237|Q247237]]. This doesn't seem to be doable with Wikifunctions, though, or at least I'm not seeing it... so I don't know how I would do this automatically. We are making articles out of functions here, so I think it would be worthwhile if I tried to future-proof the list using this paradigm. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:30, 21 April 2026 (UTC) :On your first question, I've [[f:Z33903|tried to replicate this on WF]] and I cannot, which makes it difficult to solve. :We cannot currently reverse most WD statements, so your use case is not ''currently'' possible, but we are able to access the statements that are ''on'' an item. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:10, 21 April 2026 (UTC) ::I'm experiencing the issue again on [[f:Z33997]], it seems. Check the test results of the three-item test, "''programmer''" should not appear twice. I ran into a similar problem earlier in working on the implementation. For the two-item case, using a call to ''[[f:Z13397|get the nth element of a list]]'' on both items (index 1 and 2 respectively) returned the first item twice. I had to use a call to ''[[f:Z811|first element]]'' to fix it. ::Could this be a caching issue, perhaps? That seems likely, because I don't know why else this would be happening. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:16, 23 April 2026 (UTC) :::I am considering raising this issue on Phabricator if it hasn't been brought up already, this doesn't seem intentional. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 24 April 2026 (UTC) == What are we called? == If editors of Wikipedia are Wikipedians, editors of Wiktionary are Wiktionarians, editors of Wikivoyage are Wikivoyagers, and editors of Wikiversity are Wikiversitarians, what are we? Abstract Wikipedians? Abstracters? Abstractions? AWians? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 11:54, 24 April 2026 (UTC) :I don't like Abstractions and AWians. Abstracters sounds cool, it could be our "informal" term, while Abstract Wikipedians is our "formal" one. We could also apply it based on context (in the mainspace you're an abstracter, in the projectspace you're an abstract wikipedian), I'm not sure, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:12, 24 April 2026 (UTC) :I think an -or ending for 'abstractor' sounds cooler, personally. Abstract Wikipedians is boring but is the most straightforward option. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:50, 24 April 2026 (UTC) ::I did mean to spell it as "Abstractors." Sorry about the typo. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 18:55, 24 April 2026 (UTC) == Indexed by Google - deliberate? == https://www.google.com/search?q=site%3Aabstract.wikipedia.org%2Fwiki%2F Exposing Qid to Google looks like a mistake. Not likely to attract the public. Might adversely affect Wikipedia's Page rank or whatever? [[Special:Contributions/&#126;2026-25174-74|&#126;2026-25174-74]] ([[User talk:&#126;2026-25174-74|talk]]) 04:20, 25 April 2026 (UTC) :Indexing may already have stopped, after the 7th April - no recent pages found. [[Special:Contributions/&#126;2026-25174-74|&#126;2026-25174-74]] ([[User talk:&#126;2026-25174-74|talk]]) 04:26, 25 April 2026 (UTC) == I can't edit generated text on pages for some reason? == why is this? Thank you. [[User:BigKrow|BigKrow]] ([[User talk:BigKrow|talk]]) 07:58, 25 April 2026 (UTC) :You're not supposed to be able to edit generated text. You can edit the code that makes it, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:58, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:54, 25 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Why the editing API doesn't work == {{tracked|T423542}} Immanuelle wrongly stated that there is no REST API for editing. [[#REST API for editing?|There is]]. However, it does not work when called from software outside Abstract Wikipedia. That is because there is no way to grant a bot password or OAuth customer the permission to edit abstract articles (<code>wikilambda-abstract-edit</code>) and create them (<code>wikilambda-abstract-create</code>), since no grant on [[Special:ListGrants]] includes either. Should this be fixed? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 01:57, 26 April 2026 (UTC) :Yes I think the rights should be added. I think the number of automated edits should be low at the moment as Abstract Wikipedia is still in an early phase and so far there is not much support for small languages and so many functions will maybe change to cover more languages. As automatic editing using a Bot Account requires an formal request it is no problem if the option exists. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:17, 26 April 2026 (UTC) :Sounds good to me. Could we add a bot section to [[Abstract Wikipedia:Requests for permissions]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:35, 5 May 2026 (UTC) ::[[Abstract_Wikipedia:Requests_for_permissions#Bot]] ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:56, 5 May 2026 (UTC) == Q884 == The page [[Q884]] has inaccurate statements about the head of government and the head of state of South Korea. Part of what it returns in English is "Lee Ju-ho is the head of government of South Korea.Park Geun-hye is the head of state of South Korea." However, neither Lee Ju-ho nor Park Geun-hye currently have their respective roles mentioned here. How should these statements be turned into ones using the past tense? [[User:Intolerable situation|Intolerable situation]] ([[User talk:Intolerable situation|talk]]) 14:44, 30 April 2026 (UTC) :not currently possible :((((( [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:46, 30 April 2026 (UTC) :Feeglgeef is correct, past tense sentence generation is something we are sorely lacking at the moment. If you look at [[f:WF:Type proposals#Representing abstract content|Wikifunctions' type proposals]] you can see some initiatives that could hopefully mitigate this. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:49, 1 May 2026 (UTC) == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3>According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) dkpt6z8gcmi1xwftuwfjpbnj6f22x2c 7564 7550 2026-05-11T19:06:47Z Asked42 130 /* about the usage of Z33068 */ Reply 7564 wikitext text/x-wiki {{Shortcut|[[Project:PC]]|[[Project:VP]]}} __NEWSECTIONLINK__ [[Category:Abstract Wikipedia administration|Project Chat]] This is the Abstract Wikipedia Project chat. This is where discussions on the project happen. Add your discussion below this line. More technical issues should go to [[Abstract Wikipedia:Report a technical problem]]. For older conversations, see the archives ([[Abstract Wikipedia:Project chat/Archive 1|1]]). == Put this on ice == How are non-English speakers (who this project is specifically for) meant to develop this wiki's practices and policies if a) all project pages are only available in English, and discussion is largely done in English, and b) there's no attempt to get non-en.wiki communities onboard. At present this looks like it's just going to produce Anglocentric/Eurocentric content, which belies the whole point of having a wiki in one's native language. Yes it's early days and everyone is experimenting and bug-fixing, but the project has already been released to community control, with a predominantly English-speaking/European community. This needs to be put on ice until it can be launched properly with multilingual support and invitations to all wikis, particularly smaller ones. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 11:44, 28 March 2026 (UTC) :Just because it's not perfect doesn't mean it needs to be shut down. These are all gradual processes. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:58, 28 March 2026 (UTC) ::There’s being "not perfect" where things can be improved at a later date, and then there's having antithetical foundations. Also see [https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(WMF)#c-Warudo-20260327114000-Warudo-20260327113600] re functions. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 16:15, 28 March 2026 (UTC) :::You haven't named a single thing that can't be improved at a later date. We're hoping to be able to translate project pages. Non-enwiki communities can be gotten on board later. Function generation already works multilingually in many cases, and those where it does not can be improved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:57, 28 March 2026 (UTC) ::::When the practices and policies will have already been developed, and informal positions of authority already filled. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 17:04, 28 March 2026 (UTC) :::::@[[User:Kowal2701|Kowal2701]] Thank you for your concerns. We are already aiming at less-served communities through specific calls to action to create more language functions and abstract content in their language. Just give the time to actually see these changes happen. Cheers, [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 18:55, 28 March 2026 (UTC) ::::::Hi Sannita, I'm just wondering how are AW project pages planned to be translated in the future? Is there going to be use of some kind of automated tool such as DeepL or Google Translate, or will it be a custom-designed system? [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 20:39, 28 March 2026 (UTC) :::::::@[[User:EatingCarBatteries|EatingCarBatteries]] We will enable the Translate extension soon, so everyone will be able to translate project pages into their own languages. Sorry for keeping you waiting on this. [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:41, 29 March 2026 (UTC) :@[[User:Kowal2701|Kowal2701]]: thank you for your concern and suggestion. When this Beta started, we have immediately [[:f:Wikifunctions:Status updates/2026-03-19|mentioned that there might be the possibility of restarting the project]]. So that might indeed happen. :But so far, this early start of the not fully polished project allows us to learn so incredibly much. In the last few days we have learned so much more than we would have been able without the launch in months! And it helps us to focus on where to put our limited resources, so that we can make the overall project better quicker than would have been possible otherwise. From that perspective, this has been quite a success. :I am trying to understand your suggestion: what do you think would need to be in place before a possible relaunch? Which requirements would need to be met? --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 13:53, 29 March 2026 (UTC) ::Thank you, I wasn't aware of that. Some uninformed thoughts below. ::Re communication: ideally people would communicate using functions, and there'd be some kind of visual editor where people type in their native language and it gets translated into functions, but I realise that's a pipe dream. Something that allows people who don't have a mutual language to communicate is imo necessary, maybe there could be a tool that machine translates comments. Machine translation ''sucks'', but so long as people get the gist of what is being said, that'd be better than nothing. I dread to think what disputes would be like though. ::Re invitations, idk what has already been done, but I would've thought now would the time to get some people from smaller wikis editing and experimenting, just an invitation on a wiki's main noticeboard would probably do the trick (is there a [[meta:MassMessage]] service for updates re Abstract wiki that could be recommended?). Then a central or watchlist notice for the actual launch, hopefully by which time there'd already be a small group of editors able to assist the influx of newbies. An intuitive tutorial is also necessary, as well as an intuitive version of [[f:Wikifunctions:Catalogue]]. [[User:Kowal2701|Kowal2701]] ([[User talk:Kowal2701|talk]]) 18:14, 29 March 2026 (UTC) :::What do you think about boilerplate templates. So writing a sentence and then marking the parts of the sentence what can be derived from Wikidataitems or the lexeme linked to it. This seems to me like an realistic approach for making it easier to contribute. I am happy you wrote about the predominantly English-speaking/European community involved in this project. It seems like it is different to contribute so far and I had the expectation people from small language versions come on their own and contribute also if they dont speak English. So far it seems to be not the case and I hope it will be easier to contribute. I think for the beginning the goal of Abstract Wikipedia should be generating sentences based on data. So supporting small language versions should be not the goal of the first phase as it seems to take some time and improvements of the structures to make it easier to contribute. Sharing the work and offering people help with creating an function for an specific sentence can be a important way of getting more content in Abstract Wikipedia. Maybe it is unrealistic to find a huge number of people who are interested in writing functions who generate text. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:58, 29 March 2026 (UTC) :::[[Abstract Wikipedia:Useful functions for article composition]] is already available, as is [[Help:How to create an article]], but they are not perfect. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:05, 29 March 2026 (UTC) :Wikidata has a project chat in many languages. We can do that in the future. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:28, 16 April 2026 (UTC) ::Anyone can write on this page in any language. Personally, I’d prefer to see the original and get it translated into English rather than trying to make sense of a poor machine translation without even knowing which language the original was in. For the same reason, I would generally reply in English. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:18, 16 April 2026 (UTC) == Gendered languages == I've created [[Q79097672]], an article for a woman singer. In gendered languages however, it defaults to using masculine words. An example: in Portuguese, it reads "Arlo Parks é um cantor", when it should be "Arlo Parks é uma cantora". Is there any fix to this? [[User:Skyshifter|Skyshifter]] ([[User talk:Skyshifter|talk]]) 23:49, 28 March 2026 (UTC) :Yes. But each language is handled separately. I think Italian is doing it. German was started but got stuck… it should be working here soon. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 00:48, 29 March 2026 (UTC) ::Italian is not doing it. It is just a happy coincidence that for some reason "cantante" is always treated as feminine (I have to investigate why). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:59, 7 April 2026 (UTC) == Why don't we just structure this with wikitemplates? == I feel like the project could be done a lot better by using templates kind of like how wikipedia does them. Just the entire thing is templates that can be rendered in many languages. So like [[Q106289265]] would have the content <nowiki>{{Z26039|Q7257}}</nowiki> and could even have some aliasing done across languages so it could be <nowiki>{{subject is|Q7257}}</nowiki>. Code would be editable with a regular visual editor or code editor. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:34, 29 March 2026 (UTC) :This is available in pages when Parsoid rendering is enabled. We don't use this becuase it doesn't make sense for constructing and editing massive articles. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:37, 29 March 2026 (UTC) ::How do you do parsoid rendering? And why wouldn't it make sense? With aliases and everything could work great. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:12, 29 March 2026 (UTC) :::I believe it is enabled by default. If you do have it on: {{#function:Z10000|you'll s|ee this}} [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:54, 30 March 2026 (UTC) :you may be interested in reading this old [[m:Abstract_Wikipedia/Google.org_Fellows_evaluation|Google report]]. [[User:BrokenSegue|BrokenSegue]] ([[User talk:BrokenSegue|talk]]) 14:32, 9 May 2026 (UTC) == Automatically querying wikidata == Is it possible in the future for this project to have things that automatically query wikidata? Like an infobox that gives people's spouses, or a function that queries a specific property on wikidata [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:10, 29 March 2026 (UTC) :Yes, that is the long term goal. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:37, 29 March 2026 (UTC) ::What’s “long term” about it? We already have functions that query specific properties on Wikidata, [[f:Z32431]] being a simple example. A list of spouses seems like a fairly simple function too, although there might be performance issues if there are a lot of spouses. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:01, 31 March 2026 (UTC) :I had exactly this question. One of the example here is [[Q1033]] where I read "Nigeria is the most populous country in Africa.". The problem is that this concept is hard-coded. What if its population will decrease and it will become the second-most populous country? [[User:Wiso|Wiso]] ([[User talk:Wiso|talk]]) 08:21, 20 April 2026 (UTC) == Searching for other namespaces in the search bar == Something that has always irked me with Wikidata, Wikifunctions, and now Abstract Wiki is that there are no search suggestions when you are searching in other namespaces in the search bar. For example, if I were to type "Abstract Wikipedia:", nothing shows up. Whereas on enwiki, you can do this just fine. Is this because these sites are using a more "modified" version of MediaWiki? [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 04:38, 30 March 2026 (UTC) :I also find this very annoying. I'm not sure if there's anything that can be done about it or if it is a result of technical limitations ({{ping|Jdforrester (WMF)}}?). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:41, 30 March 2026 (UTC) ::@[[User:EatingCarBatteries|EatingCarBatteries]], @[[User:Feeglgeef|Feeglgeef]]: The search interface indeed is designed to only search the Wikidata concepts that would take up the main namespace. This is conceptually the same as the search on Wikidata.org. We'd welcome Phabricator tasks for ideas on how to additionally provide wikitext community page search, though implementing that might not be a priority. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 12:11, 30 March 2026 (UTC) :::Hint: don’t use the Search bar… :::When it is empty, click the adjacent Search button. This takes you to the Search page. :::Type the namespace with final colon. You are prompted with available pages and the prompt is refined as you type. :::Click a page title in the suggestions or click Search for a full search in the entered namespace. :::A search with just a namespace will return no results. A search with a partial identifier will work only [[Special:Search/Talk:Q1*|with an appended asterisk]] (delete the asterisk to see page suggestions). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:11, 30 March 2026 (UTC) == List articles == I am interested in creating list articles ([[:de:Liste_der_Naturdenkmale_im_Bezirk_Mitte|like this one]]). But I have no idea what it needs and how to start. [[User:GPSLeo|GPSLeo]] ([[User talk:GPSLeo|talk]]) 19:58, 30 March 2026 (UTC) :An example I've created that you can copy and adapt is [[Q11750]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:27, 3 April 2026 (UTC) == Logo == {{Tracked|T424781}} In vector2009 and monobook, the logo shows as the standard enwiki logo. Which is confusing as this is technically a whole other sisterproject. I suggest [[:File:Wikipedia-logo-blank.svg|this]] be used as a temporary logo for these skins. [[User:Kinopiko|Kinopiko]] ([[User talk:Kinopiko|talk]]) 06:00, 31 March 2026 (UTC) :There's also the scalable favicon, [[commons:File:Abstract-Wikipedia-favicon.svg|Abstract-Wikipedia-favicon.svg]] [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 01:54, 3 April 2026 (UTC) :This still appears to be as of yet unfixed. I understand this wiki is still very early in its lifespan so I'm not particularly miffed about it, it looking identical due to the logo is rather confusing at first but with separation with tab groups in my browser it becomes manageable. I am personally excited to see what logo(s) will be devised for this project; seeing the same thing happen for the other sister projects has been very fun to watch in the past. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:49, 20 April 2026 (UTC) == Extra spaces between sentences == There should be no spaces between two sentences of Chinese and Japanese. —[[User:内存溢出的猫|内存溢出的猫]] ([[User talk:内存溢出的猫|talk]]) 12:38, 2 April 2026 (UTC) :I'm not sure how we plan to handle this. I'll bring it up on the Telegram/IRC. This applies to Korean too, yes? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:28, 3 April 2026 (UTC) {{tracked|T}} :Please link to the corresponding Phabricator ticket when it’s raised. (Or I will, when I raise it). I think the technical issue is that the space is inserted between function calls. There may be two, but HTML reduces their appearance to one, which is one too many for certain languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:58, 3 April 2026 (UTC) ::No, your sentences should not be individual fragments. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:40, 11 April 2026 (UTC) == community curation of abstract articles of the week/month/etc. == [[wikifunctions:wikifunctions talk:status updates/2026-03-26#Move Status Updates to Abstract Wikipedia?|this thread]] at WF mentions that WMF staff are refraining from content decisions at Abstract Wikipedia; so I thought that it might be a good idea to figure out if and how there will be editathons here focussed on a selection of articles. — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 20:38, 2 April 2026 (UTC) : I would support this. — [[user:Feeglgeef|Feeglgeef]] ([[user talk:Feeglgeef|talk]]) 01:29, 3 April 2026 (UTC) : now I notice [[abstract:featured article]] in the same category as the project chat, so there's a location for a related concept already! (coming at it the other direction: recognizing already good articles versus barnraising that quality) — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 01:48, 3 April 2026 (UTC) ::I think it will be quite a while before we can support a “good” article, let a “featured” one. At this stage, I’d settle for “technically interesting”, to include “of archaeological interest” (like the first use of a particular function or function-call pattern). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 08:51, 3 April 2026 (UTC) :::one goal could be to make stubs and grow them for the basic concepts underlying Abstract Wikipedia, in an attempt to self-document. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 02:45, 7 April 2026 (UTC) == JSON format == The JSON format for Wikifunctions is described at [[:f:Wikifunctions:Function model]]. Is there such a documentation page for Abstract Wikipedia? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:19, 2 April 2026 (UTC) :I imagine that it would be identical? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 11 April 2026 (UTC) ::No, they aren't. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 02:50, 11 April 2026 (UTC) :::Oh, I see, you're talking about the underlying text format? That isn't and (from what I've gathered, though {{ping|Jdforrester (WMF)}} didn't respond last time I pinged him) will never be editable by users. The function model where the calls are actually made is identical to Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:36, 11 April 2026 (UTC) ::::I'm not asking whether it's editable. I'm asking whether there is a page that documents what it is. ::::The JSON of the function calls is perhaps the same as Wikifunctions compositions, but there are also other things there, which are not the same as Wikifunctions. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 22:40, 11 April 2026 (UTC) :::::I'm saying that I'm not sure why you'd ''need'' or ''want'' to understand it if you can't edit it and it doesn't impact the user experience in any way. Is there a specific problem that you are running into? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:28, 12 April 2026 (UTC) ::::::I'm a very curious person. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 01:19, 12 April 2026 (UTC) :This is an example JSON of an Abstract Wikipedia article, with only the [[f:Z801|Echo function]], if you're curious: { "qid": "Q27318", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z801" } ] } } }. :The base has two key value pairs, "qid" and "sections". "sections" currently only contains one key-value pair as of now, [[d:Q8776414]], aka lead section. "fragments" is where the Wikifunctions compositions are stored. I have no idea what "index" is. [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 02:35, 12 April 2026 (UTC) ::Yes, that's what I see. I can make educated guesses about those things, but if possible, I'd prefer to read an official reference documentation page. The one about Wikifunctions is fairly good. The one about Abstracts Wikipedia doesn't seem to exist. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:25, 12 April 2026 (UTC) :::I think the reason there's no documentation is that it's merely a curiosity, whereas the mainspace of the wiki is barely functional right now. Perhaps we'll get one later, or whenever/if ever we get the ability to edit it? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:09, 12 April 2026 (UTC) ::Just to clarify (?), index is 0! I believe it can only be 0 at present, at least through the user interface, and I imagine [[:phab:T411699|this ticket]] is to allow a non-zero index to be set and modified (so long as it is positive and, in all likelihood, sequential). [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:00, 12 April 2026 (UTC) :Not yet. I think such a page on Abstract Wikipedia would be for the community to create and maintain. I don’t know how [[:phab:maniphest/graph/411686|these things]] are decided upon, but I don’t see a task that would cover technical documentation of any kind. :The development team will no doubt respond with enthusiasm to any questions from the community on matters of technical detail, but I’d be inclined to let such interactions be led by the needs of on-wiki documentation, rather than a proliferation of Phabricator tasks and Project-chat topics. :Shall we ask once on [[Abstract Wikipedia talk:Frequently Asked Questions]] and see which questions should count among the frequently-asked? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:37, 12 April 2026 (UTC) ::@[[User:GrounderUK|GrounderUK]], this is quite definitely something that the extension developers are supposed to create and maintain. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 20:32, 12 April 2026 (UTC) :::Not as content on this wiki, was my point. Here, I suggest, we should reference any relevant technical documentation from whichever pages we, as a community, choose to create for such a purpose. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:06, 12 April 2026 (UTC) ::::I don't care very much where it is. I'd just like to read it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 23:25, 12 April 2026 (UTC) :@[[User:Amire80|Amire80]]: The Wikifunctions function model is documented (alongside its two JSON forms) because we anticipate people would (and should) build tools using it directly. Conversely, the vague expectation ("plan" would be too strong at this point) for Abstract Wikipedia, on the other hand, is that we'll provide APIs to interact with the content, but its serialisation will change over time as features are added to better support the Abstract Wikipedia community's wishes. :For a concrete example (''not a commitment!'') of how the serialisation might change, whilst the system kept working as before, we might in the future add a top-level concept for an abstract article's infobox, which would be shown, edited, and stored apart from the rest of the article's sections, and used differently downstream. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:27, 12 April 2026 (UTC) == Bot request == {{Tracked|T421151}} Can someone smarter than me please create a bot that connects local items to Wikidata equivalents? Right now, we are growing and there are [[Special:UnconnectedPages|hundreds of unconnected pages]] here that are just 1:1 main namespace entries that have identical names at [[:d:]]. I have connected several of these, but this seems like a very inefficient and silly thing to do manually. Can someone help here by making a bot that checks [[Special:UnconnectedPages]] regularly or even [[Special:NewPages]] and connects pages? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 06:17, 3 April 2026 (UTC) :This doesn't sound like something that should be a bot, but like something more automatic and built-in. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 11:27, 3 April 2026 (UTC) ::@[[User:Amire80|Amire80]] and [[User:Koavf|Koavf]]: Would a bot be a good idea in the interim period before that can be added to the software? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 14:31, 3 April 2026 (UTC) :::Yes, please. Granted, Amir, doing it automatically would be nice, but that feature doesn't exist. Until then, a bot would be very helpful and seems like it would be very difficult to cause problems. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 14:57, 3 April 2026 (UTC) ::::@[[User:Amire80|Amire80]] and [[User:Koavf|Koavf]]: I've written some code for this purpose [[gitlab:toolforge-repos/jjpmaster-bot-wd-t1|here]]. <code>Retrospective.py</code> is meant to be run once, and would connect all existing pages (once the trial run is over). <code>Prospective.py</code> would run once daily and connect any pages that have been created since the previous day. That is, until the Phabricator ticket is resolved, obviously. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 21:42, 3 April 2026 (UTC) :::::Boss. I'm so glad that you're smarter than me. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 03:25, 4 April 2026 (UTC) :::::{{ping|JJPMaster}} You might want to use <syntaxhighlight lang="python" inline>{ 'action': 'query', 'list': 'querypage', 'qppage': 'UnconnectedPages' }</syntaxhighlight> instead. That way, you won't have to maintain two scripts. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 03:58, 4 April 2026 (UTC) ::::::@[[User:NguoiDungKhongDinhDanh|NguoiDungKhongDinhDanh]]: This is [[gitlab:toolforge-repos/jjpmaster-bot-wd-t1/-/commit/415688aa6f9e1dcbafa21a8b3249899c07f298e9|done]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 05:01, 4 April 2026 (UTC) :::::::{{ping|JJPMaster}} One more problem: You seem to be linking non-mainspace pages as well. Don't forget to check <syntaxhighlight lang="python" inline>page['ns']</syntaxhighlight>. Also, why <syntaxhighlight lang="python" inline>if(i > 2): break</syntaxhighlight>? [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 05:27, 4 April 2026 (UTC) ::::::::@[[User:NguoiDungKhongDinhDanh|NguoiDungKhongDinhDanh]]: The <code>if not qid.startswith("Q")</code> bit was supposed to address the namespace problem. The break statement is for the trial of the bot. The integer in the if statement will change once the request is made. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 17:04, 4 April 2026 (UTC) :::::::::{{ping|JJPMaster}} [[Special:UnconnectedPages]] results are ordered by namespace, so checking for <syntaxhighlight lang="python" inline>page['ns']</syntaxhighlight> will also help prevent unnecessary iterations. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 19:54, 4 April 2026 (UTC) :::@[[User:Amire80|Amire80]], [[User:Koavf|Koavf]], and [[User:NguoiDungKhongDinhDanh|NguoiDungKhongDinhDanh]]: Is a Wikidata BRFA in order at this time? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 05:03, 4 April 2026 (UTC) ::::{{ping|JJPMaster}} Go ahead, please. [[User:NguoiDungKhongDinhDanh|<span class="skin-invert" style="color:black;font-family:Monotype Corsiva;font-size:110%;font-weight:normal;line-height:normal">NguoiDungKhongDinhDanh</span>]] 05:25, 4 April 2026 (UTC) :::::See [[d:Wikidata:Requests for permissions/Bot/JJPMaster (bot)]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 18:00, 4 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #242 is out: Request for Discussion: Syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we introduce a proposal for Natural Language Generation, we introduce a page for function suggestions from Abstract Wikipedia, we inform you that there will be a presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1776101400 April 13, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:37, 3 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Way to specify population == Hi! I was wondering if there was a function to specify the population of a place, possibly resembling the following: :N X live in Y. N would be the population size, X would be what comprises the population (e.g., humans, frogs, etc.), and Y would be the location. [[User:Babelball|Babelball]] ([[User talk:Babelball|talk]]) 15:43, 3 April 2026 (UTC) :I don't believe we do. Thinking about it now, we should probably have a page where users can request linguistic functions in a more viable format than [[f:WF:Suggest a function]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 11 April 2026 (UTC) == The problem of when "X is a Y" and Y is a phrase == Consider [[Q486972]], whose second sentence is supposed to be "A human settlement is a populated place," generated using the "Article-ful instantiating fragment" function. However, it fails, because the implementation [[f:Z23414|Z23414]] inherently checks for a lexeme linked to the superclass ("[[D:Q123964505|populated place]]"). However, since "populated place" is a phrase whose meaning is reducible to the sum of its parts, there is no lexeme for it. Therefore, it's virtually impossible to say "An X is a Y" where Y is a non-idiomatic phrase. Additionally, languages with grammatical gender are rendered particularly problematic. Consider [[Q6636]]. The first sentence of this article renders perfectly fine in English: "Homosexuality is a sexual orientation." However, it does not render at all in Spanish. That's because that language's NLG functions use lexicographic data to determine the gender of the phrase "sexual orientation." As there are no such data available for that phrase, it errors out. I did think about using [[f:Z29743|Z29743]] (description of class with adjective and superclass) instead, but that didn't work, since there's no item linked to the adjective "sexual"! Any ideas for how to avoid this? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 00:21, 4 April 2026 (UTC) :We'd the co-operation of Wikidata contributors here, I think. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:37, 11 April 2026 (UTC) == I made a desktop app that helps with editing == [[file:Abstract Wikipedia Editor v4.1.0.png|thumb|alt=screenshot|now there's a screenshot available]] I made a desktop app that helps with creating and editing Abstract Wikipedia pages. It pulls data from wikidata to form templates that it makes into wikitext, and it can round-trip articles into and from the wikitext. Here it is [[User:Immanuelle/Abstract Wikipedia Editor]]. I hope that it helps with editing. — [[user:Immanuelle|Immanuelle]] ([[user talk:Immanuelle|talk]]) 00:51, 6 April 2026 (UTC) : I've created [[Abstract Wikipedia:Tools]] for tracking these things. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:44, 7 April 2026 (UTC) : @[[User:Immanuelle|Immanuelle]] But the main namespace is not for wikitext. Are you publishing this content there anyway? <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 15:05, 7 April 2026 (UTC) :: It's not actual wikitext. It's a custom template syntax that's kind of like wikitext, which gets converted into abstract content when you press "Push to Abstract Wikipedia." [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 16:57, 7 April 2026 (UTC) ::: @[[User:Ainali|Ainali]]@[[User:JJPMaster|JJPMaster]] if you have syntax suggestions I am interested. I was in a rush with implementing this, and I want to in the future implement aliases for wikifunctions and possibly items, so that you can type things out yourself. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:53, 7 April 2026 (UTC) ::: Ah, I see. IT was just the announcement that was ambiguous then. <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 20:03, 7 April 2026 (UTC) : FYI anything made by a clanker AI robot is not "made by you." Thank you for your attention to this matter. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:18, 7 April 2026 (UTC) :: Who, then? [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:16, 7 April 2026 (UTC) ::: The clanker AI robot. [[User:Babelball|Babelball]] ([[User talk:Babelball|talk]]) 16:42, 8 April 2026 (UTC) :::: I edited the Wikidata page for the tool to mention Claude. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:35, 8 April 2026 (UTC) ::::: FYI that LLM-generated code is not eligible for copyright, and therefore the MIT license by extension. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:59, 9 April 2026 (UTC) :::::: I think the statements that Wikidata could make are limited by what references can be found. [https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository This help page] makes it sound as if there are limited options for expressing a repo's licensing situation, so I am not surprised that MIT should be the blanket release, even if strictly speaking some of the code contained within is ineligible for copyright, or infringes on an existing copyright (which would need to be demonstrated). But I suppose [https://cpomagazine.com/cyber-security/taking-stock-of-the-anthropic-source-code-leak-ai-agent-compromise-signals-security-issues-claude-copies-ahead-of-massive-ipo turnabout] is fair play? — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 19:53, 9 April 2026 (UTC) ::::::: @[[User:Arlo Barnes|Arlo Barnes]] I like the idea of the wikidata content being restricted based on sources provided. I will try to implement something like this in the next release. Any ideas of which particular statements are useful and should be imported more readily? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:28, 9 April 2026 (UTC) :::::::: I meant in [[d:Q138963952|the Wikidata item]] ''for'' AWE, but in general I think our articles should incorporate references early on, since even abstract content needs justification. [[d:help:sources#Language-independent general principles|This help page]] may be handy; '[[d:property:P3680|statement supported by]]' could be useful for linking to biographical articles in the manner "According to [source], [claim]" (obviously adjusted to the relevant language structures in each language for saying such things). — [[user:Arlo Barnes|Arlo Barnes]] ([[user talk:Arlo Barnes|talk]]) 20:42, 9 April 2026 (UTC) :::::::::@[[User:Arlo Barnes|Arlo Barnes]] oh that makes sense. But as for the wikidata sources, actually providing the sources is something that is trivially easy as far as accessing wikidata is concerned, but I am not sure how to give sources for claims in wikilambdas. Do you know how? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:44, 9 April 2026 (UTC) ::::::::::I don't. Currently the distinction between content and format is unclear to me. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:48, 9 April 2026 (UTC) :::::::::::@[[User:Arlo Barnes|Arlo Barnes]] what do you mean by content vs format? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 21:52, 9 April 2026 (UTC) ::::::::::::In the most 'abstract' sense, an article would have as irreducible parts semantic content only (from Wikidata), with syntax handled by the group of functions responsible for getting things looking right in a given target language. In practice, the overall structuring of the article largely defines or limits the syntactic structures of language produced. This is sensible for an encyclopedia which has a fairly conventional or constrained sort of prose. Of course, a web encyclopedia needs more than prose. Hence the functions for making links and formatting text (right now directly to HTML, bypassing wikitext). Although this is a MediaWiki installation, no article has had media content added to it yet, since the formatting functions that would enable that aren't in place. So I would say that content and formatting are entangled, currently. A reference could be considered either: the text that provides the sourcing of a statement, or the formatting that enables this semantic content to read as a reference, perhaps inline or as a footnote, end note, or marginal note. [[f:WF:type proposals#Representing abstract content]] has a couple RfCs about this. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 01:45, 10 April 2026 (UTC) :::::::::::::Yeah I am very confused about what the intention of Abstract Wikipedia is and how much it lines up with the reality. I had thought that the articles would be mostly directly generated from wikidata. :::::::::::::Only particular direction I see clearly is that I think we need articles on all of these pages [[d:Wikidata:List of articles that Abstract Wikipedia should have]] since they will likely bring a lot of traffic to the site and since they have a lot of information, people will have a lot of reason to come to this site and come up with new ways of expressing things on the pages. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:06, 10 April 2026 (UTC) ::::::::::::::I am however really liking section headers like the one here [[Q12539]] and I am going to include them in the next release [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:13, 10 April 2026 (UTC) :::::::::::::::Yes I think that adding sections to articles might be really the first part of the journey towards actually having somewhat readable articles. Although a lot of this is dependent on the article text actually rendering at all [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:21, 10 April 2026 (UTC) ::::::::::::::::Yeah I think I am getting the hang of things. Adding sections and paragraph breaks to the new versions. Denoted by ::::::::::::::::<nowiki>{{p}}</nowiki> ::::::::::::::::for a paragraph break ::::::::::::::::and ::::::::::::::::==QID== ::::::::::::::::for a subheading ::::::::::::::::All content is now generated within paragraphs, and the <nowiki>{{p}}</nowiki> splits the paragraphs up. Feeglgeef mentioned that the paragraphs are a significant accessibility feature, and the paragraphs are also easier to insert with the methods of the app. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:36, 10 April 2026 (UTC) :::::::::::::::::I am also implementing "it" to avoid repeating the name of the article constantly, and I am implementing citation preservation on certain things.Meanwhile also trying to fix the accessibility issue that was criticized. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 05:25, 10 April 2026 (UTC) ::::::::::::::::::New release is out [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 07:42, 10 April 2026 (UTC) ::::::::::::::::::I would suggest not to use [[d:Q6091500]] at the moment. In some languages, there might be multiple words for different uses of "it". If you are editing with only the English logic, it won't help build a multilingual wiki. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 17:42, 11 April 2026 (UTC) :::::::::::::::::::@[[User:Sun8908|Sun8908]] fair. I had thought it would be dropped in pro-drop languages but I do not think that was a reasonable assumption. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:47, 11 April 2026 (UTC) ::::::::::::::::::::I asked at the Monday meeting. Not sure if anything is being done about it though. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:15, 15 April 2026 (UTC) :Nice work. I for one don't care how you made the tool, the important part to me is how it works and if it helps me/us edit AW. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:23, 11 April 2026 (UTC) :[[File:AWE split paragraphs.png|thumb|Article on wheat]] {{ping|Immanuelle}} your tool is back at it again! I've asked you to test it before you use it to create a bunch of articles twice now. You, evidently, haven't listened! I understand you're probably acting in good faith, but you ''have'' to test your tool before you unleash it on the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:38, 18 April 2026 (UTC) ::No, I did listen. I am not sure what your objection is, but this looks like intended behaviour. I was asked to make every single sentence into its own paragraph to make it easier to debug maintaining accessibility. Previous the tool grouped many sentences into a single paragraph. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 02:49, 18 April 2026 (UTC) :::@[[User:Immanuelle|Immanuelle]]: You were asked to make each actual paragraph into a call of the "paragraph" function. You were not asked to make every individual sentence a paragraph. That is probably even less accessible than what we started with. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 03:06, 18 April 2026 (UTC) ::::The content itself needs refining. As it is, most articles have no value-added over the Wikidata triples plus labels; basically just slight readability improvements. We require complex structures sooner rather than later. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 03:08, 18 April 2026 (UTC) ::::I thought that the rule was that we put every single sentence into a paragraph of its own because text readers need a paragraph to read the text. We cannot debug things if there are multiple sentences within a paragraph, because these sentences go up to the top and make it so that the paragraph itself fails to render. ::::So this was specifically an accessibility concern for people who are visually impaired, with an accepted reduction in readability for people with regular vision so that it can also be debugged. ::::Like this: ::::"What we might try is wrapping each sentence as a paragraph, with occasional pairing of closely related sentences. That keeps failure isolated while preserving at least some natural flow. ::::We could consider also implementing a “sentence” or “content unit” function that simply calls “paragraph”, so we can later tell where the intended paragraphs are." [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:11, 18 April 2026 (UTC) :::::We need to import the quote template [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:12, 18 April 2026 (UTC) :Does anybody want any other changes to be made to this tool? Things are still relatively up in the air about what an optimum article even is, and as a result it kind of makes us limited in what we can do with it. I'm changing the way that the paragraphs work to fit what I now perceive as the consensus. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:11, 18 April 2026 (UTC) : I tried to run it on macOS 14.5, but it errored out when I clicked "Pull from Wikidata." It appears that this was because you hardcoded your Python path. <code>Error: Error invoking remote method 'generate-wikitext': Error: spawn C:/Users/Immanuelle/AppData/Local/Programs/Python/Python313/python.exe ENOENT</code> — [[user:JJPMaster|JJP]]_{[[user talk:JJPMaster|Mas]]_{[[special:contribs/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 11:56, 6 April 2026 (UTC) :: For the record, the solution is to go into <code>src/main.ts</code> and change the Python path to something other than <code>C:/Users/Immanuelle/...</code> — [[user:JJPMaster|JJP]]_{[[user talk:JJPMaster|Mas]]_{[[special:contribs/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 12:05, 6 April 2026 (UTC) : TYSM!! I did have to debug the code a little first to get it working, but this will be so helpful for me. — [[user:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[user talk:ChaoticVermillion|converse]], [[special:contribs/ChaoticVermillion|contribs]]) 11:59, 6 April 2026 (UTC) :: I am so sorry and I fixed it so the new release should avoid that problem in the future. — [[user:Immanuelle|Immanuelle]] ([[user talk:Immanuelle|talk]]) 17:55, 6 April 2026 (UTC) ::: @[[User:ChaoticVermillion|ChaoticVermillion]] btw there is an update that has a lot more functions and I am not sure if you are using it. The new one allows you to undo edits or restore revisions. Something that I cannot figure out how to do in regular Abstract Wikipedia. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:55, 8 April 2026 (UTC) == Wikiprojects == Are there wiki projects here? Can I just make some in this namespace? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 15:12, 10 April 2026 (UTC) :I don't see why not. It's a wiki, after all :). Please just don't flood the talkspace with templates that don't exist. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:51, 10 April 2026 (UTC) ::I've created a first Wikiproject ([[Abstract Wikipedia:WikiProject Core articles]]) and an explainer page ([[Abstract Wikipedia:WikiProject]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:11, 10 April 2026 (UTC) :::I made this one too [[Abstract Wikipedia:WikiProject Quality Prose]] [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:39, 10 April 2026 (UTC) ::{{ping|Feeglgeef}} Are WikiProjects for specific languages OK? Responsibility seems to be stretched between maintaining Wikidata labels and lexemes alongside creating and maintaining functions on Wikifunctions, so I'm unsure if Abstract Wikipedia would be considered a good place to coordinate these things. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:56, 20 April 2026 (UTC) :::There's no community consensus for or against, so, since this is a wiki, I don't see any reason why anyone would stop you :). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:46, 20 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #243 is out: Community proposals for capturing meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-10|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we report on three community proposals on syntactic approaches, we introduce a new Type (Complex numbers), we report on current hiccups on Abstract Wikipedia, we share more information about a presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1776101400 April 13, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 15:35, 10 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Numerous errors have been introduced, possibly due to the "AWE" tool == As [[User:Fram|Fram]] has [[w:Wikipedia:Village_pump_(WMF)#c-Fram-20260410163000-Fram-20260408131600|pointed out]] over on the English Wikipedia in his usual style, [[User:Immanuelle]] has been breaking pages such as [[Q711]] with edits such as [[Special:Diff/4383]]. I was able to [[Special:Diff/4415|fix this]] by changing "it" to Wikidata item reference in "defining role sentence". @[[User:Immanuelle|Immanuelle]]: Judging by your edit history, you have introduced this error to a lot of pages. Before continuing with your work to make the rest of the articles from your list, [[d:Wikidata:List of articles that Abstract Wikipedia should have]], I kindly ask you to fix the pages you've already made. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 17:16, 10 April 2026 (UTC) :This is, of course, what happens when you use a slop-machine to write code. See existing discussion on [[User talk:Immanuelle/Abstract Wikipedia Editor#Creates inaccessible content]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:19, 10 April 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]] I thought you wanted everything nested in the paragraph things. That's why I did that, following your request that you linked to. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:45, 10 April 2026 (UTC) :::I know. In the future, can you test whatever the slop-machine gives you ''on-wiki'' to ensure you don't mass-vandalize it again? Thank you! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:52, 10 April 2026 (UTC) ::::@[[User:Feeglgeef|Feeglgeef]] the problem I faced is that I do not know how to actually understand error messages on this wiki. When every page fails to render, it is very difficult to know if I introduced an error, or the program introduced an error. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:18, 10 April 2026 (UTC) :::::@[[User:Warudo|Warudo]] I guess my question for you would be how did you figure out that this was an error on the page? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:19, 10 April 2026 (UTC) ::::::That's a fair question. The way things are now you can't be sure if the error is because of technical issues with the site or a bad page. In this case it was rather easy though. The "dependency" parameter of [[f:Z28016]] expects a reference to a Wikidata item but you passed the string "it" to it. That is an obvious mistake so it was easy to tell that it's not a random error. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 19:23, 10 April 2026 (UTC) :::::::That makes sense. I will try to be a lot more careful with error detection in the future. Hopefully the technical issues with the site are fixed and I can see the content issues more soon [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:08, 10 April 2026 (UTC) ::::I suggest that “vandalize” is an inappropriate choice of word in this case. Whatever your feelings about the quality of the code or the care with which it is being deployed, I think you could manage to assume good faith on the part of a fellow contributor. Thank you. ::::At a technical level, there is an issue with simply bracketing multiple calls together to yield a paragraph, since a failure in any one call will lead to the loss of the whole paragraph. In [[:f:Wikifunctions:Status updates/2026-03-26]], the advice given was: ::::::“By the way, here’s one tip: currently, caching for Abstract Wikipedia happens on the level of the “fragment”. This means that by putting several sentences into a single paragraph, the paragraph as a whole is being run, may cause time-outs, and will be cached. Instead, if, for now, you put one sentence into each fragment, caching and evaluation can be more spread out and should allow for more content.” ::::[[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:00, 10 April 2026 (UTC) :::::@[[User:GrounderUK|GrounderUK]] would you suggest removing the paragraph by default behavior in the editor over this? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:50, 10 April 2026 (UTC) ::::::What we might try is wrapping each sentence as a paragraph, with occasional pairing of closely related sentences. That keeps failure isolated while preserving at least some natural flow. ::::::We could consider also implementing a “sentence” or “content unit” function that simply calls “paragraph”, so we can later tell where the intended paragraphs are. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 21:23, 10 April 2026 (UTC) :::::::This is not accessible for users with screen-readers, and thus not a viable work-around. Each paragraph must be in a paragraph tag. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:31, 10 April 2026 (UTC) ::::::::It’s sub-optimal, I agree, but every unit of meaning would be wrapped in p tags, which is more accessible than a series of bare fragments or failed function calls. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:07, 11 April 2026 (UTC) :::::::::If you do need to make inaccessible articles, please at least give them a category on the talk page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:21, 11 April 2026 (UTC) ::::::::::We’d need to agree an accessibility standard first, but I’m not planning on creating any articles until there are suitable functions available. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:36, 11 April 2026 (UTC) :::::::::::I agree. Accessibility standards need to be established and not just assumed. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:28, 11 April 2026 (UTC) :::::::::::I definitely do agree that we need accessibility standards, but this isn't really a nice-to-have that you debate about but rather the floor. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 00:27, 12 April 2026 (UTC) ::::::::::::I took this thread as consensus that we need to have every sentence as its own paragraph. Is that incorrect? Do people want me to change it back to one paragraph per paragraph break? I removed that one because it covered up errors. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:21, 18 April 2026 (UTC) :::::When someone "vandalizes" it is not necessarily intentional, see [[wikt:vandalise]]. I do understand that Immanuelle has good faith, but at the same time, the "deployment" caused tens of articles to be broken, and furthermore I don't suspect something this bad would have slipped through had a human carefully reviewed the code. When a contributor deploys a semi-automated tool and uses it to make edits at the rate {{ping|Immanuelle}} was at this rate, you are morally obligated to test it. This wasn't the first time the slop-machine that they used caused them to mess up tens of articles, and if Immanuelle doesn't exercise extreme care in the future, I don't suspect it will be the last. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 10 April 2026 (UTC) ::::::It was a silent error that was only discovered by chance. What kind of testing would you have done to avoid this? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:37, 10 April 2026 (UTC) ::::::@[[User:Feeglgeef|Feeglgeef]]": On Wikipedia, "[[:en:WP:VAND|Vandalism]]" is a technical term that means "editing (or other behavior) '''''deliberately''' intended to [[:en:Wikipedia:DE|obstruct or defeat]] the [[:en:Wikipedia:Five_pillars|project's purpose]]''". Accidental disruptive editing is not considered vandalism. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 22:52, 10 April 2026 (UTC) :::::::@[[User:Warudo|Warudo]] on the topic of this glitch. I think I have removed it from all pages that had it. Please tell me if there are more that you see. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:29, 10 April 2026 (UTC) ::::::::Thanks for cleaning up :) [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:29, 11 April 2026 (UTC) :::::::This isn't the English Wikipedia, or even a wikipedia at all, despite the domain. Unless a defined technical term related to Wikifunctions I'd consider words to have their natural language meaning. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:28, 11 April 2026 (UTC) ::::::::@[[User:Feeglgeef|Feeglgeef]]: Last time I checked, this was the Abstract ''Wikipedia''. But in any case, this is the definition provided in [[f:Wikifunctions:Vandalism|Wikifunctions]] as well as [[meta:meta:Vandalism|meta]]. Vandalism has to be deliberate. [[User:Warudo|Warudo]] ([[User talk:Warudo|talk]]) 08:50, 11 April 2026 (UTC) :::::::::It's not ''the'' Abstract Wikipedia like ''the'' English Wikipedia, but just Abstract Wikipedia. It isn't a Wikipedia in and of itself (as in, it's not supposed to be viewed by end readers), but rather a tool for Wikipedias. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:33, 11 April 2026 (UTC) ::::::::::It still has an independent editing community. Just because it draws from Wikidata and Wikifunctions doesn't mean content decisions aren't made here; it necessarily has to have some autonomy just like any language edition. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 19:18, 11 April 2026 (UTC) :::::::::“Deliberately” is also the first word of section 3.3 of our Code of Conduct, linked at the foot of every page. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:11, 11 April 2026 (UTC) :::::+1 Please assume good faith and keep it civil. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:27, 11 April 2026 (UTC) :@[[User:Warudo|Warudo]] will hold off on page creation [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:43, 10 April 2026 (UTC) :Just a note @[[User:Immanuelle|Immanuelle]], the project is a Beta version, so, in my opinion, it's not a good idea to flood it with a large number of [{{fullurl:Special:Contributions|target=Immanuelle&namespace=0&newOnly=1&limit=250&end=2026-04-10}} article stubs]. Additionally, the natural language functions are still limited.--[[User:Mdktb|Mdktb]] ([[User talk:Mdktb|talk]]) 18:58, 10 April 2026 (UTC) ::@[[User:Mdktb|Mdktb]] okay that is a good point. I think I was confused since I thought that we were more on the trying to get new users stage. I will stick to fixing up my errors and only making pages on things that I have a lot of stuff to say on. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:20, 10 April 2026 (UTC) :::@[[User:Mdktb|Mdktb]] and here is a wikiproject I made and tagged some pages with that is specifically related to developing more natural language [[Abstract Wikipedia:WikiProject Quality Prose]] [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 19:27, 10 April 2026 (UTC) ::Would you be willing to raise this in the project chat? I'm thinking we are in an experimentation state that will keep improving incrementally just like the first edition of Wikipedia did since January 15, 2001. Just like back then I don't think it's a good idea to arbitrarily limit good faith editing. We probably will have to revisit these articles later as more and better functions become available but that in itself is not a valid argument for refraining from edits. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:36, 11 April 2026 (UTC) :::Already here ;) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:05, 11 April 2026 (UTC) ::I agree with your stub-flooding comment, I don't think it's particularly useful to have a bunch of articles that say nothing. The concern right now should be testing. I expect that the way in which we write abstract articles will change drastically eventually, so writing hundreds of articles is not only a waste of time but a debt. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 11 April 2026 (UTC) :::We can always use [[Special:AncientPages]] to find them later on. :::My expectation is that things will change, but we’ll be able to change the articles. They aren’t set in stone. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 03:21, 18 April 2026 (UTC) :The error in question was that "it" ended up getting into the jsons as a string instead of the id for "it". This occurred due to an error with the program with function aliasing, functions and items can have aliases that are used to be human readable, and replaced with their codes during insertion. But apparently when you try to insert a nonexistent alias then it just inserts the text and there is no server side validation at all of edits. :My guess is that basically they do not have an api since they have no server side validation and were relying on solely client side, and did not anticipate someone building such a tool that accidentally bypassed client side validation through a cache injection which was motivated by UX purposes :I plan on attending the Monday volunteer meeting and asking about this issue. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:45, 10 April 2026 (UTC) ::> But apparently when you try to insert a nonexistent alias then it just inserts the text and there is no server side validation at all of edits. ::This sounds like a bug. Would you be willing to create a ticket in phab with details? [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:38, 11 April 2026 (UTC) :::The team has already declined (or indicated that they had no plans) to do validation in this form, so I don't think a new ticket would be ideal. Either way, this shouldn't affect anyone besides those using a headless browser (or anyone using good, human-reviewed code and a headless browser), so I don't think it would be a priority anyway. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:19, 11 April 2026 (UTC) ::::Not sure what you are talking about. At the meeting they did not seem to be opposed to doing server side validation. They just said that they had a bit of concerns about infrastructure that was stopping it as an immediate thing. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 20:14, 15 April 2026 (UTC) :::::The volunteer's corner? I unfortunately missed that, but it was more than a year ago that I believe they decided not to pursue it, so you're probably right. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:46, 16 April 2026 (UTC) :So I have resolved this issue, as I have resolved most of the issues that people brought up. The whole paragraph debate is something I am returning to the older version of. Does anybody want other changes to the way that it makes articles? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 18:09, 18 April 2026 (UTC) == Sandbox page == The previous discussion about bot-created pages does raise a question: is it possible to have sandbox pages here? As far as I can tell, one can only create pages in the main namespace, and it has to be one page per Wikidata item. So there's no good place to experiment. Or am I missing something? The only other thing I can think of is to write the whole abstract article (or a part of it) as a function with a composition implementation on Wikifunctions and then to call it from a user-space sandbox page here. That, however, doesn't actually seem to work: [[User:Amire80/sandbox|I've just tried to call a function from my user space]], and I just see "⏳ Function is being called…". That is possibly a bug that can be fixed (maybe [https://phabricator.wikimedia.org/T422299 T422299]?), but even if it's fixed, it doesn't look like the best user experience. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:48, 10 April 2026 (UTC) :[[phab:T421417]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:52, 10 April 2026 (UTC) ::For now [[Q3938]] can be used for test edits . [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 02:06, 11 April 2026 (UTC) :We have [[Q138864867]]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 23:30, 11 April 2026 (UTC) == I propose Q10693 for featured article == I think [[Q10693]] is the best article here. Can I propose it for [[Abstract Wikipedia:Featured article]] [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:24, 10 April 2026 (UTC) :We'd to come to a consensus on criteria first before we nominate anything. Anyway, the talk page of [[Abstract Wikipedia:Featured article]] would be a better place to decide this, not ''everything'' belongs on the project chat. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:36, 11 April 2026 (UTC) == REST API for editing? == Hi, does anyone know if there is a ticket in phab for a public API endpoint that allows editing of AW content? It would be very useful to improve tooling and content. [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 20:41, 11 April 2026 (UTC) :I don't believe so. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:03, 11 April 2026 (UTC) :I do not know why there isn't a REST API, but I had to [[Abstract Wikipedia:Project chat#I made a desktop app that helps with editing|specifically work around it with my editing tool]]. It will be very nice in the future to have a REST API. :I think that right now there isn't actually any server-side verification of whether an article is well-structured, and that might be the reason why there isn't a REST API yet. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 23:46, 11 April 2026 (UTC) ::What rest api are you talking about? Checkout [[Special:RestSandbox]]. [[User:Tanbiruzzaman|Tanbiruzzaman]] ([[User talk:Tanbiruzzaman|talk]]) 16:50, 12 April 2026 (UTC) :I would like to proudly announce that it can be done. See [[Special:Diff/6102]]. Here was my request: :<syntaxhighlight lang="json">{ "source": "{\"qid\":\"Q100000\",\"sections\":{\"Q8776414\":{\"index\":0,\"fragments\":[\"Z89\"]}}}", "title": "Q100000", "comment": "Hello from MediaWiki REST API", "content_model": "abstractwiki", "token": "[token]" } </syntaxhighlight> [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 04:43, 20 April 2026 (UTC) == Spaces between sentences == In abstract articles with two sentences or more, I usually see two spaces between the sentences. Why two? I usually write one space, and that's probably what most people do in English. I know that some people write two; I don't like it myself, but this practice does exist. But here, it raises a few more nuanced questions: # Where is it actually defined that there are supposed to be ''any'' spaces between the sentences? I might be wrong, but it probably comes from the extension code and not from the functions. # Can this be customized per language? I don't know all the rules for all the languages, but I strongly suspect that some languages use spaces between sentences differently, and no default is good for all the languages. I'd especially check if it's good for Thai, Burmese, Japanese, and Chinese. # When I examine the HTML code of the rendered sentences, each of them is a <code><nowiki><div></nowiki></code>. It's a bit odd—I'd expect <code><nowiki><span></nowiki></code> there. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 21:07, 14 April 2026 (UTC) :Can you give an example article, please? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:01, 15 April 2026 (UTC) ::[[Q833]], [[Q11361384]], and probably every other abstract article whose rendered English text has more than sentence. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 14:34, 15 April 2026 (UTC) :::No, not every single one (see [[Q333]]), but most of them. This has happened because Denny promoted separating sentences into individual fragments and Immanuel used an AI slop-machine to create an editing tool. Essentially, they're being treated as separate elements (like how one paragraph is different from a section heading), so the UI adds a space. This, of course, should not be done, because it breaks screen-readers and looks weird, but apparently everyone is just OK with it. Like a thousand articles have been created by the afforementioned slop-generated tool (because the person who oversaw the bot that created it seems to care more about quantity than quality), whereas I've only created three myself (because I care more about quality and shaping the direction of the wiki in preparation for when abstract content becomes actually viable). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 15 April 2026 (UTC) ::::If I understand correctly, [[Q333]] has one fragment, which is one function call, which in turn creates two sentences and joins them using a hardcoded space. If each sentence was created using a separate fragment, they would probably appear with two spaces in practice. Neither option is very good. ::::The mass creation of abstract articles using that tool is probably not really related to this. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:52, 15 April 2026 (UTC) :::::No, one of them is objectively wrong and one of them is correct. You're not ''supposed'' to split two sentences into two fragments. That's the point. The mass creation of articles using that tool ''is'' related, because it's responsible for the proliferation of articles that follow the wrong one. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:36, 15 April 2026 (UTC) ::::::Why not split sentences into fragments? I can easily imagine some functions that produce several sentences, but it's not universal. ::::::And why is it ''correct'' to join sentences using a hardcoded space? Joining sentences shouldn't be done using a hardcoded space, but with a generic "join sentences" function, which will be one space for many languages, but probably not for all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 17:55, 15 April 2026 (UTC) :::::::Yes, not having to hardcode is the eventual goal. Splitting sentences into fragments is bad because it adds extra spacing (this is a feature, and a good one!), because it's bad for screen-readers, and because it would be impossible to distinguish between paragraphs, the article would just be a collection of sentences. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:03, 15 April 2026 (UTC) ::::::::I still don't understand why splitting into fragments is bad. What is good about extra spacing? It looks like a bad feature, not a good one. It sounds like a rendering and presentation issue, not a logical issue. Fragments can be inline, and the inline ones should be <code><nowiki><span></nowiki></code>s, not <code><nowiki><div></nowiki></code>s. And there should also be an option for <code><nowiki><div></nowiki></code> fragments. And maybe some others. Forcing every fragment to be a <code><nowiki><div></nowiki></code> sounds like a bad feature. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:46, 15 April 2026 (UTC) :::::::::Again, the spacing is good because the correct reason to split is to create two separate paragraphs. Even if the spacing ''was'' removed, it would still not work for screen-readers, and blocking out blind people when the mission is to spread knowledge to neglected languages is incredibly ironic. I'm not sure how else I'm supposed to communicate this to you. It's like asking "why is magma so hot! I want to drink magma instead of water, but it's too hot and not refreshing!" [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:07, 15 April 2026 (UTC) ::::::::::Maybe I understand what a "fragment" is supposed to be differently. Where is defined what is it supposed to be? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 20:22, 15 April 2026 (UTC) == Archiving discussions on this page? == We're soon coming up to having a month old messages here, and considering the current length of it and size of the community, perhaps 30 days is a good limit for archiving them. Does anyone know how to get an archive bot running here? <span style="color:#EAA">♥</span>[[User:Ainali|Ainali]] <small>^{[[User talk:Ainali|discussion]]}_{[[Special:Contributions/Ainali|contributions]]}</small> 06:44, 16 April 2026 (UTC) :+1 [[User:So9q|So9q]] ([[User talk:So9q|talk]]) 09:55, 16 April 2026 (UTC) :+1 [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:41, 16 April 2026 (UTC) :+1. I think SpBot does archiving on Wikifunctions. Maybe it could be brought here as well? [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 14:18, 16 April 2026 (UTC) :+1 [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:24, 16 April 2026 (UTC) == Importing the q template == I really want the <nowiki>{{q}}</nowiki> template here imported from wikidata. It is very helpful with qids. Linking to here instead of wikidata. Might be able to be expanded for lexemes and wikifunctions too. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:26, 16 April 2026 (UTC) :I've copied it and its dependencies from Wikifunctions: see {{Q|1}} It may need some tweaking to work well here, because we also use QIDs. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:51, 17 April 2026 (UTC) ::Great! I think we need [[Template:Quote]] too [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 04:13, 18 April 2026 (UTC) == Caching issues (hopefully) fixed == Hey all, I know the caching issues have been a real pain for you. I've just now deployed what (I hope) is a fix that works for calls on Wikifunctions.org, fragments here, and embedded Wikifunctions calls. See for example [https://abstract.wikipedia.org/view/en/Q1344227 view/en/Q1344227] which should load fragments near-immediately for you (not need a retry or time out). You'll also see e.g. that https://test.wikipedia.org/wiki/Wikifunctions now has "stable" results, not just endless "please wait" comments. That said, please tell me where I'm wrong and you're having issues! Much better to hear now than assume it's fixed and start all over again tomorrow. I appreciate your feedback and patience over this; it has been very generous of you all. Our next work in this area is to make the cache much more scalable and resilient over time, so it's faster and more reliable for you, and cheaper for us to support. Thank you again. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:47, 16 April 2026 (UTC) :Thank you (and the rest of the team) for your efforts for this new wiki! We really appreciate it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:58, 16 April 2026 (UTC) :Wow this is great! Now we can do a lot more verification on whether created pages are working well! Gotta look over a bunch of pages. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 15:20, 16 April 2026 (UTC) ::Yes I tried to fix up a bunch of pages. Many of them actually render properly now. But I did need to change quite a few [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 17:36, 16 April 2026 (UTC) :::Yes, please give your attention to the quality of pages you've already created rather than expanding the quantity. For example, on [[Q153]] I notice that you used Z28016 a lot, but that "defining" should only be used when it is the only instance of that class in that location (which works fine for a capital city), but not e.g. for hydrogen being "the" part of ethanol. --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 04:43, 17 April 2026 (UTC) == Importing templates from wikipedias == I think it would be a good idea to set something up so that templates from wikipedia can be represented as wikifunctions. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 14:59, 16 April 2026 (UTC) :Already {{done}} on WF, see [[f:WF:MediaWiki parser functions]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:08, 16 April 2026 (UTC) == Idea for the project chat == I've been thinking of some ideas that we could implement related to the project chat. I'm not saying I endorse anything, just throwing out an idea. There's been a ''lot'' of activity on here, I'm not sure if this is going to be a permanent thing or if it's just because the wiki just started. If it maintains its activity, we might want to divide it up like the English Wikipedia does, perhaps into "Proposals", "Technical and Wikifunctions", and "Miscellaneous." [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:19, 16 April 2026 (UTC) :Simple english wikipedia has almost all discussion happen on its Project chat. I think we should only add nerw things once we really need more chats. Having everything here makes it easier for people to keep up with the news of abstract wikipedia. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 16:31, 16 April 2026 (UTC) ::The place to keep up with news for "abstract [sic] wikipedia [sic]" is the newsletter. I think that separating might actually make it easier to follow the specific discussion that you want, as you can choose which of the three to subscribe to. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:58, 16 April 2026 (UTC) ::We should at least have a talk page archiving bot, like [[:en:User:lowercase sigmabot III]]. [[User:EatingCarBatteries|EatingCarBatteries]] ([[User talk:EatingCarBatteries|talk]]) 20:18, 16 April 2026 (UTC) == What to do with Z26955 == There are a lot of articles with [[:f:Z26955|Z26955]] in them, since it has this obvious warning on it, what should we do with existing articles that have it? Just remove it on sight? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 15:33, 16 April 2026 (UTC) :We should only improve articles by fixing the problems, not by removing them. If you can replace a function by a better one, that’s great. Otherwise, please leave it for now so that we can see what needs fixing. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:04, 16 April 2026 (UTC) == Representing "part of" == How do I represent that something is part of another thing? I used to use the spo sentence without understanding that it did not work. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 16:30, 16 April 2026 (UTC) :I think [[f:Z32982]] can be used, with the role as [[d:Q1310239]]. [[User:ChaoticVermillion|<span style="color: orangered">Chaotic</span><span style="color: crimson">Vermillion</span>]] ([[User talk:ChaoticVermillion|converse]], [[Special:Contributions/ChaoticVermillion|contribs]]) 18:55, 16 April 2026 (UTC) :See Q307, perhaps :https://abstract.wikipedia.org/view/en/Q307 :Middle finger of Galileo's right hand is the part of of Galileo Galilei. [[Special:Contributions/&#126;2026-25174-74|&#126;2026-25174-74]] ([[User talk:&#126;2026-25174-74|talk]]) 03:07, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #244 is out: Milestones; Some major issues hopefully resolved == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we celebrate 4000 functions on Wikifunctions and 1000 abstract articles on Abstract Wikipedia, we announce that we should have fixed some major issues with the websites, we inform you on our latest outreach activities, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:22, 17 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == AceWiki: Abstract Wikipedia before Abstract Wikipedia? == For those of you not in the know, ACE is [[w:Attempto Controlled English|Attempto Controlled English]]. This is a special subset of English that, unlike regular English, is entirely grammatically unambiguous and is machine-readable. For example, the sentence "Every person has a cat" is ACE, as a computer could easily parse that into a logical structure of the form "for any person P, P has a cat." Well, I found a semantic wiki software called AceWiki, whose articles are written entirely in Attempto Controlled English (see [https://acewiki.petapico.org/acewikigeo/ AceWikiGEO]). The sentence structures seen in AceWiki articles (while I can't link directly to any article, the article on the United States of America, which can be found in the Index in the sidebar, is a good example) are quite similar to those in our existing abstract articles. Using a tool called [https://github.com/Attempto/ACE-in-GF ACE-in-GF], ACE text could be translated into any language. I've been thinking about the idea of a tool that allows an editor to write Attempto Controlled English text, and have that text turned into an abstract article. As an example: '''ACE''' -- "Every antelope is a mammal." &rarr; '''Abstract content''' -- [[f:Z26627|Classifying a class of nouns (Z26627)]]: [[d:Q25894|antelope (Q25894)]], [[d:Q7377|mammal (Q7377)]] This tool would not be optimized for mass article creation, since it would not include an option to generate articles directly from Wikidata, but I think it could be interesting to see how being able to write abstract articles in natural language might lower the barrier to contributing to this project. Thoughts? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 01:59, 20 April 2026 (UTC) :I'm not sure how we'd actually do the conversion step. If you'd be willing to attempt to make a prototype I'd love to look at it, but I'm skeptical. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:12, 21 April 2026 (UTC) == Help with the news section on main page == Hi all, I would like to have some help in importing [[:f:Template:Main page/News]] here and inserting it in the main page's module. Can someone help me to do it? [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 10:26, 20 April 2026 (UTC) :I believe [[Template:Main page/News]] is already set up and visible on the main page, unless you mean importing the history of the WF template over. [[User: Tenshi Hinanawi|Tenshi!]] ([[User talk: Tenshi Hinanawi|Talk page]]) 11:12, 20 April 2026 (UTC) ::Ah, that's great, thanks! [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 14:53, 20 April 2026 (UTC) == Layout guidelines? == One thing I'm noticing is that there are a ''lot'' of ways to do the same thing. I'd like to know which is preferred in the simple case of making single-sentence articles that just say what they are. Take [[Q503]] for example. If you look at the edit history of the article, you'll see it went through a few changes: * Initially, it was a [[f:Z14396|''string of monolingual text'']] call wrapped inside of a [[f:Z27868|''string to HTML fragment'']] call. The innermost function got the monolingual text returned from [[f:Z26095|''subject is kind of'']], converted it to a string, and then to a HTML fragment. * Afterwards the two topmost functions were removed until only the ''subject is kind of'' function call remained, and this was wrapped in a call to [[f:Z29749|''monolingual text as HTML with visible language tag'']]. * Finally the ''subject is kind of'' call was placed into a typed list provided as an argument to the [[f:Z32234|''join text-like objects into HTML fragment'']] call, which in turn was made into a proper paragraph rather than a standalone <code>&lt;div&gt;</code> as it was previously. None of these seem like a particularly bad way to approach things, and I have seem all of them in the wild; the first thing I tried I did so as it was the way the first article I stumbled upon chose to render its text. Since [[Abstract Wikipedia:Useful functions for article composition]] only goes over linguistic functions, and doesn't seem to provide any guidance on ''composition'' functions (i.e. building the HTML contents itself, as you have to do in the plain visual editor online), I thought I'd ask here if there is a preferred way to do things, and if it could perhaps be made clearer on the website if so. It is rather bothersome wanting to build e.g. a wikitable, and needing to peruse the available functions on Wikifunctions instead of having an easily-accessible way to see what is generally recommended for the particular circumstance. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:36, 20 April 2026 (UTC) :I'm partial to paragraph(join text-like objects into HTML fragment(your sentences)), as not using a paragraph tag is bad for those who use screen readers, and I designed join text-like objects to reduce function calls and therefore speed up the article processing step. The long-term problem with this method is that Japanese and Chinese both do not have spaces between sentences, so I plan to soon create a function that takes a list of text-like objects and then converts it into a paragraph under the correct style of each language. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:51, 20 April 2026 (UTC) ::That sounds good, I have grown more fond of that method as well. What you described would be great to have, I have been adding [[f:Z13128]] references inbetween each sentence to counteract the lack of spacing but something that would do this automatically for English while also obeying the sentence rules of other languages it renders in would be very ideal. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:33, 21 April 2026 (UTC) ::{{ping|Feeglgeef}} I noticed [[f:Z33068]]. I decided to hack up an implementation of it that aligns with what you said, I don't know if this is what your original intention for the function was and I apologize if I misconstrued it. At the moment, it just runs the ''join text-like objects'' function I mentioned earlier wrapped in a call to ''paragraph'', but adds spaces if the language is not Japanese or Chinese. I'm not sure if, in this scope, a lack of spaces is the only difference between how certain languages arrange their sentences. This also only accounts for the ZObjects for Chinese and Japanese specifically, I think some sort of switch statement or separate configuration object would be better suited for this—not to mention that there are separate natural language objects for the different scripts of Japanese, so those would have to be blanketed under Japanese when considering the language passed in (which I don't want to chain a bunch of ORs to do at the moment). For now, though, it seems to work fine. I added two different test cases and they both pass, and I have also utilized the function on [[Q241691]]. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 03:31, 23 April 2026 (UTC) :::Ah, thank you for implementing that, it looks good to me. I've created a persistent object for storing the languages that don't use spaces, [[f:Z33984]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:47, 23 April 2026 (UTC) == Wikidata problems == Sorry for posting two questions here in a row. I'll try to make this brief. On the bottom of [[Q247237]] is what ''should'' be a list of albums, but on my end it appears as just "''PLUS''" repeated fourteen times. This seems to occur any time I use [[f:Z13464]] on a list of Wikidata item references... is anyone else seeing this? I'm not sure what I could be doing wrong. Related to this, I wonder if I can avoid needing to explicitly state each of these items? I moved the list to a separately-defined object on Wikifunctions to avoid having to constantly transfer it between websites since I don't think the clipboard works cross-site. Ordinarily, if I were trying to get all Autechre studio albums, I would use Wikidata's SPARQL query feature to do this, by finding every entity whose [[wikidata:P31|P31]] is [[wikidata:Q482994|Q482994]] and whose [[wikidata:P50|P50]] is [[wikidata:Q247237|Q247237]]. This doesn't seem to be doable with Wikifunctions, though, or at least I'm not seeing it... so I don't know how I would do this automatically. We are making articles out of functions here, so I think it would be worthwhile if I tried to future-proof the list using this paradigm. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:30, 21 April 2026 (UTC) :On your first question, I've [[f:Z33903|tried to replicate this on WF]] and I cannot, which makes it difficult to solve. :We cannot currently reverse most WD statements, so your use case is not ''currently'' possible, but we are able to access the statements that are ''on'' an item. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:10, 21 April 2026 (UTC) ::I'm experiencing the issue again on [[f:Z33997]], it seems. Check the test results of the three-item test, "''programmer''" should not appear twice. I ran into a similar problem earlier in working on the implementation. For the two-item case, using a call to ''[[f:Z13397|get the nth element of a list]]'' on both items (index 1 and 2 respectively) returned the first item twice. I had to use a call to ''[[f:Z811|first element]]'' to fix it. ::Could this be a caching issue, perhaps? That seems likely, because I don't know why else this would be happening. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:16, 23 April 2026 (UTC) :::I am considering raising this issue on Phabricator if it hasn't been brought up already, this doesn't seem intentional. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 24 April 2026 (UTC) == What are we called? == If editors of Wikipedia are Wikipedians, editors of Wiktionary are Wiktionarians, editors of Wikivoyage are Wikivoyagers, and editors of Wikiversity are Wikiversitarians, what are we? Abstract Wikipedians? Abstracters? Abstractions? AWians? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 11:54, 24 April 2026 (UTC) :I don't like Abstractions and AWians. Abstracters sounds cool, it could be our "informal" term, while Abstract Wikipedians is our "formal" one. We could also apply it based on context (in the mainspace you're an abstracter, in the projectspace you're an abstract wikipedian), I'm not sure, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:12, 24 April 2026 (UTC) :I think an -or ending for 'abstractor' sounds cooler, personally. Abstract Wikipedians is boring but is the most straightforward option. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:50, 24 April 2026 (UTC) ::I did mean to spell it as "Abstractors." Sorry about the typo. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 18:55, 24 April 2026 (UTC) == Indexed by Google - deliberate? == https://www.google.com/search?q=site%3Aabstract.wikipedia.org%2Fwiki%2F Exposing Qid to Google looks like a mistake. Not likely to attract the public. Might adversely affect Wikipedia's Page rank or whatever? [[Special:Contributions/&#126;2026-25174-74|&#126;2026-25174-74]] ([[User talk:&#126;2026-25174-74|talk]]) 04:20, 25 April 2026 (UTC) :Indexing may already have stopped, after the 7th April - no recent pages found. [[Special:Contributions/&#126;2026-25174-74|&#126;2026-25174-74]] ([[User talk:&#126;2026-25174-74|talk]]) 04:26, 25 April 2026 (UTC) == I can't edit generated text on pages for some reason? == why is this? Thank you. [[User:BigKrow|BigKrow]] ([[User talk:BigKrow|talk]]) 07:58, 25 April 2026 (UTC) :You're not supposed to be able to edit generated text. You can edit the code that makes it, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:58, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 09:54, 25 April 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Why the editing API doesn't work == {{tracked|T423542}} Immanuelle wrongly stated that there is no REST API for editing. [[#REST API for editing?|There is]]. However, it does not work when called from software outside Abstract Wikipedia. That is because there is no way to grant a bot password or OAuth customer the permission to edit abstract articles (<code>wikilambda-abstract-edit</code>) and create them (<code>wikilambda-abstract-create</code>), since no grant on [[Special:ListGrants]] includes either. Should this be fixed? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[Q1270787|she]]/[[Q3437264|they]]) 01:57, 26 April 2026 (UTC) :Yes I think the rights should be added. I think the number of automated edits should be low at the moment as Abstract Wikipedia is still in an early phase and so far there is not much support for small languages and so many functions will maybe change to cover more languages. As automatic editing using a Bot Account requires an formal request it is no problem if the option exists. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:17, 26 April 2026 (UTC) :Sounds good to me. Could we add a bot section to [[Abstract Wikipedia:Requests for permissions]]? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:35, 5 May 2026 (UTC) ::[[Abstract_Wikipedia:Requests_for_permissions#Bot]] ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:56, 5 May 2026 (UTC) == Q884 == The page [[Q884]] has inaccurate statements about the head of government and the head of state of South Korea. Part of what it returns in English is "Lee Ju-ho is the head of government of South Korea.Park Geun-hye is the head of state of South Korea." However, neither Lee Ju-ho nor Park Geun-hye currently have their respective roles mentioned here. How should these statements be turned into ones using the past tense? [[User:Intolerable situation|Intolerable situation]] ([[User talk:Intolerable situation|talk]]) 14:44, 30 April 2026 (UTC) :not currently possible :((((( [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:46, 30 April 2026 (UTC) :Feeglgeef is correct, past tense sentence generation is something we are sorely lacking at the moment. If you look at [[f:WF:Type proposals#Representing abstract content|Wikifunctions' type proposals]] you can see some initiatives that could hopefully mitigate this. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:49, 1 May 2026 (UTC) == Abstract Wikipedia should use a different mw-wiki-logo than Wikipedia for Vector 2010 skin == {{Tracked|T424781}} Hello friends. I've been asked to start a community conversation about this. I'd like to propose that Abstract Wikipedia create its own logo, so that folks visiting this wiki don't get it mixed up with Wikipedia. Even though this project is under the Wikipedia domain, I think it's pretty unique and it'd make sense to make sure it doesn't get mixed up with enwiki or other Wikipedias by newbies googling for Wikipedia articles. Thoughts? Thanks. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:02, 1 May 2026 (UTC) :Isn't there already one? Are we talking about a logo in a different context? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:25, 1 May 2026 (UTC) ::Looks like this is just for the Vector 2010 skin. [https://abstract.wikipedia.org/wiki/Abstract_Wikipedia:Main_page?useskin=vector Example.] I'll edit this section and the ticket to clarify that. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 12:28, 1 May 2026 (UTC) :::Ah, thank you, I'd {{s}} this then. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:31, 1 May 2026 (UTC) :This has been raised before above in [[#Logo]], the same problem appears on Monobook. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 1 May 2026 (UTC) ::Would you support using [https://abstract.wikipedia.org/static/images/mobile/copyright/abstractwiki-wordmark.svg the Vector 2022 logo] on Vector 2010 and Monobook? That'd be a simple technical solution. [[User:Novem Linguae|Novem Linguae]] ([[User talk:Novem Linguae|talk]]) 14:02, 1 May 2026 (UTC) :::Yes, I see no issue with using that for the moment. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 1 May 2026 (UTC) == What would it take for AW to catch up to (English) Reasonator? Porting over functions? == The Wikidata tool [https://reasonator.toolforge.org Reasonator] already automatically creates several sentences in English describing human Wikidata items using [https://codeberg.org/magnusmanske/reasonator/commit/b506362c3c2e90b32de32708ec668eee49603cb0 auto_long_desc.js] under [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/LICENSE a GPL 2.0 free software license] without using any large language model or other AI. Abstract Wikipedia, on the other hand, requires [[Help:How to create an article/en|a several step process just to create a lead sentence]]. Does Resonator have functions in [https://codeberg.org/magnusmanske/reasonator/src/commit/a6ee9095c3accfb67845caf438ce83c98c19e38e/public_html/auto_long_desc.js#L406 the English section of auto_long_desc.js] that Wikifunctions doesn't have at the moment? Is that what's preventing Abstract Wikipedia from auto-generating substantial text (at least in English) based off of Wikidata like Resonator does? Below is [https://reasonator.toolforge.org/?q=Q1339&lang=en an example of what Resonator can generate from Wikidata] without needing human edits the way Abstract Wikipedia does. (Though I omitted some children for the sake of brevity.) <blockquote> '''Johann Sebastian Bach''' was a [https://reasonator.toolforge.org/?&q=696651 Saxe-Eisenach]-[https://reasonator.toolforge.org/?&q=12548 Holy Roman Empire]-[https://reasonator.toolforge.org/?&q=183 German] [https://reasonator.toolforge.org/?&q=36834 composer], [https://reasonator.toolforge.org/?&q=765778 organist], [https://reasonator.toolforge.org/?&q=5371902 harpsichordist], [https://reasonator.toolforge.org/?&q=1259917 violinist], [https://reasonator.toolforge.org/?&q=899758 violist], [https://reasonator.toolforge.org/?&q=158852 conductor], [https://reasonator.toolforge.org/?&q=1076502 choir director], [https://reasonator.toolforge.org/?&q=691031 concertmaster], [https://reasonator.toolforge.org/?&q=14915627 musicologist], [https://reasonator.toolforge.org/?&q=16145150 music educator], [https://reasonator.toolforge.org/?&q=214970 virtuoso], and [https://reasonator.toolforge.org/?&q=2251335 school teacher]. He was born on [https://reasonator.toolforge.org/?date=1685-03-21 March 21, 1685] in [https://reasonator.toolforge.org/?&q=7070 Eisenach] to [https://reasonator.toolforge.org/?&q=309470 Johann Ambrosius Bach] and [https://reasonator.toolforge.org/?&q=66671 Maria Elisabeth Lämmerhirt]. He studied at [https://reasonator.toolforge.org/?&q=1930161 St. Michael's School] until [https://reasonator.toolforge.org/?date=1702-04 April 1702]. His field of work included [https://reasonator.toolforge.org/?&q=8361 Baroque music] and [https://reasonator.toolforge.org/?&q=9730 classical music]. He was [https://reasonator.toolforge.org/?&q=215793 chapelmaster] from [https://reasonator.toolforge.org/?date=1717-12 December 1717] until [https://reasonator.toolforge.org/?date=1723-04 April 1723] and [https://reasonator.toolforge.org/?&q=641457 Thomaskantor] from [https://reasonator.toolforge.org/?date=1723 1723] until [https://reasonator.toolforge.org/?date=1750 1750]. He worked for [https://reasonator.toolforge.org/?&q=117540 Collegium Musicum], for [https://reasonator.toolforge.org/?&q=1230608 Saint Blaise], for [https://reasonator.toolforge.org/?&q=61689 Leopold, Prince of Anhalt-Köthen], for [https://reasonator.toolforge.org/?&q=61972 Johann Ernst III, Duke of Saxe-Weimar] from [https://reasonator.toolforge.org/?date=1703-01 January 1703] until [https://reasonator.toolforge.org/?date=1703-08 August 1703], for [https://reasonator.toolforge.org/?&q=699668 Thomasschule zu Leipzig], and for [https://reasonator.toolforge.org/?&q=798194 Bachkirche Arnstadt] from [https://reasonator.toolforge.org/?date=1703-08 August 1703] until [https://reasonator.toolforge.org/?date=1707 1707]. He married [https://reasonator.toolforge.org/?&q=57487 Maria Barbara Bach] on [https://reasonator.toolforge.org/?date=1707-10-17 October 17, 1707] (married until on [https://reasonator.toolforge.org/?date=1720-07-07 July 7, 1720] ) and [https://reasonator.toolforge.org/?&q=57212 Anna Magdalena Bach] on [https://reasonator.toolforge.org/?date=1721-12-03 December 3, 1721] (married until on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] ). His children include [https://reasonator.toolforge.org/?&q=15079141 Catharina Dorothea Bach], [https://reasonator.toolforge.org/?&q=107277 Wilhelm Friedemann Bach], […] He died of [https://reasonator.toolforge.org/?&q=12202 stroke] on [https://reasonator.toolforge.org/?date=1750-07-28 July 28, 1750] in [https://reasonator.toolforge.org/?&q=2079 Leipzig]. He was buried at [https://reasonator.toolforge.org/?&q=170402 St. Thomas Church]. </blockquote> [[User:Lovelano|Lovelano]] ([[User talk:Lovelano|talk]]) 18:41, 1 May 2026 (UTC) == Project scope == Might be a stupid question but what articles are/will be allowed on Abstract Wikipedia? How far is it meant to expand? The language Wikipedias have some differing policies, so might not be as simple as copying those. Personally I find the idea of creating an article for any and every Wikidata item really cool and a good ''baseline'' for what can have an article, but wouldn't ~120 million abstract articles become unwieldy? If the only requirement is that the article topic has a Wikidata item, then there are many interesting possibilities; one could write about individual dates, Wikidata test items, even Wikimedia disambiguation pages. Have not found where this is explained, if anywhere. This may be up to common sense, but trouble is, couldn't one create an encyclopedically meaningful article on just about anything? Pretty important policy not to have if it's undecided, though is not a problem at the moment. Just wondering. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 23:36, 1 May 2026 (UTC) :This isn't a stupid question and I don't think this is entirely settled. Have you seen [[Abstract Wikipedia:About]]? [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:57, 1 May 2026 (UTC) ::Ah, I forgot about that page. So it is meant to abstract information from existing Wikipedia articles? Makes sense, though it still raises the question of creating new articles. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:41, 2 May 2026 (UTC) :::At this juncture, I don't think anyone has in mind drafting anything new here as such: this is just responding to existing Wikidata items and the possibility of new Wikipedia articles drafted from them, using Wikifunctions. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:51, 2 May 2026 (UTC) :I don't think we ever get any article an existing wiki does not have. Even if abstract content creation gets as fast as reasonably possible, it will never beat out typing text, so we will never catch up with, say, enwiki or eswiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:10, 2 May 2026 (UTC) ::It's also a question of policy. There are topics about which things could be said, but which wouldn't meet the baseline notability or other criteria of the big monolingual wikis. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 20:22, 2 May 2026 (UTC) :::This is true, if we keep [[d:]]'s notability policy (which seems like the most natural one) then there are many subjects that we theoretically can talk about that don't meet the [[w:WP:GNG|GNG]] and similar guidelines. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:25, 2 May 2026 (UTC) == How many articles in how many languages are actually fully available without errors == This is a response to the call in [[:f:Wikifunctions:Status updates/2026-05-02]]. The most important thing to count is already listed there: '''How many articles in how many languages are actually fully available without errors?''' It should be not just a count, but a list: I want to see which articles are readable in which languages; which articles are readable in some languages, but not others (which ones?); which articles are not readable in any language; etc. An even more relevant, but much harder to measure thing is how many of those articles are actually more useful than not having an article at all. There is no article about Boston in many languages, but [[Q100]], which currently says "Boston is the capital of Massachusetts.Boston is the largest city of Massachusetts." is not significantly more useful than nothing at all even if it's fully rendered in another language in which there is no concrete article about it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:12, 2 May 2026 (UTC) :Perhaps this should have been on the talk page of that status update instead of the project chat? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:25, 2 May 2026 (UTC) ::The status update is about two projects and so I can understand if there are comments here. What do you think about creating a status update overview page with links to the status updates in Abstract Wikipedia to offer the possibility to discuss the status updates and especially things related to Abstract Wikipedia there. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 18:57, 4 May 2026 (UTC) :::I don't think that's necessary. You can just include your abstractwiki (as in, the live wiki, not the project) related comments on the page on [[f:]], or, if for some reason that's not possible, as a reply to the newsletter announcement here. The point is, the project chat is crowded enough with topics as it is, ideally it should be more focussed on general matters of discussion than close-ended enquiries about topics that have their own talk page. I find Amire80's use of a new == heading here to be improper. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:32, 4 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 12:21, 2 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == Spaces between sentences, another attempt == [[Abstract Wikipedia:Project chat#Extra spaces between sentences|A month ago]], @[[User:内存溢出的猫|内存溢出的猫]]<ref group="spaces3>According to Google Translate, it's pronounced "Nèicún yìchū de māo". Please correct me if it's wrong. When I write, I want to know how are things that I write pronounced aloud, and very unfortunately, I never learned to read Chinese characters, and even if I did, most English speakers probably didn't. Come to think of it, is there a function that ''reliably'' transliterates Chinese characters?</ref> That discussion doesn't seem to have yielded any fixes or meaningful discussions, at least not that I can see. [[Abstract Wikipedia:Project chat#Spaces between sentences|Two weeks ago]], I tried to bring up a similar topic, but that discussion somehow got derailed and also didn't yield anything useful. Now, the problem looks differently, but it's still a problem. When I look at [[Q10251]], for example, what I see is four sentences that ''appear'' with ''no'' spaces between them. Not one, not two—none at all. It looks like this: :Plasma is a fundamental state of matter.Plasma is a classical state of matter.A plasma is a gas.A plasma is a matter. Note that I emphasized ''appear'': When I see them rendered on the screen, they have no spaces between them. In the HTML, however, they are represented as four <code><nowiki><div></nowiki></code>s, and their inline positioning is handled by CSS. This means, for example, that if I copy and paste them, I don't get a long string with no spaces after full stops, but four sentences with a single line break after each full stop: <poem> Plasma is a fundamental state of matter. Plasma is a classical state of matter. A plasma is a gas. A plasma is a matter. </poem> This is not how it is supposed to be done. <code><nowiki><div></nowiki></code>s are supposed to be used for block elements and not hacked into appearing as if they are inline (also known as phrasing). Spaces between sentences are supposed to be real characters rather than HTML and CSS tricks, they may be different in different languages, and in some languages they may be nothing at all. I hope that the definition of the problem is clear. <references group="spaces3"></references> [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 12:49, 2 May 2026 (UTC) :Hi, have a look at it [[Special:PermanentLink/7132|now]]. Does this match your expectations? I think it's not rendering right now for whatever reason, but there are other examples of it being done this way that you can see: [[Q241691]]. The article renders properly in both English (spaces between sentences) and Japanese (no spaces at all). : :'''English:''' :<blockquote>Programmed Data Processor is a computer model series by Digital Equipment Corporation. PDP-8 is a Programmed Data Processor.</blockquote> :'''Japanese:''' :<blockquote>PDPシリーズはディジタル・イクイップメント・コーポレーションによるコンピュータ・モデル・シリーズである。PDP-8はPDPシリーズである。</blockquote> : :I have some, err, strong opinions about [[User:Immanuelle|Immanuelle]]'s 「Abstract Wikipedia Editor」 tool, which is the predominant cause for all of these very janky and poorly-laid-out articles that you see. This is not how an article ought to be written on Abstract Wikipedia, and I and other editors are aware of this. If you see these problems, please do fix them! The wiki will be all the better for it. : :In the absence of consensus on such things as these (and awaiting any official policy pages) I have written [[f:User:Theki/best practices]] on my Wikifunctions userpage. You are welcome to read it if you wish. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:20, 2 May 2026 (UTC) ::The output of [[Q241691]] looks OK to me in this regard. How was it done? ::[[Q10251]] gives me an error. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:10, 2 May 2026 (UTC) :::WikiLambda is doing WikiLambda things. This WASI time limit error happens intermittently on Abstract Wikipedia articles and it usually goes away after a short while. The only thing is that it doesn't really seem like purging these articles does anything to force the orchestrator to retry its evaluation so the article might not render that paragraph until someone comes in and pokes at it by editing it somehow. ::: :::The working article uses the [[f:Z33068|''paragraph from sentences'']] function to lay out its individual sentence content. This function automatically handles converting any and all text-like objects (strings, HTML fragments, and monolingual text) to a consistent form, so sentence fragments can all be supplied verbatim to its list input. When the function is putting the sentences together it defaults to using a single space to separate them, but first checks if the requested language is in the [[f:Z33984|''languages without spaces between sentences'']] list. If it is, it doesn't add spaces at all, and just concatenates the sentences normally. I hope this explanation makes sense. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:19, 2 May 2026 (UTC) ::::It makes some sense, but earlier, you suggested: "If you see these problems, please do fix them", and I'm not entirely sure how to do it. How would I fix it in [[Q100]], for example? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:41, 2 May 2026 (UTC) :::::In this case you would do the following: :::::# At the bottom, click the plus and then 「Add empty fragment」. :::::# Set the function to [[f:Z33068]], as mentioned earlier. :::::# Now go through each sentence fragment, find the innermost sentence-generation function, click on the three dots, and copy it. Do not copy the calls to [[f:Z29749]] or similar, these are not necessary. :::::# Go to the ''paragraph with sentences'' function call and add an element to the list. :::::# Click on the three dots next to the new element, and paste in the earlier sentence fragment. :::::# You can now delete the original fragment and repeat the process in the same list for the one after it. :::::&mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:46, 2 May 2026 (UTC) ::@[[User:Theki|Theki]] I intend on fixing it, I recently made an attempt but the suggested fixes made problems worse. Do you have any practical suggestions of how to structure the templates? I will try to implement them when I have more time. ::Also your name is very confusing, are you in the process of getting it changed wiki-wide? [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 22:36, 2 May 2026 (UTC) :::Um, are you referring to my signature not matching my wiki username? I have considered for a long time changing it from ''theki'', but I don't feel like putting in the effort when it seems to be perfectly ignorable for most people. The user 「''Rae''」 can't be usurped because they made, like, two or three articles on the Persian Wikipedia two decades ago or something, I don't know. If that weren't the case I would be User:Rae right now but after that failed to go through I just decided to stop bothering. Maybe at some point I'll come up with a username I'm happy with keeping for the foreseeable future but I have other concerns at the moment. :::Could you explain how your attempted fixes 「made problems worse」? Presently I side with Feeglgeef's sentiments and prefer to wait for abstract content to actually be feasible to make on a reasonably descriptive scale (see: the type proposals) before I go around making articles willy-nilly, which is what AWE has been doing—making a bunch of pretty low-quality articles on a massive scale when it probably ''really'' would have been better to, err, hold off on that. :::And I honestly know very little about the actual workings of your editor, I don't really use it nor am I familiar with its template syntax or whatever it may use, so I'm going to look over how it actually works and then get back to you on that. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 23:28, 2 May 2026 (UTC) ::::Using this [[f:Z33068]] made things worse [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:44, 3 May 2026 (UTC) :::::That did not go through correctly but I do not think we have a proper thing for it. [[User:Immanuelle|Immanuelle]] ([[User talk:Immanuelle|talk]]) 00:45, 3 May 2026 (UTC) ::::::What? Could you elaborate? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 01:00, 3 May 2026 (UTC) ::::::{{ping|Immanuelle}} I checked. Your issue is that your editor is not providing the article language to Z33068K2; that is, the ''paragraph from sentences'' function has a second argument, and your editor was omitting it. If you properly specify it, it will work. Please, next time, actually tell me what went wrong instead of going quiet and forcing me to look after it myself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 17:06, 4 May 2026 (UTC) == Most used fragments == [[:f:Wikifunctions:Status updates/2026-05-02|The latest status update]] lists the most used fragments: "[[:f:Z32123]] with 1452, followed by [[:f:Z27868]] with 736 and [[:f:Z29749]] with 650)". How was this calculated? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:44, 2 May 2026 (UTC) :Again, this should definitely have been on the talk page for that status update. This isn't the everything page, it should be used for discussion relating to the wiki. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:26, 2 May 2026 (UTC) ::It's not a question just about the status update, even if it was prompted by it. It's a question about Abstract Wikipedia that can be relevant beyond the status update. ::Stop policing how people use discussion pages without a particularly good reason. If you don't have an answer to the actual question, don't write anything. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:38, 2 May 2026 (UTC) :::I have to agree with Feeglgeef that this would be better raised on the status update's talk page itself. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:42, 2 May 2026 (UTC) :::I'm "policing" which discussion pages are being used for the same reason different discussion spaces exist in the first place. And your distinction between "just about" and "prompted by" is irrelevant. If I want to ask someone how they did something, I would ask them first, not go to a general discussion board. This is still the project ''chat'', not a Q&A zone. {{ping|DVrandecic (WMF)|p=,}} can you please answer the question? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:22, 2 May 2026 (UTC) :I have a local script that I have run on a local copy. Nothing more complicated than that. Could also be very wrong -- the script hasn't been peer-reviewed or anything. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 08:54, 4 May 2026 (UTC) ::Thanks, @[[User:DVrandecic (WMF)|DVrandecic (WMF)]]. Can you share the code, please? I'll be happy to review it. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:30, 4 May 2026 (UTC) ==Wiktionary integration== I was trying out a few functions recently, such as [https://www.wikifunctions.org/view/en/Z27243 the new superlative function], and I noticed that ''every adjective'' has to be a Wikidata item. For example, I couldn't type in the inputs "Bugatti Veyron", "fast", "Earth" because "fast" as an adjective is not a Wikidata item. This doesn't really make sense, given that Wiktionary already has the word for "fast" and its superlative form in many different languages. Would it be possible to integrate Wiktionary into the function, so the user can type an adjective or verb from Wiktionary instead of having to deal with Wikidata (which consists almost entirely of nouns)? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 16:49, 6 May 2026 (UTC) :No, sadly. I would try "speed" as the adjective, though, you have to use abstract qualities instead of concrete English terms. [[File:Wikifunctions Superlative speed example.png|thumb|Here's an example of the word being used.]] [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 6 May 2026 (UTC) :Wikidata has standard items as well as lexeme data, so if anything, we should try to integrate those. E.g. [[:d:Lexeme:L1029]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:48, 6 May 2026 (UTC) ::I tried this, and it gave "Bugatti Veyron is the speedest car on Earth", which is laughably bad. The problem is that Wikidata does not "know" what the superlative form is, while Wiktionary does. Speed is a fairly common descriptor, but what about less common adjectives which aren't on Wikidata? Will there need to be a bot to copy all of this information from Wiktionary? [[User:Somepinkdude|Somepinkdude]] ([[User talk:Somepinkdude|talk]]) 22:14, 6 May 2026 (UTC) :::I'm not suggesting that the functionality works <em>now</em>, but that we need to integrate the funcationality. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:17, 6 May 2026 (UTC) :::Well, no, the superlative form is chosen by [[f:Z12203]]. I think there's a bug with the English implementation that calls that function wrong. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 22:19, 6 May 2026 (UTC) :@[[User:Somepinkdude|Somepinkdude]] I did find the item {{Q|Q19807466}} which was linked to a concept database's entry for "fast"; I have at least linked it to the English lexeme "fast" and will try to add more links at a better hour. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 04:18, 7 May 2026 (UTC) == Showcase == I was wondering if there's a curated list of decent articles to learn by example here on Abstract Wikipedia? [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:02, 8 May 2026 (UTC) :Unfortunately not, and, honestly, I wouldn't recommend article creation at the moment, it's likely to need significant refactoring as the way we represent abstract content changes, but, I can point you to [[Q668]] as a reasonably good example at the moment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:39, 8 May 2026 (UTC) ::Thank you. "308 languages" blew my mind – well done! [[User:Fgnievinski|Fgnievinski]] ([[User talk:Fgnievinski|talk]]) 02:54, 8 May 2026 (UTC) :::308 is the number of ''concrete'' Wikipedias in which a manually-written article about India is available. :::The abstract article renders for me in English as "India is a country in Asia. India is a republic. New Delhi is the capital of India. India is the most populous country in world." Switching to another language to get rendered as an abstract article is done by typing the language's name in the box above the rendered text. I tried French, German, and Dutch, and got errors in all of them. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:12, 8 May 2026 (UTC) ::::So it goes. The paragraph has quite a lot of distinct sentence generation functions, all of which of course have to be implemented in the target language. This will be rounded out once we're able to more effectively generalize linguistic content. I view these functions as sort of patchy temporary solutions to the sentence generation problem while we figure out something more robust, which I hope is soon to come. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 04:15, 8 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the presentation about Abstract Wikipedia at WikiCon Australia, and we take a look at the latest software developments. Want to catch up with the previous updates? Check [[:f:Special:MyLanguage/Wikifunctions:Status updates|our archive]]! Also, we remind you that if you have questions or ideas to discuss, the next '''Volunteers' Corner''' will be held on '''[https://zonestamp.toolforge.org/1778520600 May 11, at 17:30 UTC]''' ([https://meet.google.com/xuy-njxh-rkw link to the meeting]). Enjoy the reading! -- [[User:Sannita (WMF)|User:Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 11:16, 8 May 2026 (UTC) <!-- Message sent by User:Sannita (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Wikifunctions_%26_Abstract_Wikipedia&oldid=30325620 --> == about the usage of Z33068 == The use of [[f:Z33068]] (en: paragraph from sentences) <s>always</s> most of the time results in the error "Reached time limit in orchestrator." So should it be used at all for now, temporarily? Or maybe there are already some tickets about this that I am not aware of? -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 18:23, 10 May 2026 (UTC) :It previously worked, so I'm hoping whatever the issue is will be fixed soon. The current state of the wiki makes [[m:Immediatism|immediatism]] an illogical philosophy to have at the moment, in my opinion. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:16, 10 May 2026 (UTC) ::This issue seems to no longer exist, you might need to clear the cache by making a dummy edit on affected articles. I implemented the function in Python (instead of composition), which has increased the speed by about 2000 ms. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 04:31, 11 May 2026 (UTC) :::Seems like working. Thank you. -- [[User:Asked42|Asked42]] ([[User talk:Asked42|talk]]) 19:06, 11 May 2026 (UTC) == Manual of Style == I've created a [[Abstract Wikipedia:Manual of Style|draft for a Manual of Style]]. Please feel free to comment on or make bold edits to the page. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 03:29, 11 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Wikifunctions Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:32, 11 May 2026 (UTC) jg4i39nqmsv8lme65km2n0xtawmqmg3 12 41 7606 5049 2026-05-11T20:40:00Z Alfa-ketosav 3488 7606 wikitext text/x-wiki <languages/> <translate> <!--T:1--> In Abstract Wikipedia you can only create articles about topics that already have a Wikidata item. If the topic does not already exist on Wikidata that you can tell by [[<tvar name="1">d:special:search</tvar>|search]], follow [[<tvar name="2">d:Special:MyLanguage/help:items#Creating a new item</tvar>|this help page]] to make a new item for it. == Steps == <!--T:2--> <!--T:3--> In order to create an article, you can go to [[<tvar name="1">Special:CreateAbstract</tvar>|Create a New Abstract Article]]. </translate> [[file:aw-tutorial-step-1.png|center|frameless|800px|<translate><!--T:4--> Select a topic</translate>]] <translate><!--T:5--> Type to select a topic, and click on create.</translate> [[file:aw-tutorial-step-2.png|center|frameless|800px|<translate><!--T:6--> Empty abstract article</translate>]] <translate><!--T:7--> You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</translate> [[file:aw-tutorial-step-3.png|center|frameless|800px|<translate><!--T:8--> Click on the plus sign to add a fragment.</translate>]] <translate><!--T:9--> Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</translate> [[file:aw-tutorial-step-4.png|center|frameless|800px|<translate><!--T:10--> An empty fragment</translate>]] <translate><!--T:11--> This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</translate> [[file:aw-tutorial-step-5.png|center|frameless|800px|<translate><!--T:12--> Function selector open</translate>]] <translate><!--T:13--> That will open the function selector.</translate> [[file:aw-tutorial-step-6.png|center|frameless|800px|<translate><!--T:14--> Selecting a function</translate>]] <translate><!--T:15--> We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</translate> [[file:aw-tutorial-step-7.png|center|frameless|800px|<translate><!--T:16--> Selected the "string to HTML fragment" function</translate>]] <translate><!--T:17--> We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function.</translate> [[file:aw-tutorial-step-8.png|center|frameless|800px|<translate><!--T:18--> Change the mode of the argument</translate>]] <translate><!--T:19--> In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</translate> [[file:aw-tutorial-step-9.png|center|frameless|800px|<translate><!--T:20--> Select the inner function</translate>]] <translate><!--T:21--> Here we can now select a function that returns a string.</translate> [[file:aw-tutorial-step-10.png|center|frameless|800px|<translate><!--T:22--> Choose a function returning a string</translate>]] <translate><!--T:23--> We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</translate> [[file:aw-tutorial-step-10.png|center|frameless|800px|<translate><!--T:24--> Arguments for article-less instantiating fragment function</translate>]] <translate><!--T:25--> Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</translate> [[file:aw-tutorial-step-11.png|center|frameless|800px|<translate><!--T:26--> Changing the mode on the "class" argument</translate>]] <translate><!--T:27--> We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</translate> [[file:aw-tutorial-step-12.png|center|frameless|800px|<translate><!--T:28--> Changed the mode of "class" to literal.</translate>]] <translate><!--T:29--> This gives us now a field to select a Wikidata item for the value of the "class" argument.</translate> [[file:aw-tutorial-step-13.png|center|frameless|800px|<translate><!--T:30--> Selecting city for the class argument</translate>]] <translate><!--T:31--> We select the "city" item for the class argument.</translate> [[file:aw-tutorial-step-14.png|center|frameless|800px|<translate><!--T:32--> The first sentence is created.</translate>]] <translate> <!--T:33--> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. == This is far too complicated! == <!--T:34--> <!--T:35--> Yes, agreed. <!--T:36--> There are two ways to make this easier:</translate> * <translate><!--T:37--> improve the UX</translate> * <translate><!--T:38--> improve the catalogue of functions</translate> <translate> <!--T:39--> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. <!--T:40--> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[<tvar name="1">Abstract Wikipedia:Suggested functions</tvar>|Suggested functions]]. == See also == <!--T:41--> </translate> * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] d7sswl631988jym3p11cl6cprrzm7h9 0 225 7561 3521 2026-05-11T17:52:21Z Feeglgeef 36 7561 abstractwiki text/plain { "qid": "Q30", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q3624078" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q4917" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q8142" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q61" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } kge2bz7rxzfhzfzxch3faogiw0wyj26 4 386 7574 7458 2026-05-11T19:45:28Z Dv103 1247 Updated the definitions of some fragments 7574 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Subject is instance of == Function [[f:Z26039|subject is instance of <small>(Z26039)</small>]] creates a sentence along the lines of {{xt|"X is a(n) [instance of] Y."}}. The "entity" field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The "class" field should be what the entity is being described as. === Example === : Entity: Q3870/Nairobi : Class: Q515/city : Language: English : Result: "Nairobi is a city" Note that this function converts the subject's name's first letter to uppercase in some languages, which may not always be appropriate. If needed, you can use [[f:Z32953]] to undo that behavior. == Subject is kind of == [[f:Z26095]] creates a sentence along the lines of {{xt|"A(n) X is a(n) [kind of] Y."}} The "entity" field should be the subject (typically, but not always, your article's subject). The "class" field should be what it is being described as. === Example === : Entity: Q89/apple : Class: Q3314483/fruit : Language: English : Result: "An apple is a fruit" == Defining role sentence == [[f:Z28016]] creates a sentence along the lines of {{xt|"X is the Y of Z."}} The "subject" field should be the subject (typically, but not always, your article's subject). The "role" field should be which role it serves to the dependency. The dependency should be what is related to the subject. === Example === : Subject: Q3870/Nairobi : Role: Q5119/Capital city : Dependency: Q114/Kenya : Language: English : Result: "Nairobi is the capital city of Kenya" == State location using entity and class == [[f:Z26570]] creates a sentence along the lines of {{xt|"X is a Y in Z."}} The "entity" field should be the subject (typically, but not always, your article's subject). The "class" field should be what is being described as. The "location" field should say where it is located. It should only be used for physical location. === Example === : Entity: Q3870/Nairobi : Class: Q515/city : Location: Q114/Kenya : Language: English : Result: "Nairobi is a city in Kenya" == Sentence-case section title from Wikidata label == [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. === Example === : Entity: Q309/history : Language: English : Result: "<nowiki><h2>History</h2></nowiki>" === Plural sentence-case title from Wikidata label === A plural version of [[f:Z32145]] is [[f:Z32839]]. '''Example''' : Entity: Q121769/reference : Language: English : Result: "<nowiki><h2>References</h2></nowiki>" == Join text-like objects into HTML fragments == [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. == Monolingual text as HTML fragment w/ auto-langcode == [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. == Collective role sentence == [[f:Z32326]] creates a sentence along the lines of {{xt|"Xs are Ys of Z."}} The "subject" field should be the subject (typically, but not always, your article's subject). The "role" field should be which role it serves to the dependency. The dependency should be what is related to the subject. === Example === : Subject: Q523/star : Role: Q31464082/source entity : Dependency: Q9128/light : Language: English : Result: "Stars are sources of light." ==Simple present collective sentence== [[f:Z32531]] creates a sentence along the lines of {{xt|"Xs verb Ys."}} The "subject" field should be the subject (typically, but not always, your article's subject). The "object" field should be the entity or concept that the subject is acting upon or relating to (i.e. what receives the action in the sentence). The "verb" field should describe the type of relationship or action between the subject and object, typically expressed as a base concept that can be converted into a natural verb. === Example === : Subject: Q523/star : Object: Q11426/metal : Verb: Q6014822/containment : Language: English : Result: "Stars contain metals." [[Category:Abstract Wikipedia administration|Useful Functions]] pxa3xrmmfomrli0l55136vdx91nbqm9 7575 7574 2026-05-11T19:46:12Z Dv103 1247 /* State location using entity and class */ 7575 wikitext text/x-wiki These functions are considered useful for composing abstract articles, in that they have typical use cases in composing them and have broad support across languages. For more discussion and tracking of fragment functions, see [[:f:Wikifunctions:Abstract Wikipedia/2025 fragment experiments]]. For a list of functions relating to natural language, see [[f:Wikifunctions:Catalogue/Natural language operations/Global language functions]]. == Subject is instance of == Function [[f:Z26039|subject is instance of <small>(Z26039)</small>]] creates a sentence along the lines of {{xt|"X is a(n) [instance of] Y."}}. The "entity" field (X in the formula above) should be the subject (typically, but not always, your abstract article's subject). The "class" field should be what the entity is being described as. === Example === : Entity: Q3870/Nairobi : Class: Q515/city : Language: English : Result: "Nairobi is a city" Note that this function converts the subject's name's first letter to uppercase in some languages, which may not always be appropriate. If needed, you can use [[f:Z32953]] to undo that behavior. == Subject is kind of == [[f:Z26095]] creates a sentence along the lines of {{xt|"A(n) X is a(n) [kind of] Y."}} The "entity" field should be the subject (typically, but not always, your article's subject). The "class" field should be what it is being described as. === Example === : Entity: Q89/apple : Class: Q3314483/fruit : Language: English : Result: "An apple is a fruit" == Defining role sentence == [[f:Z28016]] creates a sentence along the lines of {{xt|"X is the Y of Z."}} The "subject" field should be the subject (typically, but not always, your article's subject). The "role" field should be which role it serves to the dependency. The dependency should be what is related to the subject. === Example === : Subject: Q3870/Nairobi : Role: Q5119/Capital city : Dependency: Q114/Kenya : Language: English : Result: "Nairobi is the capital city of Kenya" == State location using entity and class == [[f:Z26570]] creates a sentence along the lines of {{xt|"X is a Y in Z."}} The "entity" field should be the subject (typically, but not always, your article's subject). The "class" field should be what is being described as. The "location" field should say where it is located. It should only be used for physical locations. === Example === : Entity: Q3870/Nairobi : Class: Q515/city : Location: Q114/Kenya : Language: English : Result: "Nairobi is a city in Kenya" == Sentence-case section title from Wikidata label == [[f:Z32145]] makes a capitalised section title (level 2 heading), using the label of the chosen Wikidata item from the appropriate language or a fallback. === Example === : Entity: Q309/history : Language: English : Result: "<nowiki><h2>History</h2></nowiki>" === Plural sentence-case title from Wikidata label === A plural version of [[f:Z32145]] is [[f:Z32839]]. '''Example''' : Entity: Q121769/reference : Language: English : Result: "<nowiki><h2>References</h2></nowiki>" == Join text-like objects into HTML fragments == [[f:Z32234]] combines certain text-like objects (currently [[f:Z6|strings]], [[f:Z11|monolingual texts]], and [[f:Z89|HTML fragments]]) into one big HTML fragment. It is useful for making multi-sentence paragraphs and avoiding the divide between the 3 types in linguistic functions. == Monolingual text as HTML fragment w/ auto-langcode == [[f:Z29749]] converts a monolingual text into an HTML fragment. If the target language is not matched, it prepends a language code. This helps to still display a fallback when the functions available to a language are incomplete. == Collective role sentence == [[f:Z32326]] creates a sentence along the lines of {{xt|"Xs are Ys of Z."}} The "subject" field should be the subject (typically, but not always, your article's subject). The "role" field should be which role it serves to the dependency. The dependency should be what is related to the subject. === Example === : Subject: Q523/star : Role: Q31464082/source entity : Dependency: Q9128/light : Language: English : Result: "Stars are sources of light." ==Simple present collective sentence== [[f:Z32531]] creates a sentence along the lines of {{xt|"Xs verb Ys."}} The "subject" field should be the subject (typically, but not always, your article's subject). The "object" field should be the entity or concept that the subject is acting upon or relating to (i.e. what receives the action in the sentence). The "verb" field should describe the type of relationship or action between the subject and object, typically expressed as a base concept that can be converted into a natural verb. === Example === : Subject: Q523/star : Object: Q11426/metal : Verb: Q6014822/containment : Language: English : Result: "Stars contain metals." [[Category:Abstract Wikipedia administration|Useful Functions]] qj350bhvnvb972khrwkekoqk2fs8jzm 4 452 7557 2992 2026-05-11T15:59:49Z Feeglgeef 36 7557 wikitext text/x-wiki A featured article is one of the best articles Abstract Wikipedia has, as determined by community review based on a list of criteria. == Criteria == : ''This section is currently empty.'' [[Category:Abstract Wikipedia administration]] mrwtj8n86hv0rkzp1fyvsgu0miu6np4 0 466 7570 7536 2026-05-11T19:21:07Z Asked42 130 7570 abstractwiki text/plain { "qid": "Q668", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z33068", "Z33068K1": [ "Z1", { "Z1K1": "Z7", "Z7K1": "Z26570", "Z26570K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26570K2": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z26570K3": { "Z1K1": "Z6091", "Z6091K1": "Q48" }, "Z26570K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q7270" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q987" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27243", "Z27243K1": { "Z1K1": "Z6091", "Z6091K1": "Q668" }, "Z27243K2": { "Z1K1": "Z6091", "Z6091K1": "Q138758272" }, "Z27243K3": { "Z1K1": "Z6091", "Z6091K1": "Q6256" }, "Z27243K4": { "Z1K1": "Z6091", "Z6091K1": "Q16502" }, "Z27243K5": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "" ], "Z33068K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z28445", "Z28445K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z30120K2": [ "Z6030", "Z6033", "Z6036" ], "Z30120K3": [ "Z60", { "Z1K1": "Z18", "Z18K1": "Z825K2" } ], "Z30120K4": [ "Z6092", { "Z1K1": "Z6092", "Z6092K1": "P1082" } ] }, "Z28445K2": { "Z1K1": "Z6092", "Z6092K1": "P1082" }, "Z28445K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } iuxrb2az9pdpwlvxl42ve8hikvokmry 0 736 7555 7158 2026-05-11T15:57:02Z YoshiRulz 640 7555 abstractwiki text/plain { "qid": "Q3938", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z31331", "Z31331K1": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q899627" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] }, { "Z1K1": "Z7", "Z7K1": "Z32496", "Z32496K1": { "Z1K1": "Z6091", "Z6091K1": "Q2667186" }, "Z32496K2": { "Z1K1": "Z6091", "Z6091K1": "Q34679" }, "Z32496K3": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z32496K4": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z32496K5": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32496K6": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32496K7": [ "Z6091" ], "Z32496K8": [ "Z6091" ], "Z32496K9": [ "Z6091" ], "Z32496K10": [ "Z6091" ], "Z32496K11": [ "Z6091" ], "Z32496K12": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32179", "Z32179K1": { "Z1K1": "Z7", "Z7K1": "Z873", "Z873K1": "Z27868", "Z873K2": { "Z1K1": "Z7", "Z7K1": "Z13464", "Z13464K1": "Z23753", "Z13464K2": "Z33839", "Z13464K3": "Z1002" } } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q7560" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q2500638" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q113388588" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27861", "Z27861K1": { "Z1K1": "Z7", "Z7K1": "Z19405", "Z19405K1": "div", "Z19405K2": [ "Z6", "style" ], "Z19405K3": [ "Z6", "color: red; background-color: blue; padding: 8px; display: flex;" ], "Z19405K4": "hehddkdjjfjc" } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Section Title: Q" }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Title Text. loremipsum" }, { "Z1K1": "Z7", "Z7K1": "Z31331", "Z31331K1": [ "Z89", { "Z1K1": "Z89", "Z89K1": "Listlist." }, { "Z1K1": "Z89", "Z89K1": "listlistlist" } ] }, { "Z1K1": "Z7", "Z7K1": "Z32878", "Z32878K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32878K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z802K2": { "Z1K1": "Z9", "Z9K1": "" }, "Z802K3": { "Z1K1": { "Z1K1": "Z9", "Z9K1": "" } } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Testing how abstract wikipedia works." }, { "Z1K1": "Z7", "Z7K1": "Z27861", "Z27861K1": "Z11853" } ] } } } 4n64itj5bknrx9im1ypofveely0owof 7556 7555 2026-05-11T15:58:03Z YoshiRulz 640 7556 abstractwiki text/plain { "qid": "Q3938", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z31331", "Z31331K1": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q899627" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] }, { "Z1K1": "Z7", "Z7K1": "Z32496", "Z32496K1": { "Z1K1": "Z6091", "Z6091K1": "Q2667186" }, "Z32496K2": { "Z1K1": "Z6091", "Z6091K1": "Q34679" }, "Z32496K3": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z32496K4": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z32496K5": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32496K6": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32496K7": [ "Z6091" ], "Z32496K8": [ "Z6091" ], "Z32496K9": [ "Z6091" ], "Z32496K10": [ "Z6091" ], "Z32496K11": [ "Z6091" ], "Z32496K12": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z32179", "Z32179K1": { "Z1K1": "Z7", "Z7K1": "Z873", "Z873K1": "Z27868", "Z873K2": { "Z1K1": "Z7", "Z7K1": "Z13464", "Z13464K1": "Z23753", "Z13464K2": "Z33839", "Z13464K3": "Z1002" } } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z6091", "Z6091K1": "Q7560" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q2500638" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q113388588" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z27861", "Z27861K1": { "Z1K1": "Z7", "Z7K1": "Z19405", "Z19405K1": "div", "Z19405K2": [ "Z6", "style" ], "Z19405K3": [ "Z6", "color: red; background-color: blue; padding: 8px; display: flex;" ], "Z19405K4": "hehddkdjjfjc" } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Section Title: Q" }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Title Text. loremipsum" }, { "Z1K1": "Z7", "Z7K1": "Z31331", "Z31331K1": [ "Z89", { "Z1K1": "Z89", "Z89K1": "Listlist." }, { "Z1K1": "Z89", "Z89K1": "listlistlist" } ] }, { "Z1K1": "Z7", "Z7K1": "Z32878", "Z32878K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z32878K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z802K2": { "Z1K1": "Z9", "Z9K1": "" }, "Z802K3": { "Z1K1": { "Z1K1": "Z9", "Z9K1": "" } } }, { "Z1K1": "Z7", "Z7K1": "Z31465", "Z31465K1": "Testing how abstract wikipedia works." }, { "Z1K1": "Z7", "Z7K1": "Z27861", "Z27861K1": "Z13128" } ] } } } b6v03o9v9jcmiq3txwcw9vq1k1hcz94 7563 7556 2026-05-11T18:38:15Z Feeglgeef 36 7563 abstractwiki text/plain { "qid": "Q3938", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27861", "Z27861K1": "<div class=\"ext-wikilambda-app-col e=<div class=\"ext-wikilambda-app-abstract-preview__section\"><!----> <div class=\"ext-wikilambda-app-abstract-preview-fragment\"><div class=\"ext-wikilambda-app-abstract-preview-fragment-error-wrapper\"><div class=\"cdx-message cdx-message--block cdx-message--error ext-wikilambda-app-abstract-preview-fragment-error\" role=\"alert\"><span class=\"cdx-icon cdx-icon--medium cdx-message__icon--vue\">﷽</span><div class=\"cdx-message__content\">Unable to render this fragment due to. <!----></div><!--v-if--><!--v-if--></div></div></div></div> <div class=\"ext-wikilambda-app-abstract-preview__highlight-layer\" aria-hidden=\"true\"></div></div></div> <!----></div></div>" } ] } } } dn9nmmtspxz67xngnn7rshtvel5zrrp 2 1117 7656 7523 2026-05-11T21:08:54Z HenkvD 1447 7656 wikitext text/x-wiki {| border="1" style="float: right; margin-left: 1em; margin-bottom: 0.5em; border: #99B3FF solid 1px; background: #F1F8F1; border-collapse: collapse;" | | colspan="10" | <div class="plainlinks"><center>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>Gebruiker:HenkvD op [[commons:Template talk:Sisterlinks|zusterprojecten]]:&nbsp;&nbsp;&nbsp;&nbsp;</b><small>[http://nl.wikipedia.org/w/index.php?title=Gebruiker:HenkvD/Categorie%C3%ABn&action=edit (bewerk)]</div></small></center> |- | valign="top" align="center" | [[Image:Wikipedia-logo.png|18px]]<br>Wikipedia<br>[[:de:Benutzer:HenkvD|de:]] [[:en:User:HenkvD|en:]] [[:fr:Utilisateur:HenkvD|fr:]] '''[[:nl:User:HenkvD|nl:]]''' | valign="top" align="center" | [[Image:Wiktionary-logo-en.png|17px]]<br>Wiktionary<br>[[:wikt:en:User:HenkvD|en:]]<br />[http://www.omegawiki.org/index.php/User:HenkvD ΩWiki] | valign="top" align="center" | [[Image:Wikinews-logo.png|35px]]<br>Wikinews<br>[[wikinews:User:HenkvD|en:]] [[:n:nl:User:HenkvD|nl:]]<br><div id="cat" class="plainlinks">[http://incubator.wikimedia.org/w/index.php?title=User:HenkvD nl: in incubator]</div> | valign="top" align="center" | [[Image:Wikiquote-logo.png|16px]]<br>Wikiquote<br>[[:q:en:User:HenkvD|en:]] |- | valign="top" align="center" | [[Image:Wikibooks-logo.png|18px]]<br>Wikibooks<br>[[:b:en:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikisource-logo.png|18px]]<br>Wikisource<br>[[:s:en:User:HenkvD|en:]] '''[[:s:nl:Gebruiker:HenkvD|nl:]]''' <div id="cat" class="plainlinks">[http://wikisource.org/wiki/User:HenkvD old]</div> | valign="top" align="center" | [[Image:Wikiversity-logo-en.svg|18px]]<br>Wikiversity<br>[[:de:v:User:HenkvD|de:]] [[:en:v:User:HenkvD|en:]] | valign="top" align="center" | [[Image:Wikimedia-logo.png|18px]]<br>[[:meta:User:HenkvD|Meta]]<br><div id="cat" class="plainlinks">[http://strategy.wikimedia.org/wiki/User:HenkvD Strategy]<br><div id="cat" class="plainlinks">'''[http://nl.wikimedia.org/wiki/Gebruiker:HenkvD nl:]''' </div> |- | valign="top" align="center" | [[Image:Wikivoyage-Logo-v3-icon.svg|16px]]<br>Wikivoyage<br>[[:en:voy:User:HenkvD|en:]] | valign="top" align="center" | [[File:Wikidata-logo.svg|19px|Wikidata]]<br><div class="plainlinks">[http://www.wikidata.org/wiki/User:HenkvD Wikidata]</div> | valign="top" align="center" | [[Image:Commons-logo.svg|14px]]<br>[[:Commons:User:HenkvD|Commons]] | valign="top" align="center" | [[File:Wikifunctions-logo.svg|14px]] [[File:Abstract-Wikipedia-wordmark.svg|42px]]<br>[[f:User:HenkvD|Wikifunctions]] <br>'''AbstractWiki''' |} My name is Henk, from [[Q55|the Netherlands]] ([[:nl:Gebruiker:HenkvD]]). I am interested in Abstract Wikipedia functionality and have general knowledge if the Dutch language (as native speaker). As most other the Dutch persons I have good knowledge of English and some of German and a bit of French and Romance languages.<br> I have an IT background, and try to understand the programming in Wikifunctions, but can't actually program them, except minor adjustments.<br> I will try to analyse Wikifunction, Wikidata, lexemes and add Wikifunction tests if needed. {{#babel:nl|en-3|de-1}} Examples * [[Q90]] - Paris is a city. Paris is the capital of France. * [[Q1033]] - Nigeria is the most populous country in Africa. * [[Q11750]] - list of sovereign states Some help pages are multilingual like [[Abstract Wikipedia:About]] First steps to get Abstract Wikipedia started: * Basic functions on Wikifunctions ** Use defaults if no lexeme and/or gender * link Wikidata Q-items to Lexemes * Gender of lexemes on Wikidata {{AbstractTestLemma}} 90cqst1o1ia0p9qzi7wyjm7odx5rdmj 5 2323 7544 7542 2026-05-11T12:02:53Z Arlo Barnes 953 /* self-description */ Reply 7544 wikitext text/x-wiki == self-description == There should be articles for Q-numbers linked to project space pages on this wiki, so that guidance documents have an abstract content equivalent. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:23, 18 April 2026 (UTC) :I support the idea morally, but I don't think AW is currently capable of handling meta-content yet. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:37, 18 April 2026 (UTC) ::Which is why I think it can be a goal to work toward, and a progressive test of capability. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 05:32, 19 April 2026 (UTC) :::[[special:allpages]] yields: :::* [[abstract:about]] — [[d:special:entitypage/Q4387616|about/introduction/welcome]] — [[Q4387616]] :::* [[abstract:administrators]] — [[d:special:entitypage/Q4039395|administrators]] — [[Q4039395]] :::* [[abstract:administrators' noticeboard]] — [[d:special:entitypage/Q4580256|administrators' noticeboard]] — [[Q4580256]] :::* <!--👂🐟-->[[abstract:Babel]] — [[d:special:entitypage/Q6476774|Babel]] — [[Q6476774]] :::* [[abstract:community portal]] — [[d:special:entitypage/Q4654925|community portal]] — [[Q4654925]] :::* [[abstract:featured article]] — [[d:special:entitypage/Q79763|featured article candidates]] — [[Q79763]] :::* [[abstract:frequently asked questions]] — [[d:special:entitypage/Q43120|FAQ]] — [[Q43120]] :::* [[abstract:list of policies and guidelines]] — [[d:special:entitypage/Q4656150|policies and guidelines]] — [[Q4656150]] :::* [[abstract:main page]] — [[d:special:entitypage/Q5296|main page]] — [[Q5296]] :::* [[abstract:project chat]] — [[d:special:entitypage/Q16503|village pump]] — [[Q16503]] :::* [[abstract:report a technical problem]] — [[d:special:entitypage/Q4582194|village pump (technical)]] — [[Q4582194]] :::* [[abstract:requests for deletion]] — [[d:special:entitypage/Q22897|deletion requests]] — [[Q22897]] :::* [[abstract:requests for permissions]] — [[d:special:entitypage/Q5453037|requests for permissions]] — [[Q5453037]] :::* [[abstract:suggested functions]] — [[d:special:entitypage/Q139175401|suggested functions]] — [[Q139175401]] :::* [[abstract:tools]] — [[d:special:entitypage/Q6584911|tools]] — [[Q6584911]] :::* [[abstract:useful functions for article composition]] — [[d:special:entitypage/Q139175483|useful functions for article composition]] — [[Q139175483]] :::* [[abstract:user groups]] — [[d:special:entitypage/Q4616064|user groups]] — [[Q4616064]] :::* [[abstract:WikiProject]] — [[d:special:entitypage/Q4234303|WikiProject]] — [[Q4234303]] :::* [[abstract:WikiProject Core articles]] — [[d:special:entitypage/Q43375360|vital articles]] — [[Q43375360]] :::* [[abstract:WikiProject Quality Prose]] — [[d:special:entitypage/Q115706234|proficiency]] — [[Q115706234]] :::as initial candidates in the project namespace. Of course, the articles would be about these pages in '''all''' of the linked wikis, technically; but the pages are 'about' their own subjects which is what would end up being conveyed anyway. There's also [[abstract:general disclaimer]] which is linked in the footer of every page but doesn't exist yet, so it could even be abstract-first on this wiki ([[wikidata:special:entitypage/Q4980478|general disclaimer]], [[Q4980478]]). In the 'help' namespace there's: :::* [[help:contents]] — [[d:special:entitypage/Q914807|contents]] — [[Q914807]] :::* [[help:how to create an article]] — [[d:special:entitypage/Q151637|editing]] — [[Q151637]] :::[[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:26, 19 April 2026 (UTC) ::::I'm not certain that's how we want to use [[d:Q14204246]] instances. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:23, 19 April 2026 (UTC) :::::To what use should they be put then, if any? [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:25, 19 April 2026 (UTC) ::::::To describe the topics encyclopedically? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:49, 11 May 2026 (UTC) :::::::But if we are going by Wikidata sitelinks, the topics are various project and help namespace pages on separate wikis, including this one — as a sort of [[Q1549285]]. Or maybe the line between stating what said pages are used for, and what their basic use ''is'' doesn't distinguish as much as I might initially think. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 12:02, 11 May 2026 (UTC) == Adding Item labels == I think it is helpful to see directly at the page the item labels of the proposed core articles and a link to the item. At my user page I tried it with {{Q|868}} and it did not show a label. In Wikifunctions I got the english Label. What do you think about adding the Template Q to the items to show a label. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:51, 19 April 2026 (UTC) :Seems like the Q template import at Abstract Wikipedia needs something else to actually retrieve the labels, then. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:50, 19 April 2026 (UTC) ::It is possible to add a language explicit in the template as an argument. This requires translating the Wikiproject page to enable people to view item labels in different languages. As Abstract Wikipedia has the goal of making content available in more languages I think this is an important point to be not too much english centered. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:35, 24 April 2026 (UTC) :::{{q|505335}} ([[Q505335]]) for example has a 'mul' label, it should display that by default. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 19:59, 24 April 2026 (UTC) : Being bold here: I added the template Q for the labels. It also links to wikidata and shows the (same) wikidate Q-id with a link). The links to wikidata and the Q-id are not needed, so maybe an alternitve template to only show the text of tha labes could fix that. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:59, 3 May 2026 (UTC) ::There is [[Template:Label]] for showing only the label of an item. So for example <code><nowiki>{{label|Q97|link=wikidata}}</nowiki></code>. So far the link is not leading to Wikidata as expected. So the templates needs improvement or same changes in Abstract Wikipedia. I link it is useful if the link leads to the Wikidata item. As it can help learning about what an item is about and to see what content is available in Wikidata so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:17, 4 May 2026 (UTC) :::<code><nowiki>{{label|Q97|link=-}}</nowiki></code> shows the label text only. So fro example :::# [[Q97]] {{label|Q97|link=-}} :::[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:16, 5 May 2026 (UTC) :::: Or <code><nowiki>[[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]</nowiki></code>) gives ::::# [[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]) :::: [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:27, 5 May 2026 (UTC) == Missing Templates in Abstract Wikipedia == I currently do not know if there are created templates on this platform to aid in article creation because I currently find creating or editing abstract Wikipedia more tedious instead of it making life simpler for both humans and machines since we were using Wikifunctions and Wikidata as our backbone. I contacted @[[User:Hogü-456|Hogü-456]] to see if he had answers but he said I could post it here for a wider discussion. Thinking out loud, I think if we could create standard templates for articles on various subjects, category and topics of interest, that will get us much closer to the overall dream of abstract Wikipedia and automatically pull in people with non-technical background. For example, the way the article for [https://abstract.wikipedia.org/view/en/Q408 Australia] could be used as yardstick for creating articles for a country and once a template is created for country level article creation, we could even have bots create these articles under the approval of human. There are some other beautiful articles already we could use it's structure to create a master template for any of the following: * Plants * Animals * Disease * Biographies * Countries * Wikimedia affiliates * ETC... Again, Wikidata powered infobox dubbed Databox makes articles beautiful and would make our articles great. [[User:Dnshitobu|Dnshitobu]] ([[User talk:Dnshitobu|talk]]) 08:25, 11 May 2026 (UTC) 5k0fjl2biuh7t2vpugtfcxt345svprq 7545 7544 2026-05-11T12:05:16Z Feeglgeef 36 /* Missing Templates in Abstract Wikipedia */ Reply 7545 wikitext text/x-wiki == self-description == There should be articles for Q-numbers linked to project space pages on this wiki, so that guidance documents have an abstract content equivalent. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:23, 18 April 2026 (UTC) :I support the idea morally, but I don't think AW is currently capable of handling meta-content yet. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:37, 18 April 2026 (UTC) ::Which is why I think it can be a goal to work toward, and a progressive test of capability. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 05:32, 19 April 2026 (UTC) :::[[special:allpages]] yields: :::* [[abstract:about]] — [[d:special:entitypage/Q4387616|about/introduction/welcome]] — [[Q4387616]] :::* [[abstract:administrators]] — [[d:special:entitypage/Q4039395|administrators]] — [[Q4039395]] :::* [[abstract:administrators' noticeboard]] — [[d:special:entitypage/Q4580256|administrators' noticeboard]] — [[Q4580256]] :::* <!--👂🐟-->[[abstract:Babel]] — [[d:special:entitypage/Q6476774|Babel]] — [[Q6476774]] :::* [[abstract:community portal]] — [[d:special:entitypage/Q4654925|community portal]] — [[Q4654925]] :::* [[abstract:featured article]] — [[d:special:entitypage/Q79763|featured article candidates]] — [[Q79763]] :::* [[abstract:frequently asked questions]] — [[d:special:entitypage/Q43120|FAQ]] — [[Q43120]] :::* [[abstract:list of policies and guidelines]] — [[d:special:entitypage/Q4656150|policies and guidelines]] — [[Q4656150]] :::* [[abstract:main page]] — [[d:special:entitypage/Q5296|main page]] — [[Q5296]] :::* [[abstract:project chat]] — [[d:special:entitypage/Q16503|village pump]] — [[Q16503]] :::* [[abstract:report a technical problem]] — [[d:special:entitypage/Q4582194|village pump (technical)]] — [[Q4582194]] :::* [[abstract:requests for deletion]] — [[d:special:entitypage/Q22897|deletion requests]] — [[Q22897]] :::* [[abstract:requests for permissions]] — [[d:special:entitypage/Q5453037|requests for permissions]] — [[Q5453037]] :::* [[abstract:suggested functions]] — [[d:special:entitypage/Q139175401|suggested functions]] — [[Q139175401]] :::* [[abstract:tools]] — [[d:special:entitypage/Q6584911|tools]] — [[Q6584911]] :::* [[abstract:useful functions for article composition]] — [[d:special:entitypage/Q139175483|useful functions for article composition]] — [[Q139175483]] :::* [[abstract:user groups]] — [[d:special:entitypage/Q4616064|user groups]] — [[Q4616064]] :::* [[abstract:WikiProject]] — [[d:special:entitypage/Q4234303|WikiProject]] — [[Q4234303]] :::* [[abstract:WikiProject Core articles]] — [[d:special:entitypage/Q43375360|vital articles]] — [[Q43375360]] :::* [[abstract:WikiProject Quality Prose]] — [[d:special:entitypage/Q115706234|proficiency]] — [[Q115706234]] :::as initial candidates in the project namespace. Of course, the articles would be about these pages in '''all''' of the linked wikis, technically; but the pages are 'about' their own subjects which is what would end up being conveyed anyway. There's also [[abstract:general disclaimer]] which is linked in the footer of every page but doesn't exist yet, so it could even be abstract-first on this wiki ([[wikidata:special:entitypage/Q4980478|general disclaimer]], [[Q4980478]]). In the 'help' namespace there's: :::* [[help:contents]] — [[d:special:entitypage/Q914807|contents]] — [[Q914807]] :::* [[help:how to create an article]] — [[d:special:entitypage/Q151637|editing]] — [[Q151637]] :::[[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:26, 19 April 2026 (UTC) ::::I'm not certain that's how we want to use [[d:Q14204246]] instances. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:23, 19 April 2026 (UTC) :::::To what use should they be put then, if any? [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:25, 19 April 2026 (UTC) ::::::To describe the topics encyclopedically? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:49, 11 May 2026 (UTC) :::::::But if we are going by Wikidata sitelinks, the topics are various project and help namespace pages on separate wikis, including this one — as a sort of [[Q1549285]]. Or maybe the line between stating what said pages are used for, and what their basic use ''is'' doesn't distinguish as much as I might initially think. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 12:02, 11 May 2026 (UTC) == Adding Item labels == I think it is helpful to see directly at the page the item labels of the proposed core articles and a link to the item. At my user page I tried it with {{Q|868}} and it did not show a label. In Wikifunctions I got the english Label. What do you think about adding the Template Q to the items to show a label. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:51, 19 April 2026 (UTC) :Seems like the Q template import at Abstract Wikipedia needs something else to actually retrieve the labels, then. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:50, 19 April 2026 (UTC) ::It is possible to add a language explicit in the template as an argument. This requires translating the Wikiproject page to enable people to view item labels in different languages. As Abstract Wikipedia has the goal of making content available in more languages I think this is an important point to be not too much english centered. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:35, 24 April 2026 (UTC) :::{{q|505335}} ([[Q505335]]) for example has a 'mul' label, it should display that by default. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 19:59, 24 April 2026 (UTC) : Being bold here: I added the template Q for the labels. It also links to wikidata and shows the (same) wikidate Q-id with a link). The links to wikidata and the Q-id are not needed, so maybe an alternitve template to only show the text of tha labes could fix that. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:59, 3 May 2026 (UTC) ::There is [[Template:Label]] for showing only the label of an item. So for example <code><nowiki>{{label|Q97|link=wikidata}}</nowiki></code>. So far the link is not leading to Wikidata as expected. So the templates needs improvement or same changes in Abstract Wikipedia. I link it is useful if the link leads to the Wikidata item. As it can help learning about what an item is about and to see what content is available in Wikidata so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:17, 4 May 2026 (UTC) :::<code><nowiki>{{label|Q97|link=-}}</nowiki></code> shows the label text only. So fro example :::# [[Q97]] {{label|Q97|link=-}} :::[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:16, 5 May 2026 (UTC) :::: Or <code><nowiki>[[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]</nowiki></code>) gives ::::# [[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]) :::: [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:27, 5 May 2026 (UTC) == Missing Templates in Abstract Wikipedia == I currently do not know if there are created templates on this platform to aid in article creation because I currently find creating or editing abstract Wikipedia more tedious instead of it making life simpler for both humans and machines since we were using Wikifunctions and Wikidata as our backbone. I contacted @[[User:Hogü-456|Hogü-456]] to see if he had answers but he said I could post it here for a wider discussion. Thinking out loud, I think if we could create standard templates for articles on various subjects, category and topics of interest, that will get us much closer to the overall dream of abstract Wikipedia and automatically pull in people with non-technical background. For example, the way the article for [https://abstract.wikipedia.org/view/en/Q408 Australia] could be used as yardstick for creating articles for a country and once a template is created for country level article creation, we could even have bots create these articles under the approval of human. There are some other beautiful articles already we could use it's structure to create a master template for any of the following: * Plants * Animals * Disease * Biographies * Countries * Wikimedia affiliates * ETC... Again, Wikidata powered infobox dubbed Databox makes articles beautiful and would make our articles great. [[User:Dnshitobu|Dnshitobu]] ([[User talk:Dnshitobu|talk]]) 08:25, 11 May 2026 (UTC) :Of course. I think [[Q49613|year intros]] are also somewhat inspiring, they don't create ''great'' content, but it's somewhat useful. Each "template article" (which we might require to obtain featured status) might have some of its own functions created for it that will need to be made multilingual. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:05, 11 May 2026 (UTC) f8qyesrwvas1796a38b2t4yqrumlu7e 7553 7545 2026-05-11T15:47:25Z HenkvD 1447 /* Missing Templates in Abstract Wikipedia */ 7553 wikitext text/x-wiki == self-description == There should be articles for Q-numbers linked to project space pages on this wiki, so that guidance documents have an abstract content equivalent. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:23, 18 April 2026 (UTC) :I support the idea morally, but I don't think AW is currently capable of handling meta-content yet. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:37, 18 April 2026 (UTC) ::Which is why I think it can be a goal to work toward, and a progressive test of capability. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 05:32, 19 April 2026 (UTC) :::[[special:allpages]] yields: :::* [[abstract:about]] — [[d:special:entitypage/Q4387616|about/introduction/welcome]] — [[Q4387616]] :::* [[abstract:administrators]] — [[d:special:entitypage/Q4039395|administrators]] — [[Q4039395]] :::* [[abstract:administrators' noticeboard]] — [[d:special:entitypage/Q4580256|administrators' noticeboard]] — [[Q4580256]] :::* <!--👂🐟-->[[abstract:Babel]] — [[d:special:entitypage/Q6476774|Babel]] — [[Q6476774]] :::* [[abstract:community portal]] — [[d:special:entitypage/Q4654925|community portal]] — [[Q4654925]] :::* [[abstract:featured article]] — [[d:special:entitypage/Q79763|featured article candidates]] — [[Q79763]] :::* [[abstract:frequently asked questions]] — [[d:special:entitypage/Q43120|FAQ]] — [[Q43120]] :::* [[abstract:list of policies and guidelines]] — [[d:special:entitypage/Q4656150|policies and guidelines]] — [[Q4656150]] :::* [[abstract:main page]] — [[d:special:entitypage/Q5296|main page]] — [[Q5296]] :::* [[abstract:project chat]] — [[d:special:entitypage/Q16503|village pump]] — [[Q16503]] :::* [[abstract:report a technical problem]] — [[d:special:entitypage/Q4582194|village pump (technical)]] — [[Q4582194]] :::* [[abstract:requests for deletion]] — [[d:special:entitypage/Q22897|deletion requests]] — [[Q22897]] :::* [[abstract:requests for permissions]] — [[d:special:entitypage/Q5453037|requests for permissions]] — [[Q5453037]] :::* [[abstract:suggested functions]] — [[d:special:entitypage/Q139175401|suggested functions]] — [[Q139175401]] :::* [[abstract:tools]] — [[d:special:entitypage/Q6584911|tools]] — [[Q6584911]] :::* [[abstract:useful functions for article composition]] — [[d:special:entitypage/Q139175483|useful functions for article composition]] — [[Q139175483]] :::* [[abstract:user groups]] — [[d:special:entitypage/Q4616064|user groups]] — [[Q4616064]] :::* [[abstract:WikiProject]] — [[d:special:entitypage/Q4234303|WikiProject]] — [[Q4234303]] :::* [[abstract:WikiProject Core articles]] — [[d:special:entitypage/Q43375360|vital articles]] — [[Q43375360]] :::* [[abstract:WikiProject Quality Prose]] — [[d:special:entitypage/Q115706234|proficiency]] — [[Q115706234]] :::as initial candidates in the project namespace. Of course, the articles would be about these pages in '''all''' of the linked wikis, technically; but the pages are 'about' their own subjects which is what would end up being conveyed anyway. There's also [[abstract:general disclaimer]] which is linked in the footer of every page but doesn't exist yet, so it could even be abstract-first on this wiki ([[wikidata:special:entitypage/Q4980478|general disclaimer]], [[Q4980478]]). In the 'help' namespace there's: :::* [[help:contents]] — [[d:special:entitypage/Q914807|contents]] — [[Q914807]] :::* [[help:how to create an article]] — [[d:special:entitypage/Q151637|editing]] — [[Q151637]] :::[[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:26, 19 April 2026 (UTC) ::::I'm not certain that's how we want to use [[d:Q14204246]] instances. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:23, 19 April 2026 (UTC) :::::To what use should they be put then, if any? [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:25, 19 April 2026 (UTC) ::::::To describe the topics encyclopedically? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:49, 11 May 2026 (UTC) :::::::But if we are going by Wikidata sitelinks, the topics are various project and help namespace pages on separate wikis, including this one — as a sort of [[Q1549285]]. Or maybe the line between stating what said pages are used for, and what their basic use ''is'' doesn't distinguish as much as I might initially think. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 12:02, 11 May 2026 (UTC) == Adding Item labels == I think it is helpful to see directly at the page the item labels of the proposed core articles and a link to the item. At my user page I tried it with {{Q|868}} and it did not show a label. In Wikifunctions I got the english Label. What do you think about adding the Template Q to the items to show a label. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:51, 19 April 2026 (UTC) :Seems like the Q template import at Abstract Wikipedia needs something else to actually retrieve the labels, then. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:50, 19 April 2026 (UTC) ::It is possible to add a language explicit in the template as an argument. This requires translating the Wikiproject page to enable people to view item labels in different languages. As Abstract Wikipedia has the goal of making content available in more languages I think this is an important point to be not too much english centered. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:35, 24 April 2026 (UTC) :::{{q|505335}} ([[Q505335]]) for example has a 'mul' label, it should display that by default. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 19:59, 24 April 2026 (UTC) : Being bold here: I added the template Q for the labels. It also links to wikidata and shows the (same) wikidate Q-id with a link). The links to wikidata and the Q-id are not needed, so maybe an alternitve template to only show the text of tha labes could fix that. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:59, 3 May 2026 (UTC) ::There is [[Template:Label]] for showing only the label of an item. So for example <code><nowiki>{{label|Q97|link=wikidata}}</nowiki></code>. So far the link is not leading to Wikidata as expected. So the templates needs improvement or same changes in Abstract Wikipedia. I link it is useful if the link leads to the Wikidata item. As it can help learning about what an item is about and to see what content is available in Wikidata so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:17, 4 May 2026 (UTC) :::<code><nowiki>{{label|Q97|link=-}}</nowiki></code> shows the label text only. So fro example :::# [[Q97]] {{label|Q97|link=-}} :::[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:16, 5 May 2026 (UTC) :::: Or <code><nowiki>[[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]</nowiki></code>) gives ::::# [[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]) :::: [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:27, 5 May 2026 (UTC) == Missing Templates in Abstract Wikipedia == I currently do not know if there are created templates on this platform to aid in article creation because I currently find creating or editing abstract Wikipedia more tedious instead of it making life simpler for both humans and machines since we were using Wikifunctions and Wikidata as our backbone. I contacted @[[User:Hogü-456|Hogü-456]] to see if he had answers but he said I could post it here for a wider discussion. Thinking out loud, I think if we could create standard templates for articles on various subjects, category and topics of interest, that will get us much closer to the overall dream of abstract Wikipedia and automatically pull in people with non-technical background. For example, the way the article for [https://abstract.wikipedia.org/view/en/Q408 Australia] could be used as yardstick for creating articles for a country and once a template is created for country level article creation, we could even have bots create these articles under the approval of human. There are some other beautiful articles already we could use it's structure to create a master template for any of the following: * Plants * Animals * Disease * Biographies * Countries * Wikimedia affiliates * ETC... Again, Wikidata powered infobox dubbed Databox makes articles beautiful and would make our articles great. [[User:Dnshitobu|Dnshitobu]] ([[User talk:Dnshitobu|talk]]) 08:25, 11 May 2026 (UTC) :Of course. I think [[Q49613|year intros]] are also somewhat inspiring, they don't create ''great'' content, but it's somewhat useful. Each "template article" (which we might require to obtain featured status) might have some of its own functions created for it that will need to be made multilingual. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:05, 11 May 2026 (UTC) :: Question: Would it be possible to add infoboxes to Abstract Wikipedia articles? Infoboxes generated fully from Wikidata will provide a wealth of data, like template:Wikidata Infobox on Commons. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:46, 11 May 2026 (UTC) 38eajuhl2zpz38abldd5as0kgszaz8e 7554 7553 2026-05-11T15:51:14Z Feeglgeef 36 /* Missing Templates in Abstract Wikipedia */ Reply 7554 wikitext text/x-wiki == self-description == There should be articles for Q-numbers linked to project space pages on this wiki, so that guidance documents have an abstract content equivalent. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:23, 18 April 2026 (UTC) :I support the idea morally, but I don't think AW is currently capable of handling meta-content yet. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 23:37, 18 April 2026 (UTC) ::Which is why I think it can be a goal to work toward, and a progressive test of capability. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 05:32, 19 April 2026 (UTC) :::[[special:allpages]] yields: :::* [[abstract:about]] — [[d:special:entitypage/Q4387616|about/introduction/welcome]] — [[Q4387616]] :::* [[abstract:administrators]] — [[d:special:entitypage/Q4039395|administrators]] — [[Q4039395]] :::* [[abstract:administrators' noticeboard]] — [[d:special:entitypage/Q4580256|administrators' noticeboard]] — [[Q4580256]] :::* <!--👂🐟-->[[abstract:Babel]] — [[d:special:entitypage/Q6476774|Babel]] — [[Q6476774]] :::* [[abstract:community portal]] — [[d:special:entitypage/Q4654925|community portal]] — [[Q4654925]] :::* [[abstract:featured article]] — [[d:special:entitypage/Q79763|featured article candidates]] — [[Q79763]] :::* [[abstract:frequently asked questions]] — [[d:special:entitypage/Q43120|FAQ]] — [[Q43120]] :::* [[abstract:list of policies and guidelines]] — [[d:special:entitypage/Q4656150|policies and guidelines]] — [[Q4656150]] :::* [[abstract:main page]] — [[d:special:entitypage/Q5296|main page]] — [[Q5296]] :::* [[abstract:project chat]] — [[d:special:entitypage/Q16503|village pump]] — [[Q16503]] :::* [[abstract:report a technical problem]] — [[d:special:entitypage/Q4582194|village pump (technical)]] — [[Q4582194]] :::* [[abstract:requests for deletion]] — [[d:special:entitypage/Q22897|deletion requests]] — [[Q22897]] :::* [[abstract:requests for permissions]] — [[d:special:entitypage/Q5453037|requests for permissions]] — [[Q5453037]] :::* [[abstract:suggested functions]] — [[d:special:entitypage/Q139175401|suggested functions]] — [[Q139175401]] :::* [[abstract:tools]] — [[d:special:entitypage/Q6584911|tools]] — [[Q6584911]] :::* [[abstract:useful functions for article composition]] — [[d:special:entitypage/Q139175483|useful functions for article composition]] — [[Q139175483]] :::* [[abstract:user groups]] — [[d:special:entitypage/Q4616064|user groups]] — [[Q4616064]] :::* [[abstract:WikiProject]] — [[d:special:entitypage/Q4234303|WikiProject]] — [[Q4234303]] :::* [[abstract:WikiProject Core articles]] — [[d:special:entitypage/Q43375360|vital articles]] — [[Q43375360]] :::* [[abstract:WikiProject Quality Prose]] — [[d:special:entitypage/Q115706234|proficiency]] — [[Q115706234]] :::as initial candidates in the project namespace. Of course, the articles would be about these pages in '''all''' of the linked wikis, technically; but the pages are 'about' their own subjects which is what would end up being conveyed anyway. There's also [[abstract:general disclaimer]] which is linked in the footer of every page but doesn't exist yet, so it could even be abstract-first on this wiki ([[wikidata:special:entitypage/Q4980478|general disclaimer]], [[Q4980478]]). In the 'help' namespace there's: :::* [[help:contents]] — [[d:special:entitypage/Q914807|contents]] — [[Q914807]] :::* [[help:how to create an article]] — [[d:special:entitypage/Q151637|editing]] — [[Q151637]] :::[[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 07:26, 19 April 2026 (UTC) ::::I'm not certain that's how we want to use [[d:Q14204246]] instances. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:23, 19 April 2026 (UTC) :::::To what use should they be put then, if any? [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:25, 19 April 2026 (UTC) ::::::To describe the topics encyclopedically? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 11:49, 11 May 2026 (UTC) :::::::But if we are going by Wikidata sitelinks, the topics are various project and help namespace pages on separate wikis, including this one — as a sort of [[Q1549285]]. Or maybe the line between stating what said pages are used for, and what their basic use ''is'' doesn't distinguish as much as I might initially think. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 12:02, 11 May 2026 (UTC) == Adding Item labels == I think it is helpful to see directly at the page the item labels of the proposed core articles and a link to the item. At my user page I tried it with {{Q|868}} and it did not show a label. In Wikifunctions I got the english Label. What do you think about adding the Template Q to the items to show a label. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:51, 19 April 2026 (UTC) :Seems like the Q template import at Abstract Wikipedia needs something else to actually retrieve the labels, then. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 21:50, 19 April 2026 (UTC) ::It is possible to add a language explicit in the template as an argument. This requires translating the Wikiproject page to enable people to view item labels in different languages. As Abstract Wikipedia has the goal of making content available in more languages I think this is an important point to be not too much english centered. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:35, 24 April 2026 (UTC) :::{{q|505335}} ([[Q505335]]) for example has a 'mul' label, it should display that by default. [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|talk]]) 19:59, 24 April 2026 (UTC) : Being bold here: I added the template Q for the labels. It also links to wikidata and shows the (same) wikidate Q-id with a link). The links to wikidata and the Q-id are not needed, so maybe an alternitve template to only show the text of tha labes could fix that. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 16:59, 3 May 2026 (UTC) ::There is [[Template:Label]] for showing only the label of an item. So for example <code><nowiki>{{label|Q97|link=wikidata}}</nowiki></code>. So far the link is not leading to Wikidata as expected. So the templates needs improvement or same changes in Abstract Wikipedia. I link it is useful if the link leads to the Wikidata item. As it can help learning about what an item is about and to see what content is available in Wikidata so far. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 19:17, 4 May 2026 (UTC) :::<code><nowiki>{{label|Q97|link=-}}</nowiki></code> shows the label text only. So fro example :::# [[Q97]] {{label|Q97|link=-}} :::[[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:16, 5 May 2026 (UTC) :::: Or <code><nowiki>[[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]</nowiki></code>) gives ::::# [[Q97]] {{label|Q97|link=-}} ([https://www.wikidata.org/wiki/Q97 Wikidata link]) :::: [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 11:27, 5 May 2026 (UTC) == Missing Templates in Abstract Wikipedia == I currently do not know if there are created templates on this platform to aid in article creation because I currently find creating or editing abstract Wikipedia more tedious instead of it making life simpler for both humans and machines since we were using Wikifunctions and Wikidata as our backbone. I contacted @[[User:Hogü-456|Hogü-456]] to see if he had answers but he said I could post it here for a wider discussion. Thinking out loud, I think if we could create standard templates for articles on various subjects, category and topics of interest, that will get us much closer to the overall dream of abstract Wikipedia and automatically pull in people with non-technical background. For example, the way the article for [https://abstract.wikipedia.org/view/en/Q408 Australia] could be used as yardstick for creating articles for a country and once a template is created for country level article creation, we could even have bots create these articles under the approval of human. There are some other beautiful articles already we could use it's structure to create a master template for any of the following: * Plants * Animals * Disease * Biographies * Countries * Wikimedia affiliates * ETC... Again, Wikidata powered infobox dubbed Databox makes articles beautiful and would make our articles great. [[User:Dnshitobu|Dnshitobu]] ([[User talk:Dnshitobu|talk]]) 08:25, 11 May 2026 (UTC) :Of course. I think [[Q49613|year intros]] are also somewhat inspiring, they don't create ''great'' content, but it's somewhat useful. Each "template article" (which we might require to obtain featured status) might have some of its own functions created for it that will need to be made multilingual. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:05, 11 May 2026 (UTC) :: Question: Would it be possible to add infoboxes to Abstract Wikipedia articles? Infoboxes generated fully from Wikidata will provide a wealth of data, like template:Wikidata Infobox on Commons. [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:46, 11 May 2026 (UTC) :::I don't see why not. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:51, 11 May 2026 (UTC) 7bedgzmqgnax5vjtlrzdkowm2mhf53y 10 2802 7661 7304 2026-05-12T07:48:17Z HenkvD 1447 7661 wikitext text/x-wiki <div class=wikitable style="text-align: center; font-size: 85%; margin-bottom: 1em;"> '''This Abstract Wikipedia lemma is a test lemma''' </div><noinclude> lqv0ljp07tp89xg7i9a8iyiufiwge9o 12 2809 7579 7378 2026-05-11T20:34:59Z Alfa-ketosav 3488 Created page with "Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[$1|kereséssel]] állapítható meg), kövesd [[$2|e segítséglapot]] az új elem létrehozásához." 7579 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <div lang="en" dir="ltr" class="mw-content-ltr"> == Steps == </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In order to create an article, you can go to [[Special:CreateAbstract|Create a New Abstract Article]]. </div> [[file:aw-tutorial-step-1.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select a topic</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Type to select a topic, and click on create.</span> [[file:aw-tutorial-step-2.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Empty abstract article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus sign to add a fragment.</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] g5qii2xpr3f7von9vytx9yl5jq6ohlp 7581 7579 2026-05-11T20:35:03Z Alfa-ketosav 3488 Created page with "== Lépések ==" 7581 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == <div lang="en" dir="ltr" class="mw-content-ltr"> In order to create an article, you can go to [[Special:CreateAbstract|Create a New Abstract Article]]. </div> [[file:aw-tutorial-step-1.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select a topic</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Type to select a topic, and click on create.</span> [[file:aw-tutorial-step-2.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Empty abstract article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus sign to add a fragment.</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] hhkisj9xau3x23mm6u1zqz7vcxp7z3k 7583 7581 2026-05-11T20:35:24Z Alfa-ketosav 3488 Created page with "A szócikk létrehozásához mehetsz a [[$1|Új absztrakt szócikk létrehozása]] linkre." 7583 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select a topic</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Type to select a topic, and click on create.</span> [[file:aw-tutorial-step-2.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Empty abstract article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus sign to add a fragment.</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] l23og6u2ao47c9add3gl3wl4b60gde2 7585 7583 2026-05-11T20:35:30Z Alfa-ketosav 3488 Created page with "Témaválasztás" 7585 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] <span lang="en" dir="ltr" class="mw-content-ltr">Type to select a topic, and click on create.</span> [[file:aw-tutorial-step-2.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Empty abstract article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus sign to add a fragment.</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] l4zxkviy235ktokuofbrl4cwy9e4fnr 7587 7585 2026-05-11T20:35:45Z Alfa-ketosav 3488 Created page with "Írd be a kiválasztott témát, és kattints a létrehozásra." 7587 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Empty abstract article</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus sign to add a fragment.</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] e3rd4input1k61dwg0nokjk6dl08dt9 7589 7587 2026-05-11T20:35:50Z Alfa-ketosav 3488 Created page with "Üres absztrakt szócikk" 7589 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus sign to add a fragment.</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] hv0t1mkl9qdue1coa5wtgfecjlecfux 7591 7589 2026-05-11T20:36:16Z Alfa-ketosav 3488 Created page with "Kattints a pluszjelre a részlet hozzáadásához." 7591 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">An empty fragment</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 70bcgps458s8d3n2ojieuxf3lfx9y6b 7593 7591 2026-05-11T20:36:22Z Alfa-ketosav 3488 Created page with "Üres részlet" 7593 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Function selector open</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 8ll9az7u8dtgo6lbnvzu7aqlff87r9a 7595 7593 2026-05-11T20:36:52Z Alfa-ketosav 3488 Created page with "Nyitott függvényválasztó" 7595 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] <span lang="en" dir="ltr" class="mw-content-ltr">That will open the function selector.</span> [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 8uh11zj09494n2smsee02yrco58mta8 7597 7595 2026-05-11T20:36:57Z Alfa-ketosav 3488 Created page with "Ez megnyitja a függvényválasztót." 7597 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selecting a function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] oweiin7cjp1te0q5y3n10vdirn8hgke 7599 7597 2026-05-11T20:37:01Z Alfa-ketosav 3488 Created page with "Függvényválasztás" 7599 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] <span lang="en" dir="ltr" class="mw-content-ltr">We select a function. It has to be a function that exists on Wikifunctions, and at this point, it has to return an HTML fragment. In this example we choose the function "string to HTML fragment", as this allows us to enter a string, or choose a function that creates a string.</span> [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 1b2a6pg4k1hi40f9d0hu4rfi8au2ytu 7601 7599 2026-05-11T20:37:54Z Alfa-ketosav 3488 Created page with "Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterlánc alakítása HTML-részletté” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását." 7601 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterlánc alakítása HTML-részletté” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] o22b07jm6jsyjhedg7x17igkkcj7na0 7603 7601 2026-05-11T20:38:08Z Alfa-ketosav 3488 7603 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Selected the "string to HTML fragment" function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 2rj73gggr2tdv6xa3gkikfpdi9d3g2z 7605 7603 2026-05-11T20:38:18Z Alfa-ketosav 3488 Created page with "„Karakterláncból HTML-részlet” függvény kiválasztva" 7605 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] <span lang="en" dir="ltr" class="mw-content-ltr">We have now selected a function. We get fields for the arguments. Instead of typing a string, we want to add another function,</span> [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 1zz495lvmruzs758uh7sw3w393ymqmd 7608 7605 2026-05-11T20:40:05Z Alfa-ketosav 3488 Created page with "Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki." 7608 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Change the mode of the argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] g8tn6hn2w5baorrhyaru4fxudvuxue5 7610 7608 2026-05-11T20:40:11Z Alfa-ketosav 3488 Created page with "Paramétermód változtatása" 7610 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] <span lang="en" dir="ltr" class="mw-content-ltr">In order to do so, we change the mode of the argument named string by clicking on the three dots next to string. This allows us to change from the current mode, literal, to a function call.</span> [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 63xdeioclu4tbl6ad4b8wd3kal9ummu 7612 7610 2026-05-11T20:40:53Z Alfa-ketosav 3488 Created page with "Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást." 7612 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Select the inner function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] auvrllbpuzbfs2krnaxmmcy3sgsgi4d 7614 7612 2026-05-11T20:40:59Z Alfa-ketosav 3488 Created page with "Belső függvény kiválasztása" 7614 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] <span lang="en" dir="ltr" class="mw-content-ltr">Here we can now select a function that returns a string.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] kqjzsyvgu7a9s9r1wolh59qs8wew7ng 7617 7614 2026-05-11T20:41:11Z Alfa-ketosav 3488 Created page with "Most kiválaszthatunk egy karakterláncot adó függvényt." 7617 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Choose a function returning a string</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 84abl234oiz8pzmh0vi2aezm10wbv3a 7619 7617 2026-05-11T20:41:19Z Alfa-ketosav 3488 Created page with "Karakterláncot adó függvény kiválasztása" 7619 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] <span lang="en" dir="ltr" class="mw-content-ltr">We select the function "Article-less instantiating fragment" -- a function that creates sentences such as "Paris is a city." Note that selecting the function “Article-less instantiating HTML fragment” would have allowed us to skip using the function “string to HTML fragment”.</span> [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] q6rj9ofr5kiebsyvbqejmr5leiqa17r 7621 7619 2026-05-11T20:42:23Z Alfa-ketosav 3488 Created page with "A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását." 7621 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Arguments for article-less instantiating fragment function</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 5fsf6x3sou3ju66hx5nmmcdr0iuv03r 7623 7621 2026-05-11T20:42:44Z Alfa-ketosav 3488 Created page with "Névelő nélküli leíró részlet függvény paraméterei" 7623 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] <span lang="en" dir="ltr" class="mw-content-ltr">Now we see the arguments for this function. We also get automatically fitting arguments filled in. This leads to the sentence "Paris is a Paris.", because the arguments "entity" and "class" both get prefilled with the item we are writing about.</span> [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] ssn0of59c5dikgblz6wk5r2fenyl54j 7626 7623 2026-05-11T20:43:38Z Alfa-ketosav 3488 Created page with "Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre." 7626 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|<span lang="en" dir="ltr" class="mw-content-ltr">Changing the mode on the "class" argument</span>]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] lrhywexg0q8ob5csx4fzyifl8vuji9u 7628 7626 2026-05-11T20:43:52Z Alfa-ketosav 3488 Created page with "Osztályparaméter módjának megváltoztatása" 7628 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] <span lang="en" dir="ltr" class="mw-content-ltr">We need to change the mode on the "class" argument from the automatically filled value (an Argument reference) to a literal.</span> [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 0cuqzxdhskvgf7egfj9bpv40j3r2ql8 7630 7628 2026-05-11T20:44:14Z Alfa-ketosav 3488 Created page with "Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni." 7630 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] <span lang="en" dir="ltr" class="mw-content-ltr">You will get to a new screen. On the right hand side you see the preview in the selected language, on the left hand side the abstract content.</span> [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] bdfyu4bwh7svgkox86cmq47yba7ausv 7636 7630 2026-05-11T20:54:18Z Alfa-ketosav 3488 Created page with "Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom." 7636 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] <span lang="en" dir="ltr" class="mw-content-ltr">Click on the plus button in the left panel to add a new fragment. For now, we are adding an empty fragment.</span> [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] pbpjdbnyipe37v8uc8o41f2xfl2ucc8 7638 7636 2026-05-11T20:54:46Z Alfa-ketosav 3488 Created page with "Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá." 7638 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá. [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] <span lang="en" dir="ltr" class="mw-content-ltr">This will look like this, showing a function call without a function selected yet. We click on the caron next to the red "Select Function" text.</span> [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 2o1mzu8d2dmynv9i4kv6whe8ow68iyd 7642 7638 2026-05-11T20:55:27Z Alfa-ketosav 3488 Created page with "Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk." 7642 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá. [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk. [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] <div lang="en" dir="ltr" class="mw-content-ltr"> Once this is selected, the first sentence of the article should be ready. We can now click on publish and have a first version of the article available. Now you can click edit to add more. </div> <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] twa972h6t2edvw0qz6prolumytuww0u 7645 7642 2026-05-11T20:56:24Z Alfa-ketosav 3488 Created page with "Ennek kiválasztásakor az első mondatnak késznek kell lennie. Megnyomhatjuk a „Közzététel” gombot, elérhetővé téve a cikk első változatát. Továbbiak hozzáadásához kattinthatsz a „Szerkesztés” gombra." 7645 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá. [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk. [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] Ennek kiválasztásakor az első mondatnak késznek kell lennie. Megnyomhatjuk a „Közzététel” gombot, elérhetővé téve a cikk első változatát. Továbbiak hozzáadásához kattinthatsz a „Szerkesztés” gombra. <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával <div lang="en" dir="ltr" class="mw-content-ltr"> Whereas the development team at the Wikimedia Foundation will be focused on the first approach (and will always appreciate UX ideas), the community can work on a more comprehensive and easy to use catalogue of functions in Wikifunctions. Here we see that naming the functions and arguments is important, and that we probably want to avoid too many functions which turn one type in another in the above flow. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] m06ek7brxtmrasppog6y7q78ed4se9w 7648 7645 2026-05-11T20:58:05Z Alfa-ketosav 3488 Created page with "Bár a Wikimédia Alapítvány fejlesztői csapata az első megközelítésre összpontosít (és mindig támogatja az UX-ötleteket), a közösség a Wikifunkciókon a teljesebb és könnyebben használható függvénykatalógusért tehet. Itt látható a függvények és paraméterek megnevezésének fontossága, és hogy valószínűleg szeretnénk elkerülni a túl sok egyik típust másikká alakító függvény használatát." 7648 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá. [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk. [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] Ennek kiválasztásakor az első mondatnak késznek kell lennie. Megnyomhatjuk a „Közzététel” gombot, elérhetővé téve a cikk első változatát. Továbbiak hozzáadásához kattinthatsz a „Szerkesztés” gombra. <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával Bár a Wikimédia Alapítvány fejlesztői csapata az első megközelítésre összpontosít (és mindig támogatja az UX-ötleteket), a közösség a Wikifunkciókon a teljesebb és könnyebben használható függvénykatalógusért tehet. Itt látható a függvények és paraméterek megnevezésének fontossága, és hogy valószínűleg szeretnénk elkerülni a túl sok egyik típust másikká alakító függvény használatát. <div lang="en" dir="ltr" class="mw-content-ltr"> But yes, most importantly, Abstract Wikipedia is currently in an early public Beta, and it is currently difficult to create and edit articles. We all will need to work together to improve that. If you have ideas for new functions, please suggest them at [[Abstract Wikipedia:Suggested functions|Suggested functions]]. </div> <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 104xl5voiv381md7vrvdrelfmip51qa 7651 7648 2026-05-11T20:59:08Z Alfa-ketosav 3488 Created page with "De igen, ami a legfontosabb, az Absztrakt Wikipédia jelenleg korai nyilvános béta állapotban van, és jelenleg nehéz a cikkek létrehozása és szerkesztése. Mindannyiunknak együtt kell működni ennek javításában. Ha vannak új függvényötleteid, tedd fel őket javaslatra a [[$1|Kért függvények]] listáján." 7651 wikitext text/x-wiki <languages/> Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[d:special:search|kereséssel]] állapítható meg), kövesd [[d:Special:MyLanguage/help:items#Creating a new item|e segítséglapot]] az új elem létrehozásához. <span id="Steps"></span> == Lépések == A szócikk létrehozásához mehetsz a [[Special:CreateAbstract|Új absztrakt szócikk létrehozása]] linkre. [[file:aw-tutorial-step-1.png|center|frameless|800px|Témaválasztás]] Írd be a kiválasztott témát, és kattints a létrehozásra. [[file:aw-tutorial-step-2.png|center|frameless|800px|Üres absztrakt szócikk]] Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. [[file:aw-tutorial-step-3.png|center|frameless|800px|Kattints a pluszjelre a részlet hozzáadásához.]] Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá. [[file:aw-tutorial-step-4.png|center|frameless|800px|Üres részlet]] Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk. [[file:aw-tutorial-step-5.png|center|frameless|800px|Nyitott függvényválasztó]] Ez megnyitja a függvényválasztót. [[file:aw-tutorial-step-6.png|center|frameless|800px|Függvényválasztás]] Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. [[file:aw-tutorial-step-7.png|center|frameless|800px|„Karakterláncból HTML-részlet” függvény kiválasztva]] Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. [[file:aw-tutorial-step-8.png|center|frameless|800px|Paramétermód változtatása]] Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. [[file:aw-tutorial-step-9.png|center|frameless|800px|Belső függvény kiválasztása]] Most kiválaszthatunk egy karakterláncot adó függvényt. [[file:aw-tutorial-step-10.png|center|frameless|800px|Karakterláncot adó függvény kiválasztása]] A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. [[file:aw-tutorial-step-10.png|center|frameless|800px|Névelő nélküli leíró részlet függvény paraméterei]] Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. [[file:aw-tutorial-step-11.png|center|frameless|800px|Osztályparaméter módjának megváltoztatása]] Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. [[file:aw-tutorial-step-12.png|center|frameless|800px|„Osztály” módjának váltása literálra.]] Ez mezőt ad nekünk Wikidata-elem kiválasztására az osztályargumentum értékéhez. [[file:aw-tutorial-step-13.png|center|frameless|800px|Város kiválasztása osztályargumentumként]] Kiválasztjuk a „város” elemet osztályargumentumként. [[file:aw-tutorial-step-14.png|center|frameless|800px|Az első mondat létrejött.]] Ennek kiválasztásakor az első mondatnak késznek kell lennie. Megnyomhatjuk a „Közzététel” gombot, elérhetővé téve a cikk első változatát. Továbbiak hozzáadásához kattinthatsz a „Szerkesztés” gombra. <span id="This_is_far_too_complicated!"></span> == Ez túl bonyolult! == Igen, elfogadva. Kétféleképp lehet ezt könnyíteni: * UX-javítással * a függvénykatalógus javításával Bár a Wikimédia Alapítvány fejlesztői csapata az első megközelítésre összpontosít (és mindig támogatja az UX-ötleteket), a közösség a Wikifunkciókon a teljesebb és könnyebben használható függvénykatalógusért tehet. Itt látható a függvények és paraméterek megnevezésének fontossága, és hogy valószínűleg szeretnénk elkerülni a túl sok egyik típust másikká alakító függvény használatát. De igen, ami a legfontosabb, az Absztrakt Wikipédia jelenleg korai nyilvános béta állapotban van, és jelenleg nehéz a cikkek létrehozása és szerkesztése. Mindannyiunknak együtt kell működni ennek javításában. Ha vannak új függvényötleteid, tedd fel őket javaslatra a [[Abstract Wikipedia:Suggested functions|Kért függvények]] listáján. <span id="See_also"></span> == Lásd még == * [[Abstract Wikipedia:Useful functions for article composition]] [[category:help{{#translation:}}]] 6banpj5o2qeb4fkhexgwqam473j8yb1 4 2883 7546 7540 2026-05-11T12:11:31Z Feeglgeef 36 7546 wikitext text/x-wiki :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Emphasis == ''Italics'' are to be used for emphasis, instead of '''boldface''' or CAPITALS. Overuse may diminish its effect: consider rewriting instead. == Quotations == Brief quotations of copyrighted text may be used to illustrate a point, establish context, or attribute a point of view or idea. While quotations are an indispensable part of Wikipedia, excessive use of them is incompatible with an encyclopedic writing style, makes the content hard for those who don't speak the quoted language to understand, and may be copyright infringement, so most of the content should be abstract content. Consider paraphrasing quotations into plain and concise text when appropriate (while being aware that close paraphrasing can still violate copyright). Quotes should always be handled as if in a foreign language. == Links == * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. [[Category:Abstract Wikipedia administration]] qz0im6nsui7o3u1z9vt2fjly2eqnq9g 7571 7546 2026-05-11T19:33:23Z Dv103 1247 Added reccomendation on which fragments to use 7571 wikitext text/x-wiki :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Emphasis == ''Italics'' are to be used for emphasis, instead of '''boldface''' or CAPITALS. Overuse may diminish its effect: consider rewriting instead. == Quotations == Brief quotations of copyrighted text may be used to illustrate a point, establish context, or attribute a point of view or idea. While quotations are an indispensable part of Wikipedia, excessive use of them is incompatible with an encyclopedic writing style, makes the content hard for those who don't speak the quoted language to understand, and may be copyright infringement, so most of the content should be abstract content. Consider paraphrasing quotations into plain and concise text when appropriate (while being aware that close paraphrasing can still violate copyright). Quotes should always be handled as if in a foreign language. == Links == * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Fragments == Only use fragments that are already implemented in multiple languages. New fragments may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use fragments for their exact definition. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. [[Category:Abstract Wikipedia administration]] mam3f4vxm7t4v2jn3ff8ywxicft08ju 7615 7571 2026-05-11T20:41:03Z Feeglgeef 36 rm emphasis per talk 7615 wikitext text/x-wiki :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Quotations == Brief quotations of copyrighted text may be used to illustrate a point, establish context, or attribute a point of view or idea. While quotations are an indispensable part of Wikipedia, excessive use of them is incompatible with an encyclopedic writing style, makes the content hard for those who don't speak the quoted language to understand, and may be copyright infringement, so most of the content should be abstract content. Consider paraphrasing quotations into plain and concise text when appropriate (while being aware that close paraphrasing can still violate copyright). Quotes should always be handled as if in a foreign language. == Links == * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Fragments == Only use fragments that are already implemented in multiple languages. New fragments may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use fragments for their exact definition. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. [[Category:Abstract Wikipedia administration]] sl9uhlc1j8bzke5pinmmtkiyiqbyrjo 7631 7615 2026-05-11T20:44:40Z Feeglgeef 36 7631 wikitext text/x-wiki :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Quotations == Brief quotations of copyrighted text may be used to illustrate a point, establish context, or attribute a point of view or idea. While quotations are an indispensable part of Wikipedia, excessive use of them is incompatible with an encyclopedic writing style, makes the content hard for those who don't speak the quoted language to understand, and may be copyright infringement, so most of the content should be abstract content. Consider paraphrasing quotations into plain and concise text when appropriate (while being aware that close paraphrasing can still violate copyright). Quotes should always be handled as if in a foreign language. == Links == * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Functions == Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions for their exact definition. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. [[Category:Abstract Wikipedia administration]] ndy75uhokvtbtzt7r03wqv751gi4tar 7632 7631 2026-05-11T20:46:50Z Feeglgeef 36 /* Functions */ elaborate 7632 wikitext text/x-wiki :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Quotations == Brief quotations of copyrighted text may be used to illustrate a point, establish context, or attribute a point of view or idea. While quotations are an indispensable part of Wikipedia, excessive use of them is incompatible with an encyclopedic writing style, makes the content hard for those who don't speak the quoted language to understand, and may be copyright infringement, so most of the content should be abstract content. Consider paraphrasing quotations into plain and concise text when appropriate (while being aware that close paraphrasing can still violate copyright). Quotes should always be handled as if in a foreign language. == Links == * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Functions == Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions in the literal sense of their scope. Do not use them for metaphorso or abstract concepts. Just because the output in English (or any one language) is correct does not make a use acceptable. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. [[Category:Abstract Wikipedia administration]] st9qe33miu8v9yawmb3fbyz5g1zdt4o 7633 7632 2026-05-11T20:51:23Z Feeglgeef 36 /* Quotations */ 7633 wikitext text/x-wiki :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Quotations == Quotations should be used sparingly, as a quote can only be on one language, whereas an article in many. They should be used only when you would naturally use a foreign language quote. Consider paraphrasing quotations abstractly (while being aware that close paraphrasing can still violate copyright). == Links == * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Functions == Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions in the literal sense of their scope. Do not use them for metaphorso or abstract concepts. Just because the output in English (or any one language) is correct does not make a use acceptable. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. [[Category:Abstract Wikipedia administration]] bj4wad3n5occf394pe2ohtd81kwz487 7653 7633 2026-05-11T20:59:38Z Feeglgeef 36 shortcut notices 7653 wikitext text/x-wiki {{Shortcut|Abstract Wikipedia:MOS}} :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == {{Shortcut|Abstract Wikipedia:MOS/SO}} An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == {{Shortcut|Abstract Wikipedia:MOS/SH}} All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Quotations == {{Shortcut|Abstract Wikipedia:MOS/Q}} Quotations should be used sparingly, as a quote can only be on one language, whereas an article in many. They should be used only when you would naturally use a foreign language quote. Consider paraphrasing quotations abstractly (while being aware that close paraphrasing can still violate copyright). == Links == {{Shortcut|Abstract Wikipedia:MOS/LINK}} * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == {{Shortcut|Abstract Wikipedia:MOS/P}} Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Functions == {{Shortcut|Abstract Wikipedia:MOS/FUNC}} Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions in the literal sense of their scope. Do not use them for metaphorso or abstract concepts. Just because the output in English (or any one language) is correct does not make a use acceptable. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. [[Category:Abstract Wikipedia administration]] du6ztasz4t3iw0zjv5am8u41xvymwrn 7654 7653 2026-05-11T21:04:42Z Feeglgeef 36 + monolingual content 7654 wikitext text/x-wiki {{Shortcut|Abstract Wikipedia:MOS}} :''Note: this manual has yet to be approved by community consensus, and is still in draft phase.'' This '''Manual of Style''' is the style manual for all Abstract Wikipedia articles. This page applies to content in all languages, but be sure to check the local Wikipedia's style guide, as you should adhere to that as much as possible for outputted text. This manual may be relevant to content authors, function authors, or both. == Section organization == {{Shortcut|Abstract Wikipedia:MOS/SO}} An article's content should begin with an introductory lead section – a concise summary of the article – which is never divided into sections. The remainder of the article is typically divided into sections. Infoboxes, images, and other related content in the lead should be positioned on the side opposite the reader's starting point for that specific script (on the right for left-to-right languages like English, on the left for right-to-left languages like Arabic). == Section headings == {{Shortcut|Abstract Wikipedia:MOS/SH}} All section headings should be their own fragment. Section headings should not: * redundantly refer back to the subject of the article, e.g., Early life, not Smith's early life or His early life * refer to a higher-level heading, unless doing so is shorter or clearer * be numbered or lettered as an outline * use question format, e.g., Languages, not What languages are spoken? * use color, unusual fonts, markup such as bold or italics, images, citations, or footnotes, which cause accessibility issues. Section headings must be unique in all languages (except in ones with exceptionally limited vocabulary, like Toki Pona). == Quotations == {{Shortcut|Abstract Wikipedia:MOS/Q}} Quotations should be used sparingly, as a quote can only be on one language, whereas an article in many. They should be used only when you would naturally use a foreign language quote. Consider paraphrasing quotations abstractly (while being aware that close paraphrasing can still violate copyright). == Links == {{Shortcut|Abstract Wikipedia:MOS/LINK}} * '''Make links only where they are relevant and helpful in the context''': Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that are worth pursuing should stand out clearly. * '''Link to Abstract Wikipedia articles''': Do not link to articles on other Wikipedias, such as the English Wikipedia, unless in a section specifically for external links. Link to an Abstract Wikipedia article through its QID, displaying the title of the article or another relevant name in the display language. * '''Link a term at most once per major section''': Only include one link per term per major section (typically level 2), at its first occurrence. == Paragraphs == {{Shortcut|Abstract Wikipedia:MOS/P}} Paragraphs should roughly cover one cohesive topic area. Each paragraph should be its own fragment, and all parts of the paragraph should be one fragment. In the interest of best serving the many languages that abstract content may be written in, write in chronological order, and include the most general statements first and continue to more detailed statements. == Functions == {{Shortcut|Abstract Wikipedia:MOS/FUNC}} Only use NLG functions that are already implemented in multiple languages. New functions may be ill-defined, and might never be suitable for Abstract Wikipedia. Only use functions in the literal sense of their scope. Do not use them for metaphorso or abstract concepts. Just because the output in English (or any one language) is correct does not make a use acceptable. For example, only use [[f:Z26570]] only for physical locations, and not for metaphorical ones. Do not use a sequence of functions that only generate a part of a sentence, since different languages structure their sentences in a very different way. == Monolingual content == {{Shortcut|Abstract Wikipedia:MOS/MONO}} Monolingual content should be avoided on Abstract Wikipedia to the greatest extent possible. [[Category:Abstract Wikipedia administration]] isdiy4ksgcw8kvwfz4o5jp7cltch0l6 2 2887 7547 2026-05-11T12:38:25Z Dv103 1247 Created page with "== Discussions == * [[/Abstract articles architectures|Abstract articles architectures]]" 7547 wikitext text/x-wiki == Discussions == * [[/Abstract articles architectures|Abstract articles architectures]] 8n49ks2jct5esurmm77wf9lnguh386q 4 2888 7548 2026-05-11T13:13:45Z Dv103 1247 Current architecture 7548 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural language heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introduction a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. ewfgcsb47yfe2ona9fyzz4qtx1e91mv 7549 7548 2026-05-11T14:26:46Z Dv103 1247 Added the semantic unit architecture 7549 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural language heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introduction a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === ae7oj19vh0nd78gg55l8cz1roftpsjz 7558 7549 2026-05-11T16:58:50Z Theki 2698 7558 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introduction a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === ai66ojvddb0a6r1ydx37kn8ju123wr0 7559 7558 2026-05-11T16:59:49Z Theki 2698 7559 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === ammuql0ennlm68abh3pp8ovmgwwm6ow 7562 7559 2026-05-11T18:03:11Z Dv103 1247 First draft for Stream semantic units 7562 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|frame]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is instead splitted in paragraphs. i8dpyus7x3dak5b9swfnr4rnh1fgyj8 7565 7562 2026-05-11T19:11:17Z Dv103 1247 /* Stream semantic units */ Completed the section 7565 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|frame]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is splitted in paragraphs. Each renderer internally would work very similarly to the renders described in the previous section. The article is generated by the concatenation of the outputs of the various renderers. Starting from the second renderer, each renderer would have two sources of inputs: * the input defined in the function call (i.e., in Abstract Wikipedia), consisting in the Semantic unit representing a part of the article (indicatively, a paragraph), * the input coming from the previous renderer, consisting in 2 inputs: ** the abstract content that the previous renderer decided not to render, ** the context (initially created on Abstract Wikipedia and passed to the first renderer as an input), updated by all the rederers that have executed previously. The renderer would then execute, providing three outputs: * the HTML containing the rendered abstract content that the renderer decided to render, * the abstract content (Semantic unit) that for some reasons it may decide not to render and to pass to the next renderer, * the context, updated by the renderer itself. The first output would go directly to compose the Abstract Wikipedia article, while the other 2 outputs will be used as inputs by the next renderer. At the end of the chain, a "Final renderer" would render the eventual abstract content that has not been rendered yet. While it is already technically possible to implement this chain on Wikifunctions, it would be a single function call, and, like the previous proposal, it would suffer from the issue that it would need to generate the entire article in one go. The real advantage of this proposal would come if, instead of being implemented by a regular function, it was implemented through a magical function that would execute the renderers sequentially, giving each one the complete function execution timeout, collecting the partial outputs (and show the partial generated output directly in the page) and passing the internal outputs to the next renderer, alongside the new external input. === Pros === * It would have all the advantages of the Semantic unit architectures, and still give at least partial outputs in a reasonable time (limiting timeouts). * Even if it doesn't allow the constructors to know all the abstract content that eventually will need to be rendered, it still gives them a quantity of foreknowledge that should be enough for practical purposes, while mantaining all the necessary memory of the previous content. After all, this is more or less the same type of knowledge humans have while generating linguistic content. === Cons === * It is not currently implementable, since it requires a magic function that has a special behavior. * It requires rendering partial abstract content in discrete sequential chunks, without the possibility to refine them once more abstract contentent is rendered. However, as mentioned before, realistically this should not be a problem, since the quantity of foreknowledge that renderers have available (i.e., the content of the entire paragraph) should be enough for all practical purposes. === Comments === gs25wv00jn3q7au8sdlet4e5niqrgq9 7567 7565 2026-05-11T19:14:38Z Dv103 1247 /* Stream semantic units */ 7567 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|frame]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is splitted in paragraphs. Each renderer internally would work very similarly to the renders described in the previous section. The article is generated by the concatenation of the outputs of the various renderers. Starting from the second renderer, each renderer would have two sources of inputs: * the input defined in the function call (i.e., in Abstract Wikipedia), consisting in the Semantic unit representing a part of the article (indicatively, a paragraph), * the input coming from the previous renderer, consisting in 2 inputs: ** the abstract content that the previous renderer decided not to render, ** the context (initially created on Abstract Wikipedia and passed to the first renderer as an input), updated by all the rederers that have executed previously. The renderer would then execute, providing three outputs: * the HTML containing the rendered abstract content that the renderer decided to render, * the abstract content (Semantic unit) that for some reasons it may decide not to render and to pass to the next renderer, * the context, updated by the renderer itself. The first output would go directly to compose the Abstract Wikipedia article, while the other 2 outputs will be used as inputs by the next renderer. At the end of the chain, a "Final renderer" would render the eventual abstract content that has not been rendered yet. While it is already technically possible to implement this chain on Wikifunctions, it would be a single function call, and, like the previous proposal, it would suffer from the issue that it would need to generate the entire article in one go. The real advantage of this proposal would come if, instead of being implemented by a regular function, it was implemented through a magical function that would execute the renderers sequentially, giving each one the complete function execution timeout, collecting the partial outputs (and showing the partial generated output directly in the page) and passing the internal outputs to the next renderer, alongside the new external input. === Pros === * It would have all the advantages of the Semantic unit architectures, and still give at least partial outputs in a reasonable time (limiting timeouts). * Even if it doesn't allow the constructors to know all the abstract content that eventually will need to be rendered, it still gives them a quantity of foreknowledge that should be enough for practical purposes, while mantaining all the necessary memory of the previous content. After all, this is more or less the same type of knowledge humans have while generating linguistic content. === Cons === * It is not currently implementable, since it requires a magic function that has a special behavior. * It requires rendering partial abstract content in discrete sequential chunks, without the possibility to refine them once more abstract contentent is rendered. However, as mentioned before, realistically this should not be a problem, since the quantity of foreknowledge that renderers have available (i.e., the content of the entire paragraph) should be enough for all practical purposes. === Comments === 68820e4jjrsp7zsyary70emew6fingz 7568 7567 2026-05-11T19:16:43Z Dv103 1247 /* Stream semantic units */ Made image smaller 7568 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|thumb]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is splitted in paragraphs. Each renderer internally would work very similarly to the renders described in the previous section. The article is generated by the concatenation of the outputs of the various renderers. Starting from the second renderer, each renderer would have two sources of inputs: * the input defined in the function call (i.e., in Abstract Wikipedia), consisting in the Semantic unit representing a part of the article (indicatively, a paragraph), * the input coming from the previous renderer, consisting in 2 inputs: ** the abstract content that the previous renderer decided not to render, ** the context (initially created on Abstract Wikipedia and passed to the first renderer as an input), updated by all the rederers that have executed previously. The renderer would then execute, providing three outputs: * the HTML containing the rendered abstract content that the renderer decided to render, * the abstract content (Semantic unit) that for some reasons it may decide not to render and to pass to the next renderer, * the context, updated by the renderer itself. The first output would go directly to compose the Abstract Wikipedia article, while the other 2 outputs will be used as inputs by the next renderer. At the end of the chain, a "Final renderer" would render the eventual abstract content that has not been rendered yet. While it is already technically possible to implement this chain on Wikifunctions, it would be a single function call, and, like the previous proposal, it would suffer from the issue that it would need to generate the entire article in one go. The real advantage of this proposal would come if, instead of being implemented by a regular function, it was implemented through a magical function that would execute the renderers sequentially, giving each one the complete function execution timeout, collecting the partial outputs (and showing the partial generated output directly in the page) and passing the internal outputs to the next renderer, alongside the new external input. === Pros === * It would have all the advantages of the Semantic unit architectures, and still give at least partial outputs in a reasonable time (limiting timeouts). * Even if it doesn't allow the constructors to know all the abstract content that eventually will need to be rendered, it still gives them a quantity of foreknowledge that should be enough for practical purposes, while mantaining all the necessary memory of the previous content. After all, this is more or less the same type of knowledge humans have while generating linguistic content. === Cons === * It is not currently implementable, since it requires a magic function that has a special behavior. * It requires rendering partial abstract content in discrete sequential chunks, without the possibility to refine them once more abstract contentent is rendered. However, as mentioned before, realistically this should not be a problem, since the quantity of foreknowledge that renderers have available (i.e., the content of the entire paragraph) should be enough for all practical purposes. === Comments === h3iju2dv8f2ffoed9e3erp8ehv9sjmr 7569 7568 2026-05-11T19:17:59Z Dv103 1247 7569 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, to comment below the architecture sections, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|thumb]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is splitted in paragraphs. Each renderer internally would work very similarly to the renders described in the previous section. The article is generated by the concatenation of the outputs of the various renderers. Starting from the second renderer, each renderer would have two sources of inputs: * the input defined in the function call (i.e., in Abstract Wikipedia), consisting in the Semantic unit representing a part of the article (indicatively, a paragraph), * the input coming from the previous renderer, consisting in 2 inputs: ** the abstract content that the previous renderer decided not to render, ** the context (initially created on Abstract Wikipedia and passed to the first renderer as an input), updated by all the rederers that have executed previously. The renderer would then execute, providing three outputs: * the HTML containing the rendered abstract content that the renderer decided to render, * the abstract content (Semantic unit) that for some reasons it may decide not to render and to pass to the next renderer, * the context, updated by the renderer itself. The first output would go directly to compose the Abstract Wikipedia article, while the other 2 outputs will be used as inputs by the next renderer. At the end of the chain, a "Final renderer" would render the eventual abstract content that has not been rendered yet. While it is already technically possible to implement this chain on Wikifunctions, it would be a single function call, and, like the previous proposal, it would suffer from the issue that it would need to generate the entire article in one go. The real advantage of this proposal would come if, instead of being implemented by a regular function, it was implemented through a magical function that would execute the renderers sequentially, giving each one the complete function execution timeout, collecting the partial outputs (and showing the partial generated output directly in the page) and passing the internal outputs to the next renderer, alongside the new external input. === Pros === * It would have all the advantages of the Semantic unit architectures, and still give at least partial outputs in a reasonable time (limiting timeouts). * Even if it doesn't allow the constructors to know all the abstract content that eventually will need to be rendered, it still gives them a quantity of foreknowledge that should be enough for practical purposes, while mantaining all the necessary memory of the previous content. After all, this is more or less the same type of knowledge humans have while generating linguistic content. === Cons === * It is not currently implementable, since it requires a magic function that has a special behavior. * It requires rendering partial abstract content in discrete sequential chunks, without the possibility to refine them once more abstract contentent is rendered. However, as mentioned before, realistically this should not be a problem, since the quantity of foreknowledge that renderers have available (i.e., the content of the entire paragraph) should be enough for all practical purposes. === Comments === nvim4tk54ey0varre9pyenu178qn6tt 7657 7569 2026-05-11T21:26:06Z YoshiRulz 640 /* Modest improvement to current architecture using spans */ New section 7657 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, to comment below the architecture sections, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Modest improvement to current architecture using spans == tl;dr: Do all linguistic processing on plaintext (Z11/Monolingual text), but keep track of which span(s) in the string corresponds to each Item from the outer callsite. Then that outer Function can format and linkify the final string by iterating those ranges as ordered by their start index. {| class="wikitable mw-collapsible mw-collapsed" ! (Existing types, for completeness) |- | <syntaxhighlight lang="rust"> type WFString = Z6; type MonolingualText = Z11; // = Pair<Langcode, WFString> type Langcode = Z60; type HTMLFragment = Z89; type List<E> = Z881<E>; type Pair<F, S> = Z882<F, S>; type Map<K, V> = Z883<K, V>; // = List<Pair<K, V>> w/ key uniqueness invariant type WDItem = Z6001; type WDItemRef = Z6091; type Natural = Z13518; </syntaxhighlight> |} <syntaxhighlight lang="rust"> type Span = Pair<Natural, Natural>; type Multimap<K, V> = Map<K, List<V>>; // = List<Pair<K, V>> w/o key uniqueness invariant type NLGOutput = Pair<MonolingualText, Multimap<WDItemRef, Span>>; type RichTextTransform = fn(HTMLFragment) -> HTMLFragment; type SuperlativeInLocationDefiningSentence<R> = fn( subject: WDItemRef, class: WDItemRef, location: WDItemRef, characteristic: WDItemRef, displayLang: Langcode, ) -> R; pub static superlativeInLocationDefiningSentence: SuperlativeInLocationDefiningSentence<HTMLFragment> = |subj, class, loc, charc, lang| applyFormatting( toSentenceCaseAndAddPunctuation( (match lang { Langcode("en", _) => enSuperlativeInLocationDefiningSentence, _ => todo!(), })(subj, class, loc, charc, lang), lang ), Multimap([ createArticleSubjectEmphasisTransformation(subj), createLinkifyTransformation(class, awArticleLinkFor(class)), createLinkifyTransformation(loc, awArticleLinkFor(loc)), ]) ); pub static toSentenceCaseAndAddPunctuation: (NLGOutput, Langcode) -> NLGOutput = todo!(); pub static createArticleSubjectEmphasisTransformation: (WDItemRef) -> RichTextTransform = |item| Pair(item, |innerHTML| HTMLFragment(format!("<strong>{innerHTML}</strong>"))); pub static awArticleLinkFor: (WDItemRef) -> WFString = |item| format!("https://abstract.wikipedia.org/wiki/{item.qid}"); pub static createLinkifyTransformation: (WDItemRef, WFString) -> RichTextTransform = |item, linkTarget| Pair(item, |innerHTML| HTMLFragment(format!("<a href=\"{linkTarget}\">{innerHTML}</a>"))); pub static applyFormatting: (NLGOutput, Multimap<WDItemRef, RichTextTransform>) -> HTMLFragment = todo!(); // handwaving, but it would split the Monolingual text in the 1st arg's first item based on the spans from the 1st arg's second item, convert them to HTML fragments, then apply each of the transformations from the 2nd arg </syntaxhighlight> {| class="wikitable mw-collapsible mw-collapsed" ! (The implementation <code>enSuperlativeInLocationDefiningSentence</code>, as an example) |- | <syntaxhighlight lang="rust"> pub static enSuperlativeInLocationDefiningSentence: SuperlativeInLocationDefiningSentence<NLGOutput> = |subj, class, loc, charc, lang| { let words = [ labelFor(subj, lang), enCopulaFor(subj), MonolingualText(lang, "the"), enSuperlativeFor(charc), labelFor(class, lang), enPrepositionForLoc(loc), labelFor(loc, lang), ]; NLGOutput( MonolingualText(lang, words.join(" ")), [ // Rust is 0-indexed, but there's probably a bunch of errors here anyway, so don't copy it Span(subj, 0..words[0].length), Span(class, (4 + &words[0..=3].iter().map(|&text| text.length).sum()) ..(4 + &words[0..=4].iter().map(|&text| text.length).sum())), Span(loc, (6 + &words[0..=5].iter().map(|&text| text.length).sum()) ..(6 + &words[0..=6].iter().map(|&text| text.length).sum())), Span(charc, (3 + &words[0..=2].iter().map(|&text| text.length).sum()) ..(3 + &words[0..=3].iter().map(|&text| text.length).sum())), ] ) }; </syntaxhighlight> |} === Pros === * The existing corpus of NLG Functions can be either kept as-is (e.g. inflection helpers) or migrated piecemeal (sentence-generating Functions). * This texts+spans structure puts to rest the question of which Type to use for the outputs of sentence-generating Functions: Z11, not Z89 (and definitely not Z6). === Cons === * Inherits the m&ndash;n problem of the status quo: each sentence-generating Function still needs an Implementation in every language. There's no new affordance for constructing grammatically correct sentences from smaller fragments. * Inherits other problems of the status quo, covered in [[#Current architecture]] above. === Comments === (With apologies to non-Rust programmers for its use here as a statically-typed lingua franca, and with apologies to Rust programmers for weird or broken syntax. I know <code>pub fn &lt;identifier&gt;</code> exists.) <br>This outlines what I foresee as the most evolved form of the current architecture, and is an expansion of [[f:WF:Type_proposals/Syntactic_table#c-YoshiRulz-20260403175300-Comments|my offhand comment here]]. <br>I'm only offering this as a "baseline", I can't advocate its adoption (except as a stop-gap, since as mentioned above it does solve the return type problem). Personally, I want to see an architecture which can attain prose, or something close to it, in most of the world's languages. <br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 21:26, 11 May 2026 (UTC) == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|thumb]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is splitted in paragraphs. Each renderer internally would work very similarly to the renders described in the previous section. The article is generated by the concatenation of the outputs of the various renderers. Starting from the second renderer, each renderer would have two sources of inputs: * the input defined in the function call (i.e., in Abstract Wikipedia), consisting in the Semantic unit representing a part of the article (indicatively, a paragraph), * the input coming from the previous renderer, consisting in 2 inputs: ** the abstract content that the previous renderer decided not to render, ** the context (initially created on Abstract Wikipedia and passed to the first renderer as an input), updated by all the rederers that have executed previously. The renderer would then execute, providing three outputs: * the HTML containing the rendered abstract content that the renderer decided to render, * the abstract content (Semantic unit) that for some reasons it may decide not to render and to pass to the next renderer, * the context, updated by the renderer itself. The first output would go directly to compose the Abstract Wikipedia article, while the other 2 outputs will be used as inputs by the next renderer. At the end of the chain, a "Final renderer" would render the eventual abstract content that has not been rendered yet. While it is already technically possible to implement this chain on Wikifunctions, it would be a single function call, and, like the previous proposal, it would suffer from the issue that it would need to generate the entire article in one go. The real advantage of this proposal would come if, instead of being implemented by a regular function, it was implemented through a magical function that would execute the renderers sequentially, giving each one the complete function execution timeout, collecting the partial outputs (and showing the partial generated output directly in the page) and passing the internal outputs to the next renderer, alongside the new external input. === Pros === * It would have all the advantages of the Semantic unit architectures, and still give at least partial outputs in a reasonable time (limiting timeouts). * Even if it doesn't allow the constructors to know all the abstract content that eventually will need to be rendered, it still gives them a quantity of foreknowledge that should be enough for practical purposes, while mantaining all the necessary memory of the previous content. After all, this is more or less the same type of knowledge humans have while generating linguistic content. === Cons === * It is not currently implementable, since it requires a magic function that has a special behavior. * It requires rendering partial abstract content in discrete sequential chunks, without the possibility to refine them once more abstract contentent is rendered. However, as mentioned before, realistically this should not be a problem, since the quantity of foreknowledge that renderers have available (i.e., the content of the entire paragraph) should be enough for all practical purposes. === Comments === 59rjgcf51woxnfzz2uvywrcfjqm3siv 7658 7657 2026-05-11T21:49:46Z YoshiRulz 640 /* Modest improvement to current architecture using spans */ Add diagram 7658 wikitext text/x-wiki This page proposes to discuss the possible different architectures in which the generation of an Abstract Wikipedia article can be organized. The main issues are how to handle context, and how to keep execution times reasonable. Pleas feel free to improve this page, to comment below the architecture sections, and to add your own alternative proposals. == Current architecture == [[File:Simple fragments.svg|frame]] This architecture is the currently used one: an Abstract Wikipedia article is the collection of multiple fragments, that are inserted in the article as single function calls. The different types of sentence are encoded as call to different functions, with the content encoded by the function parameters. Each fragment is independent from the other. Currently fragment generating functions output monolingual texts, that then need to be converted into HTML code; it is possible to also define fragment generating functions that directly output HTML code, in order to include formattings/wikilinks/etc. === Pros === * Being the current architecture, it is already supported. * For each "fragment" a different function is called, allowing fast-executing functions and to parallelise the generation of an Abstract article. ** Note that, with the current implementation, this advantage disappears when multiple fragments are grouped in paragraphs or other text-organizing functions. * Somewhat intuitive both for Abstract Wikipedia editors and for Functioneers. === Cons === * Each type of sentence requires the definition of its own function. Considering that even simple sentences can have multiple combinations, the number of needed functions would undergo to combinatoric explosion. ** Also note that each function needs to be singularly implemented in each language, with little possibility of code reuse. It would be almost impossible for smaller languages to keep up with the implementation of an ever growing number of fragments. * Each fragment would be generated without any knowledge of the global context. Considering that natural languages heavily rely on context, the generation of grammatical and somewhat natural-looking text would become impossible with articles with more than 2-3 sentences. * Currently, the fragment generating functions are very vaguely defined: they are basically defined through the English translation of the fragment, introducing a heavy bias towards English and Indo-European languages, as can be proved for example by the fact that [[f:Z26039]] and [[f:Z26095]] are different functions, while [[f:Z26570]] does not define in which sense the entity is in the location (is it in the geographical area? physically inside the building? near the location?). ** Note that this con can be resolved by a better redefinition of the fragments. This would still cause the definition of hyper-specific fragment functions, with the consequent lost of intuitivity and the already mentioned combinatorial explosion. === Comments === == Modest improvement to current architecture using spans == [[File:NLG object architecture under modest improvement.svg|right|x200px]] tl;dr: Do all linguistic processing on plaintext (Z11/Monolingual text), but keep track of which span(s) in the string corresponds to each Item from the outer callsite. Then that outer Function can format and linkify the final string by iterating those ranges as ordered by their start index. {| class="wikitable mw-collapsible mw-collapsed" ! (Existing types, for completeness) |- | <syntaxhighlight lang="rust"> type WFString = Z6; type MonolingualText = Z11; // = Pair<Langcode, WFString> type Langcode = Z60; type HTMLFragment = Z89; type List<E> = Z881<E>; type Pair<F, S> = Z882<F, S>; type Map<K, V> = Z883<K, V>; // = List<Pair<K, V>> w/ key uniqueness invariant type WDItem = Z6001; type WDItemRef = Z6091; type Natural = Z13518; </syntaxhighlight> |} <syntaxhighlight lang="rust"> type Span = Pair<Natural, Natural>; type Multimap<K, V> = Map<K, List<V>>; // = List<Pair<K, V>> w/o key uniqueness invariant type NLGOutput = Pair<MonolingualText, Multimap<WDItemRef, Span>>; type RichTextTransform = fn(HTMLFragment) -> HTMLFragment; type SuperlativeInLocationDefiningSentence<R> = fn( subject: WDItemRef, class: WDItemRef, location: WDItemRef, characteristic: WDItemRef, displayLang: Langcode, ) -> R; pub static superlativeInLocationDefiningSentence: SuperlativeInLocationDefiningSentence<HTMLFragment> = |subj, class, loc, charc, lang| applyFormatting( toSentenceCaseAndAddPunctuation( (match lang { Langcode("en", _) => enSuperlativeInLocationDefiningSentence, _ => todo!(), })(subj, class, loc, charc, lang), lang ), Multimap([ createArticleSubjectEmphasisTransformation(subj), createLinkifyTransformation(class, awArticleLinkFor(class)), createLinkifyTransformation(loc, awArticleLinkFor(loc)), ]) ); pub static toSentenceCaseAndAddPunctuation: (NLGOutput, Langcode) -> NLGOutput = todo!(); pub static createArticleSubjectEmphasisTransformation: (WDItemRef) -> RichTextTransform = |item| Pair(item, |innerHTML| HTMLFragment(format!("<strong>{innerHTML}</strong>"))); pub static awArticleLinkFor: (WDItemRef) -> WFString = |item| format!("https://abstract.wikipedia.org/wiki/{item.qid}"); pub static createLinkifyTransformation: (WDItemRef, WFString) -> RichTextTransform = |item, linkTarget| Pair(item, |innerHTML| HTMLFragment(format!("<a href=\"{linkTarget}\">{innerHTML}</a>"))); pub static applyFormatting: (NLGOutput, Multimap<WDItemRef, RichTextTransform>) -> HTMLFragment = todo!(); // handwaving, but it would split the Monolingual text in the 1st arg's first item based on the spans from the 1st arg's second item, convert them to HTML fragments, then apply each of the transformations from the 2nd arg </syntaxhighlight> {| class="wikitable mw-collapsible mw-collapsed" ! (The implementation <code>enSuperlativeInLocationDefiningSentence</code>, as an example) |- | <syntaxhighlight lang="rust"> pub static enSuperlativeInLocationDefiningSentence: SuperlativeInLocationDefiningSentence<NLGOutput> = |subj, class, loc, charc, lang| { let words = [ labelFor(subj, lang), enCopulaFor(subj), MonolingualText(lang, "the"), enSuperlativeFor(charc), labelFor(class, lang), enPrepositionForLoc(loc), labelFor(loc, lang), ]; NLGOutput( MonolingualText(lang, words.join(" ")), [ // Rust is 0-indexed, but there's probably a bunch of errors here anyway, so don't copy it Span(subj, 0..words[0].length), Span(class, (4 + &words[0..=3].iter().map(|&text| text.length).sum()) ..(4 + &words[0..=4].iter().map(|&text| text.length).sum())), Span(loc, (6 + &words[0..=5].iter().map(|&text| text.length).sum()) ..(6 + &words[0..=6].iter().map(|&text| text.length).sum())), Span(charc, (3 + &words[0..=2].iter().map(|&text| text.length).sum()) ..(3 + &words[0..=3].iter().map(|&text| text.length).sum())), ] ) }; </syntaxhighlight> |} === Pros === * The existing corpus of NLG Functions can be either kept as-is (e.g. inflection helpers) or migrated piecemeal (sentence-generating Functions). * This texts+spans structure puts to rest the question of which Type to use for the outputs of sentence-generating Functions: Z11, not Z89 (and definitely not Z6). === Cons === * Inherits the m&ndash;n problem of the status quo: each sentence-generating Function still needs an Implementation in every language. There's no new affordance for constructing grammatically correct sentences from smaller fragments. * Inherits other problems of the status quo, covered in [[#Current architecture]] above. === Comments === (With apologies to non-Rust programmers for its use here as a statically-typed lingua franca, and with apologies to Rust programmers for weird or broken syntax. I know <code>pub fn &lt;identifier&gt;</code> exists.) <br>This outlines what I foresee as the most evolved form of the current architecture, and is an expansion of [[f:WF:Type_proposals/Syntactic_table#c-YoshiRulz-20260403175300-Comments|my offhand comment here]]. <br>I'm only offering this as a "baseline", I can't advocate its adoption (except as a stop-gap, since as mentioned above it does solve the return type problem). Personally, I want to see an architecture which can attain prose, or something close to it, in most of the world's languages. <br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 21:26, 11 May 2026 (UTC) == Semantic unit architecture == This architecture is the architecture explained in the Wikifunctions type proposal for [[f:Wikifunctions:Type proposals/Semantic unit|Semantic units]] by user [[User:Mahir256|Mahir256]] (see [[f:Wikifunctions:Type_proposals/Semantic_unit/Douglas_Adams|the example]] to better understand how the encoding of abstract content and of context would work). The architecture explained here is mostly taken from the article [https://journals.sagepub.com/doi/full/10.3233/SW-243564#x1-14001-4], with some minor tweaking to accomodate to the actual needs of Abstract Wikipedia. [[File:Semantic unit.svg|frame]] The entire Abstract article would be generated in a single function call. The input would be the entire abstract content enclosed in a "context", that would encode all the meta-information that is necessary for the generation of the article (like the references to all the real-life objects that do not have a QID that uniquely identifies them). The (really simplified) rendering process would be as follows: # The abstract article is converted by rendering functions to a syntactic tree, i.e. a tree encoding the lexemes that are present in the sentence and the mutual relation between them. The rendering function acts on a single semantic unit (i.e., a node of the abstract article tree), and recursively calls the rendering functions acting on the child semantic units. # The syntactic tree is rendered into the final HTML article. This renderer comprises various steps, that generally require a complete traversal of the entire syntactic tree or of the internal partial representation. === Pros === * It is an architecture that allows the creation of a cohesive text, thanks to the support of a shared context. It also allows more freedom for the language-specific renderers to organize the text in a way that makes more sense to the specific language. * Since the abstract content is encoded as a tree, it prevents the combinatoric explosion of constructor types and of needed implementations. === Cons === * The generation of an entire article with a single function call is now not possible, due to the prohibitively high execution times. This architecture does not allow to parallelise the generation of an article, or just to progressively generate the article in a progressive fashion. * The learning curve would initially be very steep both for Abstract Wikipedia editors and for Functioneers; after the initial difficulties, this encoding would not include any particular difficulty, and it would probably be easier to use in order to encode complex abstract content that hyper-specific fragments. === Comments === == Stream semantic units == [[File:Stream semantic unit.svg|thumb]] This architecture is based on the semantic unit architecture, but with the difference that the abstract content, instead of being completely provided in a single function call, is splitted in paragraphs. Each renderer internally would work very similarly to the renders described in the previous section. The article is generated by the concatenation of the outputs of the various renderers. Starting from the second renderer, each renderer would have two sources of inputs: * the input defined in the function call (i.e., in Abstract Wikipedia), consisting in the Semantic unit representing a part of the article (indicatively, a paragraph), * the input coming from the previous renderer, consisting in 2 inputs: ** the abstract content that the previous renderer decided not to render, ** the context (initially created on Abstract Wikipedia and passed to the first renderer as an input), updated by all the rederers that have executed previously. The renderer would then execute, providing three outputs: * the HTML containing the rendered abstract content that the renderer decided to render, * the abstract content (Semantic unit) that for some reasons it may decide not to render and to pass to the next renderer, * the context, updated by the renderer itself. The first output would go directly to compose the Abstract Wikipedia article, while the other 2 outputs will be used as inputs by the next renderer. At the end of the chain, a "Final renderer" would render the eventual abstract content that has not been rendered yet. While it is already technically possible to implement this chain on Wikifunctions, it would be a single function call, and, like the previous proposal, it would suffer from the issue that it would need to generate the entire article in one go. The real advantage of this proposal would come if, instead of being implemented by a regular function, it was implemented through a magical function that would execute the renderers sequentially, giving each one the complete function execution timeout, collecting the partial outputs (and showing the partial generated output directly in the page) and passing the internal outputs to the next renderer, alongside the new external input. === Pros === * It would have all the advantages of the Semantic unit architectures, and still give at least partial outputs in a reasonable time (limiting timeouts). * Even if it doesn't allow the constructors to know all the abstract content that eventually will need to be rendered, it still gives them a quantity of foreknowledge that should be enough for practical purposes, while mantaining all the necessary memory of the previous content. After all, this is more or less the same type of knowledge humans have while generating linguistic content. === Cons === * It is not currently implementable, since it requires a magic function that has a special behavior. * It requires rendering partial abstract content in discrete sequential chunks, without the possibility to refine them once more abstract contentent is rendered. However, as mentioned before, realistically this should not be a problem, since the quantity of foreknowledge that renderers have available (i.e., the content of the entire paragraph) should be enough for all practical purposes. === Comments === j6k6ivfho0zbpnctg8j9titur2nvq3e 5 2889 7551 2026-05-11T15:13:35Z Feeglgeef 36 /* The whole article? */ new section 7551 wikitext text/x-wiki == The whole article? == re: Semantic units, why do we ''need'' to process the whole article at once? Is that really necessary? Can't we split it up into paragraphs? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:13, 11 May 2026 (UTC) 4v35xgxxxsvwvqdeg968lmwyswz9hfb 7552 7551 2026-05-11T15:29:37Z Dv103 1247 /* The whole article? */ Reply 7552 wikitext text/x-wiki == The whole article? == re: Semantic units, why do we ''need'' to process the whole article at once? Is that really necessary? Can't we split it up into paragraphs? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:13, 11 May 2026 (UTC) :That was more or less the idea I had for another alternative architecture, that I haven't formalized yet. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:29, 11 May 2026 (UTC) 9kdr9fn4etdljm1ge56783jupmohv6k 7560 7552 2026-05-11T17:49:16Z Mahir256 62 7560 wikitext text/x-wiki == The whole article? == re: Semantic units, why do we ''need'' to process the whole article at once? Is that really necessary? Can't we split it up into paragraphs? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:13, 11 May 2026 (UTC) :That was more or less the idea I had for another alternative architecture, that I haven't formalized yet. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:29, 11 May 2026 (UTC) :The use of semantic units does not preclude introducing section/paragraph breaks, but trying to non-serially render the parts of an article would only make sense if each section/paragraph described a truly self-contained, isolated set of details/circumstances, which for an article focusing a single topic would be difficult to justify. (If you're telling a story about a {{Q|329737}}, a {{Q|160131}}, and a {{Q|1739737}}, and they're introduced in the first section/paragraph, what are you supposed to do if the system in its parallel logic starts rendering the fifth paragraph first?) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 17:49, 11 May 2026 (UTC) jmldgan8a95b7w97au3suzrl5jmvd4t 7566 7560 2026-05-11T19:12:29Z Dv103 1247 /* The whole article? */ Reply 7566 wikitext text/x-wiki == The whole article? == re: Semantic units, why do we ''need'' to process the whole article at once? Is that really necessary? Can't we split it up into paragraphs? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:13, 11 May 2026 (UTC) :That was more or less the idea I had for another alternative architecture, that I haven't formalized yet. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:29, 11 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]] @[[User:Mahir256|Mahir256]] Now I've formalized my architecture (the same one I showed in the Volunteers' Corner). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:12, 11 May 2026 (UTC) :The use of semantic units does not preclude introducing section/paragraph breaks, but trying to non-serially render the parts of an article would only make sense if each section/paragraph described a truly self-contained, isolated set of details/circumstances, which for an article focusing a single topic would be difficult to justify. (If you're telling a story about a {{Q|329737}}, a {{Q|160131}}, and a {{Q|1739737}}, and they're introduced in the first section/paragraph, what are you supposed to do if the system in its parallel logic starts rendering the fifth paragraph first?) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 17:49, 11 May 2026 (UTC) 8ge83jdv6wdcye1fbwii7uroykkh6tx 7659 7566 2026-05-12T01:29:02Z Feeglgeef 36 /* Move out of userspace? */ new section 7659 wikitext text/x-wiki == The whole article? == re: Semantic units, why do we ''need'' to process the whole article at once? Is that really necessary? Can't we split it up into paragraphs? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:13, 11 May 2026 (UTC) :That was more or less the idea I had for another alternative architecture, that I haven't formalized yet. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:29, 11 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]] @[[User:Mahir256|Mahir256]] Now I've formalized my architecture (the same one I showed in the Volunteers' Corner). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:12, 11 May 2026 (UTC) :The use of semantic units does not preclude introducing section/paragraph breaks, but trying to non-serially render the parts of an article would only make sense if each section/paragraph described a truly self-contained, isolated set of details/circumstances, which for an article focusing a single topic would be difficult to justify. (If you're telling a story about a {{Q|329737}}, a {{Q|160131}}, and a {{Q|1739737}}, and they're introduced in the first section/paragraph, what are you supposed to do if the system in its parallel logic starts rendering the fifth paragraph first?) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 17:49, 11 May 2026 (UTC) == Move out of userspace? == Shouldn't this be in the project space if you want it to be collaborative? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:29, 12 May 2026 (UTC) h1emz5raa2nwsw27pk10f4eyhutg6y5 7663 7659 2026-05-12T08:27:20Z Dv103 1247 /* Move out of userspace? */ Reply 7663 wikitext text/x-wiki == The whole article? == re: Semantic units, why do we ''need'' to process the whole article at once? Is that really necessary? Can't we split it up into paragraphs? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:13, 11 May 2026 (UTC) :That was more or less the idea I had for another alternative architecture, that I haven't formalized yet. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:29, 11 May 2026 (UTC) ::@[[User:Feeglgeef|Feeglgeef]] @[[User:Mahir256|Mahir256]] Now I've formalized my architecture (the same one I showed in the Volunteers' Corner). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:12, 11 May 2026 (UTC) :The use of semantic units does not preclude introducing section/paragraph breaks, but trying to non-serially render the parts of an article would only make sense if each section/paragraph described a truly self-contained, isolated set of details/circumstances, which for an article focusing a single topic would be difficult to justify. (If you're telling a story about a {{Q|329737}}, a {{Q|160131}}, and a {{Q|1739737}}, and they're introduced in the first section/paragraph, what are you supposed to do if the system in its parallel logic starts rendering the fifth paragraph first?) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 17:49, 11 May 2026 (UTC) == Move out of userspace? == Shouldn't this be in the project space if you want it to be collaborative? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 01:29, 12 May 2026 (UTC) :Perhaps it's better. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 08:27, 12 May 2026 (UTC) 3inxi18jd5wlkxcegij494mk5f97bs0 5 2890 7572 2026-05-11T19:37:33Z Dv103 1247 /* About emphasis */ new section 7572 wikitext text/x-wiki == About emphasis == Why should emphasis be used on Abstract Wikipedia? I don't see why normally entire sentences should be emphasized, and for single-word emphasis I think it is better to leave to the rendered the choice on how to emphasize the word. Some languages may prefer to use different ways to emphasize a single word; some languages might even choose to emphasize a concept through grammar instead of typography. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:37, 11 May 2026 (UTC) hvglmtvs9bda564n3ekfbkgfzfjdzgm 7624 7572 2026-05-11T20:43:37Z Feeglgeef 36 /* About emphasis */ Reply 7624 wikitext text/x-wiki == About emphasis == Why should emphasis be used on Abstract Wikipedia? I don't see why normally entire sentences should be emphasized, and for single-word emphasis I think it is better to leave to the rendered the choice on how to emphasize the word. Some languages may prefer to use different ways to emphasize a single word; some languages might even choose to emphasize a concept through grammar instead of typography. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:37, 11 May 2026 (UTC) :I've removed it for now, thank you for your comment. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:43, 11 May 2026 (UTC) 63771x4le0fbq2ulhca0s5lmpbazrsa 5 2891 7573 2026-05-11T19:41:45Z Dv103 1247 /* Simple sentence collective sentences */ new section 7573 wikitext text/x-wiki == Simple sentence collective sentences == I think that, for now, it shouldn't be a recommended function: it takes an arbitrary "predicate" (we haven't yet established what counts and what doesn't count as predicate) and it requires a "subject" and an "object" (which again, are language-dependent concepts, that do not work in a language-independent context). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:41, 11 May 2026 (UTC) 6t1qmdbp24nafomddy21lup65u10j2i 0 2892 7576 2026-05-11T20:24:46Z Max263 3347 created abstract article 7576 abstractwiki text/plain { "qid": "Q692", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q214917" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } ] } } } m5yjn86g0v3ziv25ocuebumw8200cm6 1198 2893 7577 2026-05-11T20:34:04Z Alfa-ketosav 3488 Created page with "Segítség:Szócikk létrehozása" 7577 wikitext text/x-wiki Segítség:Szócikk létrehozása edoc8mgnc1v5tlfmx2k64ncn6suzzgy 1198 2894 7578 2026-05-11T20:34:58Z Alfa-ketosav 3488 Created page with "Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[$1|kereséssel]] állapítható meg), kövesd [[$2|e segítséglapot]] az új elem létrehozásához." 7578 wikitext text/x-wiki Az Absztrakt Wikipédián csak Wikidata-elemmel rendelkező témákról készíthető szócikk. Ha nem szerepel a téma a Wikidatán (ez [[$1|kereséssel]] állapítható meg), kövesd [[$2|e segítséglapot]] az új elem létrehozásához. 9nw211fllj9uk6uz233w88c03hua2x1 1198 2895 7580 2026-05-11T20:35:02Z Alfa-ketosav 3488 Created page with "== Lépések ==" 7580 wikitext text/x-wiki == Lépések == a9ua3obkqoighzceckcl8fnjdbh0l9n 1198 2896 7582 2026-05-11T20:35:24Z Alfa-ketosav 3488 Created page with "A szócikk létrehozásához mehetsz a [[$1|Új absztrakt szócikk létrehozása]] linkre." 7582 wikitext text/x-wiki A szócikk létrehozásához mehetsz a [[$1|Új absztrakt szócikk létrehozása]] linkre. 34xh397oa16rmilunrhquad2qpv1wpb 1198 2897 7584 2026-05-11T20:35:30Z Alfa-ketosav 3488 Created page with "Témaválasztás" 7584 wikitext text/x-wiki Témaválasztás i6vy6b7j2sotzsw99jtt95y1240j8fg 1198 2898 7586 2026-05-11T20:35:44Z Alfa-ketosav 3488 Created page with "Írd be a kiválasztott témát, és kattints a létrehozásra." 7586 wikitext text/x-wiki Írd be a kiválasztott témát, és kattints a létrehozásra. 0entz74puy5qixwar95vhcsd47bzt39 1198 2899 7588 2026-05-11T20:35:50Z Alfa-ketosav 3488 Created page with "Üres absztrakt szócikk" 7588 wikitext text/x-wiki Üres absztrakt szócikk 0zxtjwijp9scul1d37elsgw5cx1u8oq 1198 2900 7590 2026-05-11T20:36:16Z Alfa-ketosav 3488 Created page with "Kattints a pluszjelre a részlet hozzáadásához." 7590 wikitext text/x-wiki Kattints a pluszjelre a részlet hozzáadásához. 88kv6vhx25h09e19mmz26b8kews4z4w 1198 2901 7592 2026-05-11T20:36:21Z Alfa-ketosav 3488 Created page with "Üres részlet" 7592 wikitext text/x-wiki Üres részlet lj4ifugzq88ofdqjs7c92ppdsn14auv 1198 2902 7594 2026-05-11T20:36:51Z Alfa-ketosav 3488 Created page with "Nyitott függvényválasztó" 7594 wikitext text/x-wiki Nyitott függvényválasztó 8syqkewivju5gchy0cqcl5fukenmxbv 1198 2903 7596 2026-05-11T20:36:56Z Alfa-ketosav 3488 Created page with "Ez megnyitja a függvényválasztót." 7596 wikitext text/x-wiki Ez megnyitja a függvényválasztót. f4lki031zt12q7utci471ub9mtikul4 1198 2904 7598 2026-05-11T20:37:00Z Alfa-ketosav 3488 Created page with "Függvényválasztás" 7598 wikitext text/x-wiki Függvényválasztás 50a7nrqsax9xg09ail8j5xiuxhl4fpp 1198 2905 7600 2026-05-11T20:37:53Z Alfa-ketosav 3488 Created page with "Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterlánc alakítása HTML-részletté” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását." 7600 wikitext text/x-wiki Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterlánc alakítása HTML-részletté” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. 504enykg0pjs5s9xuzc9ejoqwmcgorv 7602 7600 2026-05-11T20:38:08Z Alfa-ketosav 3488 7602 wikitext text/x-wiki Kiválasztunk egy függvényt Ennek a Wikifunkciókon létező függvénynek kell lennie, és itt HTML-részletet kell kiadnia. E példában a „karakterláncból HTML-részlet” függvényt választjuk, mert lehetővé teszi karakterlánc vagy karakterláncot adó függvény választását. s15wrr1tvxr9xh49wrn8tgx657ljxct 1198 2906 7604 2026-05-11T20:38:17Z Alfa-ketosav 3488 Created page with "„Karakterláncból HTML-részlet” függvény kiválasztva" 7604 wikitext text/x-wiki „Karakterláncból HTML-részlet” függvény kiválasztva hbqlc8ed1ycgx0hr4b92hk57nbe53ga 1198 2907 7607 2026-05-11T20:40:04Z Alfa-ketosav 3488 Created page with "Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki." 7607 wikitext text/x-wiki Kiválasztottunk egy függvényt. A paraméterekhez mezőket kaptunk. A karakterlánc beírása helyett másik függvényt választunk ki. qugpwjv6ol0bx0u9ecl8863gqgsidj8 1198 2908 7609 2026-05-11T20:40:10Z Alfa-ketosav 3488 Created page with "Paramétermód változtatása" 7609 wikitext text/x-wiki Paramétermód változtatása 2ls38rbrxl8vcmocpu8i9zi404ga7bw 1198 2909 7611 2026-05-11T20:40:52Z Alfa-ketosav 3488 Created page with "Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást." 7611 wikitext text/x-wiki Ehhez a karakterlánc-paraméter módját megváltoztatjuk a mellette lévő 3 pontra kattintva. Ez lehetővé teszi a jelenlegi literálmódról a függvényhívásra váltást. ie3mnolaa90s9zrlxc3n3vg03rp6zq2 1198 2910 7613 2026-05-11T20:40:58Z Alfa-ketosav 3488 Created page with "Belső függvény kiválasztása" 7613 wikitext text/x-wiki Belső függvény kiválasztása a0i4px16pcm6b9gxt0mfo2zi2jn2aoy 1198 2911 7616 2026-05-11T20:41:10Z Alfa-ketosav 3488 Created page with "Most kiválaszthatunk egy karakterláncot adó függvényt." 7616 wikitext text/x-wiki Most kiválaszthatunk egy karakterláncot adó függvényt. 7je3wf3y9drj5jptfpq35018kbqxo7o 1198 2912 7618 2026-05-11T20:41:18Z Alfa-ketosav 3488 Created page with "Karakterláncot adó függvény kiválasztása" 7618 wikitext text/x-wiki Karakterláncot adó függvény kiválasztása 3ja8vltdbl9b1137bcmhnbybj6k9csu 1198 2913 7620 2026-05-11T20:42:22Z Alfa-ketosav 3488 Created page with "A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását." 7620 wikitext text/x-wiki A „Névelő nélküli leíró részlet” függvényt választjuk – ez „Párizs város.” formátumú mondatokat alkot. Megjegyzendő, hogy a „Névelő nélküli leíró részlet” függvény lehetővé teszi a „Karakterláncból HTML-részlet” függvény kihagyását. 6cgced534lntmlbb3lvic0bngrddpa2 1198 2914 7622 2026-05-11T20:42:44Z Alfa-ketosav 3488 Created page with "Névelő nélküli leíró részlet függvény paraméterei" 7622 wikitext text/x-wiki Névelő nélküli leíró részlet függvény paraméterei pagl2ncuptac14kgvyvi9rvndov87lp 1198 2915 7625 2026-05-11T20:43:37Z Alfa-ketosav 3488 Created page with "Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre." 7625 wikitext text/x-wiki Most láthatók a függvény paraméterei. Az automatikusan megadott paraméterek kitöltése is megtörtént. Ez a „Párizs Párizs.” mondatot eredményezi, mert az entitás és osztály paramétereket is a leírni kívánt elem tölti ki előre. c53ftbtttrrlb5i342qty6vvri0ouu5 1198 2916 7627 2026-05-11T20:43:51Z Alfa-ketosav 3488 Created page with "Osztályparaméter módjának megváltoztatása" 7627 wikitext text/x-wiki Osztályparaméter módjának megváltoztatása avdwnbg2xmyqitq0x8ocinnm57n9frz 1198 2917 7629 2026-05-11T20:44:13Z Alfa-ketosav 3488 Created page with "Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni." 7629 wikitext text/x-wiki Az osztályparaméter módját az automatikusan kitöltött értékről (argumentumhivatkozás) literálra kell cserélni. rg1w16yuznft2x9levozttoyyyriiyj 4 2918 7634 2026-05-11T20:52:02Z Feeglgeef 36 +redirect 7634 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style]] l825zt0hx5qbr7sk02j5lu70m5izf6t 1198 2919 7635 2026-05-11T20:54:17Z Alfa-ketosav 3488 Created page with "Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom." 7635 wikitext text/x-wiki Új képernyő jelenik meg. Jobboldalt a kiválasztott nyelvi előnézet van, baloldalt az absztrakt tartalom. ggu6l7t0x3smpp26u86dd4d3vymy8cw 1198 2920 7637 2026-05-11T20:54:45Z Alfa-ketosav 3488 Created page with "Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá." 7637 wikitext text/x-wiki Kattints a balra található pluszjelre az új részlet hozzáadására. Most üres részletet adunk hozzá. syajr2ai83wjxnhug2c1h18xqpavb9q 4 2921 7639 2026-05-11T20:55:00Z Feeglgeef 36 +redirect 7639 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style#Section organization]] 0p0mkviw2midr9t1goe7057521du83d 4 2922 7640 2026-05-11T20:55:25Z Feeglgeef 36 +redirect 7640 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style#Section headings]] q3sl7dinabli7wvkrzj6ignjhdiuhnr 1198 2923 7641 2026-05-11T20:55:26Z Alfa-ketosav 3488 Created page with "Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk." 7641 wikitext text/x-wiki Ez így néz ki, függvényhívásként kiválasztott függvény nélkül. A piros „Függvény kiválasztása” szöveg melletti nyílra kattintunk. as44bik8rs1l8okpmm43i1nhovfa0rp 4 2924 7643 2026-05-11T20:56:20Z Feeglgeef 36 +redirect 7643 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style#Quotations]] codjt8iky2pwp9bxxhp62btf3gcvfq1 1198 2925 7644 2026-05-11T20:56:24Z Alfa-ketosav 3488 Created page with "Ennek kiválasztásakor az első mondatnak késznek kell lennie. Megnyomhatjuk a „Közzététel” gombot, elérhetővé téve a cikk első változatát. Továbbiak hozzáadásához kattinthatsz a „Szerkesztés” gombra." 7644 wikitext text/x-wiki Ennek kiválasztásakor az első mondatnak késznek kell lennie. Megnyomhatjuk a „Közzététel” gombot, elérhetővé téve a cikk első változatát. Továbbiak hozzáadásához kattinthatsz a „Szerkesztés” gombra. jq4jdtagwqe3z9wsllc8hclhldj8g8l 4 2926 7646 2026-05-11T20:57:22Z Feeglgeef 36 Redirected page to [[Abstract Wikipedia:Manual of Style#Links]] 7646 wikitext text/x-wiki #REDIRECT [[Abstract Wikipedia:Manual of Style#Links]] f9cncmkj8727vyukklgxfanl6o2jxc6 1198 2927 7647 2026-05-11T20:58:04Z Alfa-ketosav 3488 Created page with "Bár a Wikimédia Alapítvány fejlesztői csapata az első megközelítésre összpontosít (és mindig támogatja az UX-ötleteket), a közösség a Wikifunkciókon a teljesebb és könnyebben használható függvénykatalógusért tehet. Itt látható a függvények és paraméterek megnevezésének fontossága, és hogy valószínűleg szeretnénk elkerülni a túl sok egyik típust másikká alakító függvény használatát." 7647 wikitext text/x-wiki Bár a Wikimédia Alapítvány fejlesztői csapata az első megközelítésre összpontosít (és mindig támogatja az UX-ötleteket), a közösség a Wikifunkciókon a teljesebb és könnyebben használható függvénykatalógusért tehet. Itt látható a függvények és paraméterek megnevezésének fontossága, és hogy valószínűleg szeretnénk elkerülni a túl sok egyik típust másikká alakító függvény használatát. 00x610c1dyic6bjajthcmqu4h3p9rx9 4 2928 7649 2026-05-11T20:58:43Z Feeglgeef 36 +redirect 7649 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style#Paragraphs]] i1ahge4jov6t2nxb6tpmofbr35i22ff 1198 2929 7650 2026-05-11T20:59:07Z Alfa-ketosav 3488 Created page with "De igen, ami a legfontosabb, az Absztrakt Wikipédia jelenleg korai nyilvános béta állapotban van, és jelenleg nehéz a cikkek létrehozása és szerkesztése. Mindannyiunknak együtt kell működni ennek javításában. Ha vannak új függvényötleteid, tedd fel őket javaslatra a [[$1|Kért függvények]] listáján." 7650 wikitext text/x-wiki De igen, ami a legfontosabb, az Absztrakt Wikipédia jelenleg korai nyilvános béta állapotban van, és jelenleg nehéz a cikkek létrehozása és szerkesztése. Mindannyiunknak együtt kell működni ennek javításában. Ha vannak új függvényötleteid, tedd fel őket javaslatra a [[$1|Kért függvények]] listáján. k8l89j3v4v8uu12vhiuf2028zqlskia 4 2930 7652 2026-05-11T20:59:26Z Feeglgeef 36 +redirect 7652 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style#Functions]] j41lx1r7i6fg82s89j3bwk9srp0gco6 4 2931 7655 2026-05-11T21:05:18Z Feeglgeef 36 Redirected page to [[Abstract Wikipedia:Manual of Style#Monolingual content]] 7655 wikitext text/x-wiki #REDIRECT [[Project:Manual of Style#Monolingual content]] gv290bsyoflhryo5qclr1m4z5xhohu5 0 2932 7660 2026-05-12T03:11:08Z Dapper-wp 3646 Create article describing Elon Musk as a businessperson 7660 abstractwiki text/plain { "qid": "Q317521", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z32123", "Z32123K1": { "Z1K1": "Z7", "Z7K1": "Z27868", "Z27868K1": { "Z1K1": "Z7", "Z7K1": "Z26039", "Z26039K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z26039K2": { "Z1K1": "Z6091", "Z6091K1": "Q43845" }, "Z26039K3": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } } } ] } } } obau6qhy6f8kob9243dmqatjiafhg4u 0 2933 7662 2026-05-12T08:00:40Z Siam2019 2521 Created page with "{ "qid": "Q1861", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1"..." 7662 abstractwiki text/plain { "qid": "Q1861", "sections": { "Q8776414": { "index": 0, "fragments": [ "Z89", { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q5119" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q869" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, { "Z1K1": "Z7", "Z7K1": "Z29749", "Z29749K1": { "Z1K1": "Z7", "Z7K1": "Z28016", "Z28016K1": { "Z1K1": "Z18", "Z18K1": "Z825K1" }, "Z28016K2": { "Z1K1": "Z6091", "Z6091K1": "Q51929311" }, "Z28016K3": { "Z1K1": "Z6091", "Z6091K1": "Q869" }, "Z28016K4": { "Z1K1": "Z18", "Z18K1": "Z825K2" } }, "Z29749K2": { "Z1K1": "Z18", "Z18K1": "Z825K2" } } ] } } } 5yf75vjciaird0lfdhka77mzsqbteev