Normal internal links are not in class internal (they used to be, and still are on sites that use an older version of the software, e.g. a.internal – link to file itself (Media:), and links from thumbnail and magnifying glass icon to image description page (note that color and font size specified for a.internal are only applicable in the first case) - Media:example.a.image – link from full image to image description page.a.extiw – interwiki link in page body - en:example.a:link, a:visited - together these are all the links, as opposed to "a" elements which are just anchors - example: help:index.a - note that "a" is not always a link, in particular, the "Special page" tab is not (see Help:Namespace#Tab_labels).The css selectors, expressed in terms of elements, classes and id's, relevant for the style of the page body include: When the browser has been set to the option to ignore the font size specified in the webpage or external CSS, CSS lines regarding font size have to be put in the local CSS. In that case the user subpages allow the setting of a user style anyway. in internet cafes, do not allow users to set preferences for the browser. for a different background color for easy distinction, clearly the local CSS can not be used at least these lines should be put in the user subpages. a setting for the selector a.extiw affects fewer pages on the web than one for h2.įor lines of CSS which should be different on different MediaWiki projects, e.g. However, a setting only affects other webpages if they use the same class name e.g. Each applies to the whole world wide web, not just a MediaWiki project (and does not depend on being logged in). If one uses multiple browsers, each can be set to a different CSS. In addition to the above, or alternatively, a local CSS can be set on the browser. The applicable personal css page is User: username/ myskin.css (all lowercase!).Ĭss Css in user subpages vs. The HTML source contains lines "/w/wiki.phtml?title=User: username/standard.css&action=raw&ctype=text/css" įor the project-wide CSS for the particular skin (in this case here on Meta referring to ) and the personal JS and CSS for a particular skin.įor "MySkin" there is no main.css applicable. After saving, while still on the page or while on any other page, do a forced reload (shift-reload/ctrl-f5) to get the new files. E.g., one can preview how links in the margin will look, but these may not be of all the types one would want to check. The preview works here in a special way: it allows viewing of the margins of the page (not the contents) on the basis of the style info in the page, provided that the skin used is the skin for which the page applies. The changes are in a subpage of your user page called monobook.css and monobook.js.Īlso you can change the classic skin your subpages should be named User: username/ standard.css and User: username/ standard.js (and similar for the other skins). In the monobook skin, you can now change any aspect of the UI specified in and en:MediaWiki:Monobook.css or similar using your own Javascript or CSS. The name of the style directory is set on installation, see LocalSettings.php#Stylesheet_Location. The files in the style directory are for a given skin probably the same in each project. Css is specified with reference to selectors : HTML elements, classes and id's specified in the HTML code.Īccordingly, what the possibilities are for each skin can be seen by looking at the HTML source code of a page, in particular looking at these classes and id's: the more there are, the more versalitity there is.įor example in the English Wikipedia, the defaults are in For each skin, the user can make various choices regarding fonts, colors, positions of links in the margin, etc. 3.1 Duplicate edit links at the bottom of the content areaįor each user-definable style, a skin is first selected, and a corresponding style sheet (CSS).2.3.5 Monobook menus with serif fonts in the content area. 2.3.4 Make the quickbar float / sideboxes have fixed position.Table markup often complicates page editing. Īs a general rule, it is best to avoid using a table unless you need one. Tables redirects here for information about database table structure, see Manual:Database layout.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |