4. Make an infographic about the project. Could be advertisement, which compares it to competitors. Could be a Tutorial. Could be a cheetsheat. 5. Build a real

4. Make an infographic about the project. Could be advertisement, which compares it to competitors. Could be a Tutorial. Could be a cheetsheat. 5. Build a real website, if the Github project page is the current website. You should probably contact them first to check for backend technology. Not every developer likes Wordpress. 6. Bug reports about smaller design issues. Graphic designer often have good testing skills (and infrastructure?) for multiple operating systems. You can probably suggest a solution already. Examples: "The website should specify the Frutiger font for OS X, because the sans-serif fallback mixes badly with the fixed-width font." or "The navigation menu is unuseable on smartphones. Add this CSS: ..." 7. Larger projects need to integrate multiple parts (wiki,forum,bugtracker,etc) in their website. Often there is no unified theme for all components. Personally, I like lifeisstillgood's point 1 best, because you would help multiple projects at once. For example, Sphinx themes could definitely benefit from a graphic designer: http://sphinx-doc.org/theming.html http://sphinx-doc.org/theming.html