Subpage

“ These are:
portal, related_author wikipedia, wikispecies, commons, commonscat, wikiquote are typically applied from Wikidata data through interwiki links, or through linking of main subject (P921) so should only be used to override the default wikinews, wiktionary, wikibooks, wikiversity, meta For portal this would generally be added to the root page of a work, rather than added repeatedly for each subpage. Usage on a subpage would be useful where the subpage alone has a relationship with the specified portal, whereas the parent work does not have that relationship. ”

“ There were serious problems with page naming (one subpage called "The Critique of the Critique of Judgment" for instance, found nowhere in the work) , as well as wrong titles of parts in the table of contents. ”

“ When to create red links Main namespace Long works may start with just a table of contents, with links to each chapter as a subpage. Red links in the table show which chapters or sections have been added and so give an approximate gauge of the degree of completion. ”

“ It is now pretty much a licence for the published work, which is usually akin to what is at the root level. IIRC this was discussed as one of the advantages of the placement of works within a hierarchical representation of a publication, ie. where a poem is a subpage of a larger work, the publication covers it.This also pretty much applies for adding similar components such as year parameter, wikipedia parameter, portal parameter and category. If adding it to the top level is appropriate and there is no difference at the subpage, then no need to add further ”

“ The Style guide states that "Standalone works published as part of a collection, such as most poems, have their own pages"; whether a particular work is stand-alone depends on your judgment. I've stated my opinion (and my preference for subpages) : if you can't tell whether a work is stand-alone or not, just use a subpage with a redirect. The fact that works can be reprinted is a good reason to use subpages, since the same work printed in three different sources can be three different editions with different annotations or prefaces, every edition of which is welcome on Wikisource. ”

“ A possible solution to Allan's concern is just have the subpage (Wikisource:Legislative documents/England--or United Kingdom) , and then using headers for all the different monarchs. That still might be a bit too bulky, but then it would save us from an entire sub-page tree. I prefer to have a tree than the entire mess all on one page, but I'm willing to go either way here. But, it should be noted, that not act will be in the subpage tree; it will have its own page.—Zhaladshar (Talk) 01:04, 4 July 2006 (UTC) Ok, I had thought you were meaning to have the texts as sub-pages ”

“ Can we start with what are our principles for siting our reproduction, and then we align from there.To me a series page belong in portals, if a volume is part of a series, and exists in our space, then we can throw in a redirect. That an editor reinvigorates a work and includes it in their series is neither here nor there, it is an edition of a work unless you can find some other reason to place it as a subpage, ie. first time brought into publishing world in a language, or the works translators and some other special curatorial aspects. ”

“ This is probably how the scans are organised, the pagination shows the publishers conceived it this way. The need for subpages is based on managing page size and making use of named sections of the work; adding complexity has a benefit to the reader for this reason, i.e. they only get the desired article, nothing more. There should be just enough structure to get the sections in page order. The month of publication can be regarded as incidental and noted in the header or the page title when clarification is needed. ”

“ Linking from an index requires - Title/subpage# [anchor] | [text] - the 'anchor' and the 'text' are the page number given in the scan and adjusted at our Index. If I find an explicit internal reference in a work, I create an anchor to link it; this is not required with a work's index because the link to the Page:namespace creates an anchor in mainspace - the actual page number. Sure keeps things simple, any offset and other palaver in fixed in place and the rest looks after itself. Creating these links within a work, in mainspace, is marvellous and well worth the labour and bits of code. ”

“ Strike me stupid, have you looked at Template:header recently? Look at that huge long list and which we use. Also look at how they are marked and explained. ALSO with the header gadget, it applies year parameter to the ROOTPAGE Some dumb page, not to the subpages Some dumb page/subpage. So we manage that aspect, and ideally we minimise the data that needs to be added. For consistency we say that if it is true at the top (portals, categories) , then don't do it to the subpages, just do it when different. Links from author and portal pages should have a date against the work. ”

“ What would the consequences of a move be? I'm assuming your plan for the subpage /Pagelinks is that they be auto-generated by a script determining how the index is currently invoked to its Title/subpages, avoiding multiple uses of the same Page:space and so on, but will it build deeplinks to works that are underconstruction?
I don't know the appropriate parlance, but I'm trying to establish is what would be 'static' (needing updates or purging) and what would 'active' (resolves without intervention) . ”

“ I want make Hard Times the page that list all the versions of the work instead of containing the text of one specific edition. Languageseeker (talk) 05:53, 9 April 2021 (UTC) Then, why did you call it a "subpage"? You mean a versions page. Once we are hosting multiple versions (editions) of Hard Times, then we'll need a versions page. Until then, the single version can stay where it is and the list of other versions/editions should be on the Author: page. Generally, we prefer to avoid redlinks on the three types of disambiguation pages (disambiguation, versions, translations) . ”

“ So I think we can take our time; simply altering all 100,000 pages replacing "header2" with "header" is not worth doing. One of the expensive changes I think would be beneficial is for subpages to use a template which is mostly automated; see Template talk:Header/Archive 1#Subpages. {{subpage-header}} achieves this for simple cases, excepting that it doesnt display the author. I see three solutions: add more params to {{subpage-header}} ”

“ Then maybe I'll come to understand the Title/Volume subpage system. Klarm768 (talk) 00:33, 6 December 2017 (UTC) The point of the Title/Volume/Section system is to avoid spreading parts of a single work (single or multiple volumes) around in the mainspace, but rather have them "contained" under a single parent page. This is helpful because, at least: It's organisationally "tidier" to not spread a single work out amongst many mainspace pages There's a clear "entry point" to the work, i.e. the top level page. ”

