Change Details

**Feature summary**: Utilise a single local CSS file within other files, without needing to replicate its content; nor have the file centrally lodged in wiki's common.js **Steps to reproduce** (a list of clear steps to create the situation that made you report this, including full links if applicable): **Use case(s)** (describe the actual underlying problem which you want to solve, and not only a solution): * At English Wikisources we have CSS pages to our Index: ns pages that allow for CSS to created that applies to the pages of the related work in the Page: ns and hence when transcluded to main namespace. (our new feature through ProofreadPage) ** Example : https://en.wikisource.org/wiki/Index:My_Life_in_Two_Hemispheres,_volume_1.djvu/styles.css ==> https://en.wikisource.org/wiki/My_Life_in_Two_Hemispheres * Numbers of 19th and 20th century works can have multiple volumes of work or a variety of reasons. Similarly compilation and serial publications have multiple volumes, example a biographical series has over 70 volumes, so 70 Index: ns pages. Imagine how it is for journals, etc. Recreating the same CSS across 70 files is not only time-consuming in the first instance, but also if one needs to update the code that it needs to be replicated across the remainder of the css files of the series of works. Putting the respective cssof multiple works into common.js is not particularly a sustainable approach, and will lead to (further?) CSS bloat. What would be useful is if we were able to set up one of the Index:...css files to have the css code for the work, and then allow a **local** import of that file into the respective Index: files of the series. Still a little time-consuming, though not overburdening at an intial set up time, and could be bot'd at the original configuration.

**Feature summary**: Utilise a single local CSS file within other files, without needing to replicate its content; nor have the file centrally lodged in wiki's common.js **Steps to reproduce** (a list of clear steps to create the situation that made you report this, including full links if applicable): **Use case(s)** (describe the actual underlying problem which you want to solve, and not only a solution): * At English Wikisources we have CSS pages to our Index: ns pages that allow for CSS to created that applies to the pages of the related work in the Page: ns and hence when transcluded to main namespace. (our new feature through ProofreadPage) ** Example : https://en.wikisource.org/wiki/Index:My_Life_in_Two_Hemispheres,_volume_1.djvu/styles.css ==> https://en.wikisource.org/wiki/My_Life_in_Two_Hemispheres * Numbers of 19th and 20th century works can have multiple volumes of work or a variety of reasons. Similarly compilation and serial publications have multiple volumes, example a biographical series has over 70 volumes, so 70 Index: ns pages. Imagine how it is for journals, etc. Recreating the same CSS across 70 files is not only time-consuming in the first instance, but also if one needs to update the code that it needs to be replicated across the remainder of the css files of the series of works. Putting the respective cssof multiple works into common.js is not particularly a sustainable approach, and will lead to (further?) CSS bloat. What would be useful is if we were able to set up one of the Index:...css files to have the css code for the work, and then allow a **local** import of that file into the respective Index: files of the series. Still a little time-consuming, though not overburdening at an intial set up time, and could be bot'd at the original configuration. I m only looking for the import to be of another **css-sanitized** file, not of css files from anywhere else on the wiki

**Feature summary**: Utilise a single local CSS file within other files, without needing to replicate its content; nor have the file centrally lodged in wiki's common.js **Steps to reproduce** (a list of clear steps to create the situation that made you report this, including full links if applicable): **Use case(s)** (describe the actual underlying problem which you want to solve, and not only a solution): * At English Wikisources we have CSS pages to our Index: ns pages that allow for CSS to created that applies to the pages of the related work in the Page: ns and hence when transcluded to main namespace. (our new feature through ProofreadPage) ** Example : https://en.wikisource.org/wiki/Index:My_Life_in_Two_Hemispheres,_volume_1.djvu/styles.css ==> https://en.wikisource.org/wiki/My_Life_in_Two_Hemispheres * Numbers of 19th and 20th century works can have multiple volumes of work or a variety of reasons. Similarly compilation and serial publications have multiple volumes, example a biographical series has over 70 volumes, so 70 Index: ns pages. Imagine how it is for journals, etc. Recreating the same CSS across 70 files is not only time-consuming in the first instance, but also if one needs to update the code that it needs to be replicated across the remainder of the css files of the series of works. Putting the respective cssof multiple works into common.js is not particularly a sustainable approach, and will lead to (further?) CSS bloat. What would be useful is if we were able to set up one of the Index:...css files to have the css code for the work, and then allow a **local** import of that file into the respective Index: files of the series. Still a little time-consuming, though not overburdening at an intial set up time, and could be bot'd at the original configuration. I m only looking for the import to be of another **css-sanitized** file, not of css files from anywhere else on the wiki