I realize I was very vague. I don't have a concrete suggestion, but 
github/pull request/jekyll/pandoc plus the fact that I'm not well 
acquainted with any of the steps was just too much. If I remember correctly 
I got as far as producing an error message in Jekyll and eventually 
giving up the whole thing.

Chris: If it could boil down to basically editing a .bib in the browser or 
comparable, that would be just amazing.

I'm raising the question, I don't have answers though...

Den tisdag 20 september 2016 kl. 21:48:06 UTC+2 skrev Chris Rackauckas:
> I think he's talking about the fact that this specifically is more than 
> Github: it also requires using pandoc and Jekyll: 
> https://github.com/JuliaLang/julialang.github.com/tree/master/publications 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FJuliaLang%2Fjulialang.github.com%2Ftree%2Fmaster%2Fpublications&sa=D&sntz=1&usg=AFQjCNFzbEE5GBkf-Is3hQUfWpSbw_Y7Ug>
> If the repo somehow ran a build script when checking the PR so that way 
> all you had to do was edit the .bib and index.md file, that probably 
> would lower the barrier to entry (and could be done straight from the 
> browser). That would require a smart setup like what's done for building 
> docs, and probably overkill for this. It's probably easier on the 
> maintainer side just to tell people to ask for help. (And it's better to 
> keep it as a .bib instead of directly editing the Markdown/HTML so that way 
> formatting is always the same / correct).
> On Tuesday, September 20, 2016 at 12:14:21 PM UTC-7, Tony Kelman wrote:
>> What do you propose? Github is about as simple as we can do, considering 
>> also the complexity of maintaining something from thr project side. There 
>> are plenty of people around the community who are happy to walk you through 
>> the process of making a pull request, and if it's not explained in enoug 
>> detail then we can add more instructions if it would help. What have you 
>> tried so far?

Reply via email to