talk to any tech writer... wiki is _NOT_ a documentation. it is the most
perverse form of somthing looking like documentation. the only thing that
wiki can be good for is to fill the time gap until "real" documentation is
produced.
i would rather see the discussion why things from wiki are not in
On 26-09-2015 08:12:30, Vladimír Čunát wrote:
> On 09/26/2015 12:07 AM, Matthias Beyer wrote:
> > I agree. I wanted to create a new organization for this and publish
> > the repository on the organizations account and github page.
> >
> > Something like github.com/nixos-wiki
> >
> > or something
Hi,
On 26-09-2015 09:04:57, Eric Sagnes wrote:
>
> I would be great to have support for i18n, including guidelines and
> workflows for foreign languages. (eg: Who with merging privileges can
> determine if a contribution in thai is not spam?)
>
I can try to work out i18n, of course.
Guideline
On 09/26/2015 12:07 AM, Matthias Beyer wrote:
> I agree. I wanted to create a new organization for this and publish
> the repository on the organizations account and github page.
>
> Something like github.com/nixos-wiki
>
> or something similar. I explicitely want _not_ to include the wiki in
> t
Hi,
A few considerations:
I would be great to have support for i18n, including guidelines and
workflows for foreign languages. (eg: Who with merging privileges can
determine if a contribution in thai is not spam?)
Git and command line can be a big hurdle for non technical users, so to
help the
On 25-09-2015 20:58:36, Nicolas Pierron wrote:
>
> Also, I wanted to mention that Github offers an option for modifying
> pages without even cloning the repository on your computer. Which
> makes this approach less painful for making contributions.
>
> https://help.github.com/articles/editing-fi
I think having a wiki in git can be a big trouble for users who don't
know where to find the "edit" / "login" buttons, but I am sure that we
can make the proper template in due time to wrap an interface around
such system.
On Fri, Sep 25, 2015 at 3:49 PM, Eelco Dolstra
wrote:
> […] But I wouldn't
+1 for hakyll.
--
Sincerely,
Arseniy Seroka
On 25 September 2015 18:07:38 Vladimír Čunát wrote:
> On 09/25/2015 04:58 PM, Jookia wrote:
>> On Fri, Sep 25, 2015 at 04:01:21PM +0200, Matthias Beyer wrote:
>>> What do you mean by proprietary tools? Jekyll, Bundler, git - all open
>>> source. Th
On 25-09-2015 17:07:23, Vladimír Čunát wrote:
>
> The point is you won't have to use github. Just edit files in your local
> checkout and commit it. For creating a PR you maybe do need it (though
> the CLI interface probably can do that as well), but that's much more of
> concern for the main nixp
On 09/25/2015 04:58 PM, Jookia wrote:
> On Fri, Sep 25, 2015 at 04:01:21PM +0200, Matthias Beyer wrote:
>> What do you mean by proprietary tools? Jekyll, Bundler, git - all open
>> source. The only thing which would be non-open source are the web
>> servers who host the generated html files and the
- Forwarded message from Jookia <166...@gmail.com> -
Date: Sat, 26 Sep 2015 00:40:38 +1000
From: Jookia <166...@gmail.com>
To: Matthias Beyer
Subject: Re: [Nix-dev] NixOS-Wiki alternative. Was: What license does the
content of the nixos wiki and the manuals have?
User-Agent:
There is also Pelican, a static site generator written in python. I
don't know how it compares to Jekyll:
http://blog.getpelican.com/
https://github.com/getpelican/pelican
--
Jascha Geerds
j...@ekby.de
___
nix-dev mailing list
nix-dev@lists.science
Hi,
On 25/09/15 16:04, Matthias Beyer wrote:
>> This is essentially how the NixOS homepage is built, i.e., a git repository +
>> Template Toolkit + a makefile. And of course you can make pull requests on
>> GitHub. But I wouldn't call that a wiki, since you can't easily edit it from
>> a
>> brow
On 09/25/2015 04:28 PM, Matthias Beyer wrote:
> and 1GB installation, as you mentioned.
>
> I used Jekyll because I don't know Haskell (I know a bit, but not
> enough) and I can see that haskell puts off a lot of people just
> because it is different. [...]
I believe we can work around those as f
On 25-09-2015 16:18:31, Vladimír Čunát wrote:
> On 09/25/2015 02:24 PM, Matthias Beyer wrote:
> > So, an idea came up - why not using static pages for all of this?
>
> Yeah, sounds good. Actually, you can edit and preview files on github
> easily - it's two clicks to get a PR with the changes (at
On 09/25/2015 04:18 PM, Vladimír Čunát wrote:
> I've got great experience with Hakyll
The only downside to Hakyll I can see is that apparently you need ~1 GB
of Haskell stuff to build the site :-/
smime.p7s
Description: S/MIME Cryptographic Signature
On Fri, Sep 25, 2015 at 11:53:24PM +1000, Jookia wrote:
> On Fri, Sep 25, 2015 at 03:49:08PM +0200, Eelco Dolstra wrote:
> > Hi,
> >
> > On 25/09/15 14:24, Matthias Beyer wrote:
> >
> > > So, an idea came up - why not using static pages for all of this? If you
> > > want to do contributions via git
On 09/25/2015 02:24 PM, Matthias Beyer wrote:
> So, an idea came up - why not using static pages for all of this?
Yeah, sounds good. Actually, you can edit and preview files on github
easily - it's two clicks to get a PR with the changes (at least markdown
is previewed).
Personally, I've got grea
On 25-09-2015 15:49:08, Eelco Dolstra wrote:
> Hi,
>
> On 25/09/15 14:24, Matthias Beyer wrote:
>
> > So, an idea came up - why not using static pages for all of this? If you
> > want to do contributions via git, you can use github. If one want to
> > host it, one can use github pages and build i
On Fri, Sep 25, 2015 at 03:49:08PM +0200, Eelco Dolstra wrote:
> Hi,
>
> On 25/09/15 14:24, Matthias Beyer wrote:
>
> > So, an idea came up - why not using static pages for all of this? If you
> > want to do contributions via git, you can use github. If one want to
> > host it, one can use github
Hi,
On 25/09/15 14:24, Matthias Beyer wrote:
> So, an idea came up - why not using static pages for all of this? If you
> want to do contributions via git, you can use github. If one want to
> host it, one can use github pages and build it with travis-ci. These
> things are documented and they _w
On 25-09-2015 12:58:14, Eelco Dolstra wrote:
> However, an alternative to relicensing is to combine it with a move to a
> different Wiki, which many people have wanted in the past anyway. For
> instance,
> we could set up a GitHub wiki, and people could copy their own contributions
> to
> the new
22 matches
Mail list logo
