2 ms·
Ok, suggestions: 1. Python world has a documentation "standard" of a markdown language (ReSt) converts to HTML and LaTeX, usually through a preprocessing calle
by lifeisstillgood 14y ago
Ok, suggestions:
1. Python world has a documentation "standard" of a markdown language (ReSt) converts to HTML and LaTeX, usually through a preprocessing called sphinx that can link docs intelligently.
There are doc-a-likes in other languages (JS-docco) and they generally look boring and work-a-day.
Luckily they also have abstracted out most of the templating and css.
I suggest that initially try out writin some themes for a markdown output, but with the goal of agreeing target outputs - that is get the output from markdown for page footer to be standardised across all languages - and then there is a target HTML to aim CSS at - in the same way that there are a million themes for Wordpress because all Wordpress HTML output uses same conventions, so designers can iterate against same background, I would love to see a million themes for open documentation, knowing I could write comments and it would already be not ugly
2. Logos - yeah boring I know but everyone loves them. Offer one to any open source project and they will say yes. So run a gravatar of logos - store the png on (logotar) and link to it via the hash of the repo. Then all I need do is put link of logotar.com/md5hash.png and presto. You have a scorechart and a way to see who has logos for most popular repos and I have a logo in my readme
3. Wan to get more deeply involved in a project - do mood boards for their site or do button / widget themes (ie bootstrap alterations). In the end we developers need as much practise at getting it right as you guys
Brilliant decision to push on this - good luck
- jongold 14y agoFantastic suggestions, thank you :)
- qznc 14y ago4. 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