“ Times Other works ... basically without having to generate manual pages when we have subpages. So your inputs there would be great. — billinghurst sDrewth 02:43, 15 January 2012 (UTC) You said you couldn't tell a subpage from the API, but I was able to find some good variables that do through APING my betters in Wikimedia template programming. As for these displays you want, maybe if we originated a special newspaper header, we could assign multiple categories automatically when the header detects when a certain page is down on either a root directory, a subdirectory or a sub-sub directory. ”

“ Link to a subpage Button link:
What it does: Creates a link from the highlighted text to a subpage from the current page. On the page The Double Dealer, converts the text "Act I" to " [ [/Act I|] ] ", which looks like "/Act I". The actual Wikisource link would be The Double Dealer/Act I.
mw.toolbar.addButton ({ "//upload.wikimedia.org/wikipedia/commons/0/0c/Button_Link_DifferentName.png", "Subpage", ' [ [/', '|] ] ', "Insert link here" }) Relative link Button link:
What it does: Wraps the text in a relative link ( [ [../link location/] ] ) . ”

“ I don't think there are many old pages not using the subpage format; most of those were corrected a long time ago. —{admin} Pathoschild 03:03:54, 22 May 2008 (UTC) "Corrected" is your POV" Eclecticology 08:44, 22 May 2008 (UTC) Indeed, mine and that of the various community members who agreed to enable subpage syntax on Wikisource and to implement a subpage convention, and who then manually renamed pages to conform to the standard. There are several reasons for the subpage convention we use, which the approach you advocate blocks. ”

“ You can see Index:Picturesque New Zealand, 1913.djvu for an example of both of those. For the headers, you can either fill them in by hand on each subpage, or you can transclude your pages like this: Panama.djvu" from=56 to=57 header=1 /> If the index page has a fully linked table of contents, and the gods smile on you, a header will appear by magic, with the fore- and back-links filled in for you. Inductiveload—talk/contribs 01:46, 25 December 2010 (UTC) I finally figured out how to edit headers and footers by digging into the HTML and Javascript. ”

“ I have been putting together a list here of public domain documents missing from Wikisource which are listed in various compilations of most important books/historic documents. Perhaps I should move this to a subpage of Requested texts? BD2412 T 00:23, 19 May 2010 (UTC) I like that list, and your idea of making it a subpage of Requested texts. Would it be possible to add your sources at the top? Is it an exhaustive list of works that we don't have (from those compilations, I mean) ? ”

“ Where articles are transcluded, you can get to the page from the article (either directly by clicking in the margin, or by editing the article, depending on transclusion method. With page numbers to 'bracket', bisecting the range gets you there quite quickly. We are though moving to ability to look up. Author subpage listings should have the page number in the original volume added, and knowing the "offset" you can go to the exact page directly. (I have been lent a handbook, but unfortunately it is based on the 22-volume edition so I can go directly, but at the cost of some mental arithmetic.) ”

“ Don't remove unused parameters, as these help editors use the template elsewhere.
Relative links On pages works with many subpages, using relative links is highly recommended. This shortens the code and ensures that pages remain linked together even if the overall system is moved or reorganised. The three formats are [ [/subpage] ] (subpage) , [ [../] ] (parent) , and [ [../sibling] ] (sibling) ; see the example usage below. Note that [ [../] ] will expand to the title of the parent page, which is ideal if the page is renamed at a later time. ”

“ Jonathan Swift where the main page is the title of the series, then each volume has a sub-page with sub-sub-pages for each chapter/sermon/poem/&c. In other words do what you suggest above with the exception of calling the main page a dab page. Beeswaxcandle (talk) 05:33, 19 September 2013 (UTC) I tend to do it in subpages as you mention, ie. Memoirs of James Hardy Vaux/Volume 1/Chapter 1, although I would call Memoirs of James Hardy Vaux a Table of Contents more than a disambiguation page. ”

“ Example – The following snippet of code can be used to detect if a page is a subpage by checking for the existence of at least a second part to the pagename:
{{#if:{{#titleparts:{{PAGENAME}}|1|2}} | | }} Notes ↑ An "absolute" wikilink would be, for example, [ [My Book/Chapter 2] ] , which will always link to the same page regardless of where it is on Wikisource.↑ A "relative" wikilink would be, for example, [ [../Chapter 2/] ] , which will link to the subpage "Chapter 2" of the current work. ”

“ If it's going to be subpaged, then footnotes as we've been doing them are fine because the pages won't be long. However, if you're thinking of a single page, then we could explore sidenotes. I see my role here as helping you achieve the look you want rather than telling you what to do. Beeswaxcandle (talk) 04:31, 4 March 2013 (UTC) I think the chapters are too short to have a single page each. I tried adding template:LR sidenote to one of the pages, but the notes all ran into one another. ”

“ I propose a slight change to the proposed sub-page tree, though. From the currently proposed one, I get the feeling that the actual names of the statues/acts/etc. are going to have the entire tree's path in it. I think the trees should only contain links, where the links point to pages in the main article namespace and do not have any subpages. So, I guess it would like something more like Wikisource:Legislative documents/England Wikisource:Legislative documents/England/Henry III Wikisource:Legislative documents/England/Henry IV and each of these pages contain links. ”

“ The Love of Books: the Philobiblon of Richard de Bury I have moved the subpages of this work under the title of the root page, and I have add the table of contents. It is just confusing to readers to start in one title and end up somewhere else with no clarity of reason. Also to generate digital versions of the first and subpages, we need to have the ToC so that the tool knows that the pages below it, and their links. ”