diff options
author | ailin-nemui <ailin-nemui@users.noreply.github.com> | 2017-06-26 12:45:35 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-06-26 12:45:35 +0200 |
commit | 285ff64480eeed66217d82b1f1117cb3d7be18a6 (patch) | |
tree | 956f2ee9985748727fc472801515e809199fef9a | |
parent | 42a4eeee370cf450693b422fde162b6c5c8ab843 (diff) | |
download | irssi.github.io-285ff64480eeed66217d82b1f1117cb3d7be18a6.zip |
Update README.markdown
-rw-r--r-- | README.markdown | 41 |
1 files changed, 3 insertions, 38 deletions
diff --git a/README.markdown b/README.markdown index 273e5ad..1254c61 100644 --- a/README.markdown +++ b/README.markdown @@ -1,43 +1,8 @@ Irssi.org ========= -We need a new shiny website! We would like help with that. We want a -bootstrap-based, statically-generated, Jekyll-based website :-) +This repository holds the content of https://irssi.org. It is currently +bootstrap-based, statically-generated, Jekyll-based website hosted on +GitHub Pages :-) Join us in `#irssi` on freenode, if you are interested in helping out. - -# What do we want? - -We want to have a modern, easily updatable, website that we can use together -with our already well-functioning Github infrastructure. A contribution should -arrive as a pull-request such that our contributor team can easily review the -commits. - -Sections we need: - -- More or less everything from irssi.org (news, release information, all that - jazz). -- A way to submit articles to the website using Markdown. I'm thinking an index - page at `/articles/` and the individual articles as - `/articles/my-cool-new-irssi-feature/` where the directory contains an - index.markdown with the article itself. The individual article directory can - contain images and everything else needed to make the article look shiny. -- Fancy "how to install irssi page" with the various popular distributions - listed + how to do it directly from Git. ahf quite likes something like - https://mosh.mit.edu -- More ideas? :-) - -Things to think about: - -- [Permalinks](http://jekyllrb.com/docs/permalinks/) in jekyll are... tricky. - The best optioned seemed to be to hardcode a permalink into every page to - get [cool URIs](http://www.w3.org/Provider/Style/URI). -- While jekyll does obfuscate email addresses in markdown, this functionality - is not available in filters. Hence contributor's email addresses are - on the site. -- There was some objection to adding {{ site.baseurl }} to links in templates. - Using the `<base>` tag does not seem to be a viable option due to the - inflexible URI schemes, jekyll doesn't seem to want to generate relative - URIs it requires. - -These issues might be fixable with or without plugins. |