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
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. TODO items for www.fsfeurope.org web pages (unsorted):
  2. * Have the "Fellowship" link from the FSFE
  3. front page link to the language-specific Fellowship page, similar to what is
  4. used for every "normal" FSFE page link. That is,
  5. http://fellowship.fsfe.org/index.fi.html instead of http://fellowship.fsfe.org/
  6. when using http://fsfe.org/index.fi.html.
  7. * Have a list of volunteers on /contribute/web, /contribute/translators, and
  8. /contribute/booth to give better credit to permanent volunteers. Should be
  9. done with name lists which are stored in a language indepenedent file and
  10. included dynamically with <dynamic-content>. At the same time, remove
  11. volunteers from /about/team to avoid confusion.
  12. * Change all .xsl scripts to use <dynamic-content> instead of just appending
  13. the dynamic content to the end of the body.
  14. * Make sure all non-dynamic *.xhtml files have a proper <timestamp> tag.
  15. * Validate all HTML pages with validator.w3.org (is this scriptable?)
  16. * Make sure all documents are linked from /documents/documents whenever this
  17. makes sense.
  18. * Include a dynamic document list on the project pages using <dynamic-content>.
  19. This will make it easier to add a new document related to a project.
  20. * Include a dynamic news and events list on the project pages for those
  21. projects where it makes sense.
  22. * Include a dynamic leaflet list on the project pages for those projects that
  23. have leaflets.
  24. * Check all pages for outdated content and update them to be current. This is
  25. certainly one for a rainy Sunday afternoon :-)
  26. * Clean up .symlinks (actually they should be replaced by .htaccess redirects)
  27. * Move files from /documents that actually belong to a project to their
  28. respective /projects/* directory (for example wiwo). Or into other
  29. directories like /about/, ... Don't forget to add a redirect to not break old
  30. external links!
  31. * Search the whole tree for broken links, external as well as internal (is this
  32. scriptable?)
  33. * Create "braglist" (list of projects and documents) on personal pages (like
  34. /about/greve) dynamically from document and project .xml files. Requires
  35. adding an "author=" to documents and a "coordinator=" to projects.
  36. * Scan the apache log for 404 errors resulting from external links and help
  37. avoid them by adding page redirects.
  38. * Make a separate page per year for news and events.
  39. * Find some smart solution for page groups that have a kind of local menu in
  40. [...] at the top of each page (like projects/swpat/* or projects/ftf/*)
  41. * Find a better alternative for the focus system. Maybe just create different
  42. versions of these pages that are sensitive to focus (actually only news,
  43. events, projects, and documents lists)
  44. * in internal/er.en.xhtml, allow for manual entry of name and email address
  45. additionally to the possibility to select from the dropdown.
  46. * in internal/er.en.xhtml, allow for presetting of fields through URL, like
  47. http://www.fsfeurope.org/internal/er?budget=GENERAL
  48. * Add id to RSS so caching readers replace old versions of a news entry or
  49. event with the new version istead of just adding the new version. The id
  50. should be the same for all languages, so changing from untranslated to
  51. translated shouldn't change the id.
  52. * Create a table of content if there are more then 4 headlines on one page
  53. (like mediawiki does in its defaults)
  54. * Create a "quick links" page with interesting internal and external links.
  55. * Change the names on http://www.fsfe.org/contact/local.en.html from plain text
  56. to links like on http://www.fsfe.org/about/team.en.html?
  57. * ONLY IF EVERYTHING ELSE IS DONE: think about new TODO items ;-)