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.
 
 
 
 
 
 

152 lines
5.3 KiB

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