Copy docs from the main project and redo the index#15
Copy docs from the main project and redo the index#15iloveitaly merged 5 commits intoresque:masterfrom
Conversation
iloveitaly
left a comment
There was a problem hiding this comment.
Great change! Could we add that GH link back in? Otherwise, this looks great.
Next step would be pulling in the plugin wiki, and other useful wiki pages.
Also would be great if we could use a better theme, but that's definitely low-pri.
Thanks for the help here
|
|
||
| <h1 class="page-heading">Posts</h1> | ||
|
|
||
| <a class='githublink' href="https://github.com/resque/resque">Source code and documentation on github</a> |
There was a problem hiding this comment.
@varyonic we should keep the github link on the page.
There was a problem hiding this comment.
Added back 'View on Github', I'll leave styling to someone else.
I'm a little reluctant to pull in the plugins page. I understand the wiki does not get indexed by Google but it has minimal barriers to contribution so anyone in the community can register their forks and add notes on older gems (eg. @pboling). I do think the docsite should link to other gems adopted by the organization, ie. resque-scheduler (will resque-loner be revived?) Which other plugins might be adopted?
There was a problem hiding this comment.
but it has minimal barriers to contribution so anyone in the community can register their forks and add notes on older gems
Yeah, this is a downside. I wonder if there's some GH tooling out there to sync GH wiki pages to a public website or something? Would be something useful to look into.
What gems/projects do this well? None really come to mind for me.
There was a problem hiding this comment.
Will resque-loner be revived? Unlikely, I think. However, the lineage is alive (and yet withering, as I don't currently use Resque).
My resque-unique_in_queue was a rewrite of resque-solo, which was a rewrite of resque-loner. :)
There was a problem hiding this comment.
Right. I'm currently switching from resque-lonely_job to resque-unique-at-runtime. Given that resque-loner has already been adopted by the resque organization perhaps PRs could be accepted for a v2.0? If not then may as well archive it.
There was a problem hiding this comment.
Yeah, I definitely need to find a way to get my work adopted more broadly if it is going to survive at this point. There could be a PR to resque-loner, but it seems there has been no effort to do anything there in many years, so maybe it isn't on any active radars of anyone who could make a decision?
Follow on from resque/resque#1778 in response to resque/resque#1771
Preview currently at https://varyonic.github.io/resque.github.com/
I'm not sure which content from the wiki you wanted to include. I did go through the plugins page and tried to organize.
Shall I move more of the README Additional Information?