Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

web.en.xhtml 5.5KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <title>Information for Webmasters - FSFE</title>
  5. </head>
  6. <body class="article web" microformats="h-entry" id="information-webmasters">
  7. <p id="category"><a href="/contribute/">Contribute</a></p>
  8. <h1 class="p-name">Webmastering</h1>
  9. <div class="e-content">
  10. <p id="introduction" class="p-summary">
  11. The <em>Web team </em> maintain and develop the FSFE's websites —
  12. ranging from <a href="/">fsfe.org</a> to project and campaign
  13. sites. Webmasters are volunteers working to enhance the
  14. organization's face to the world, and to improve the technical
  15. solutions of our web efforts.
  16. </p>
  17. <h2>Get to know us, get to know the website</h2>
  18. <p>
  19. If you want to get an idea of what work on FSFE's website consists
  20. of, the best way is to come have a chat with us. Some of the
  21. webmasters are regularly on freenode's #fsfe channel, where we
  22. will be happy to meet you and answer your questions!
  23. To check out who is working on the website, and with
  24. FSFE as a whole, visit <a href="/about/team.html">the FSFE's team page</a> and the specific <a href="https://wiki.fsfe.org/Teams/Web">Web team page</a>.
  25. </p>
  26. <p>
  27. Your web coordinator, Paul Hänsch.
  28. </p>
  29. <h2>Introduction</h2>
  30. <p>
  31. The technologies and programs used to maintain the FSFE web page
  32. should already be familiar to many developers and authors and might be of
  33. interest to those that have not yet discovered them.
  34. </p>
  35. <p>
  36. Translators and occasional volunteers will most likely only get in touch
  37. with
  38. </p>
  39. <ul>
  40. <li>
  41. <a href="http://en.wikipedia.org/wiki/XHTML">XHTML</a> – from
  42. which the web pages are generated
  43. </li>
  44. <li>
  45. <a href="http://git-scm.com/">Git</a> – for
  46. version control of web page sources
  47. </li>
  48. </ul>
  49. <p>
  50. Volunteers interested in getting deeper into the maintenance should also
  51. be familiar with
  52. </p>
  53. <ul>
  54. <li>
  55. <a href="https://www.gnu.org/software/bash/">Bash</a> – for the maintenance
  56. and page creation scripts
  57. </li>
  58. <li>
  59. <a href="http://www.apache.org/">Apache</a> – as the web server
  60. </li>
  61. </ul>
  62. <h2 id="Understanding">Understanding how the web pages are built</h2>
  63. <p>
  64. The web pages of <var>fsfe.org</var> are maintaned as a set of
  65. XML files. The web server generates the HTML pages from these XML files
  66. automatically every ten minutes. Consequently, all editing of the pages
  67. is done in the XML files, and the HTML is never edited directly.
  68. </p>
  69. <p>
  70. Every page on fsfe.org is named
  71. <var><em>pagename</em>.<em>language</em>.html</var>
  72. (<em>language</em> being the two-letter <a
  73. href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO-639
  74. code</a> of the language, like "en" for English or "de" for German).
  75. The source files are named
  76. <var><em>pagename</em>.<em>language</em>.xhtml</var>.
  77. </p>
  78. <p>
  79. Some pages have a dynamic part: apart from the fixed texts taken
  80. from the XHTML file, they include information from one or several
  81. XML files. Whenever such a page is built, the build system takes
  82. the translated XML files where available, and falls back to the
  83. English version of those XML files that have not yet been
  84. translated. This way, such pages can end up with parts of the
  85. text being translated and other parts still showing in English.
  86. Examples of such pages include the <a href="/">start page</a>, the
  87. <a href="/news/">news page</a>, and the <a href="/events/">events
  88. page</a>.
  89. </p>
  90. <h2 id="Getting">Working with the website as an editor</h2>
  91. <p>Please visit our <a href="https://wiki.fsfe.org/TechDocs/Mainpage/Editing">website editing wiki page</a> to find more information about:</p>
  92. <ul>
  93. <li>how to copy the websites' source code to your computer</li>
  94. <li>how to edit and push files to the website</li>
  95. <li>how to coordinate with other website editors</li>
  96. <li>responsible handling of write access</li>
  97. <li>advanced webmaster techniques</li>
  98. <li>proper licencing of source code and media</li>
  99. </ul>
  100. </div>
  101. <!--/e-content-->
  102. </body>
  103. <sidebar promo="about-fsfe">
  104. <div id="related-content">
  105. <h3>Howtos:</h3>
  106. <ul>
  107. <li>
  108. <a href="/contribute/web/tagging.html">Use tags and article metadata, implement a country page</a>
  109. </li>
  110. <li>
  111. <a href="/contribute/web/css.html">Edit the CSS with LESS</a>
  112. </li>
  113. <li>
  114. <a href="/contribute/web/campaigns-frontpage.html">Add and select campaign banners for the frontpage</a>
  115. </li>
  116. <li>
  117. <a href="/contribute/template.html">A template article, to use the new webdesign</a>
  118. </li>
  119. </ul>
  120. </div>
  121. </sidebar>
  122. <tags>
  123. <tag>webmaster</tag>
  124. </tags>
  125. <timestamp>$Date$ $Author$</timestamp>
  126. </html>
  127. <!--
  128. Local Variables: ***
  129. mode: xml ***
  130. End: ***
  131. -->