editing.mdwn 2.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  1. **NOTE: Some info here is outdated. A wiki account can easily be created by
  2. clicking "Edit" in any page, which will take you to a registration form asking
  3. for username and password.**
  4. # Editing Wiki Pages
  5. This wiki is powered by the ikiwiki software.
  6. + [[ikiwiki]] page - basic documentation for ikiwiki syntax and features
  7. + [[tags]] - should be under [[ikiwiki]] but until it moves, it will be here
  8. + [[Sandbox]] - here you can try features and learn without worrying about
  9. deleting something important.
  10. + [ikiwiki website](https://www.ikiwiki.info) - full documentation
  11. + [[Help]] - aspects and guidelines specific to this wiki
  12. + [[CSS]] - the wiki's stylesheet
  13. # Creating an Account
  14. Before you can edit, you'll need to create an account. Maybe one day many people
  15. will want to participate and then registration could be made with just a
  16. username and a password, but at the moment it also requires getting a
  17. registration code, which you can get only from me. It's not a test or something:
  18. I just want to know the people with whom I work :-) and prevent spam. Yes, spam
  19. is one of the ugly sides of our society. Where is the global brotherhood?
  20. If you want to participate, talk to me face-to-face or on IRC or on Jabber or by
  21. e-mail or by I2PBote or any other way. See the [[contact]] page.
  22. # Git Commits
  23. If you prefer to edit using git - great, I prefer that too. It's much safer to
  24. use an SSH key for connecting and a PGP key for signing a commit, than just a
  25. password like the web interface. Since right now there aren't any locked pages
  26. (unless some are automatically locked, e.g. user pages), it really doesn't make
  27. much difference how you edit. I'll just need your public SSH key.
  28. All the commits to git are done with `git commit -S`, so that they're all
  29. signed. It's much more secure than letting people specify name and e-mail by
  30. themselves for each commit, risking having automatic spam pretend to be one of
  31. the team members and cause chaos in the repository. And it will hopefully allow
  32. me to accept commits by GPG trust paths in the future. For now it's just the
  33. extra -S option and either you type the GPG key password every time, or you tell
  34. your computer to remember it for you.