[kwlug-disc] Website Wishlist

[Andrew Sullivan Cant]

Paul,

Trying to consolidate the list of things that I think that kwlug.org
should do.

* event listings which include
  - announcement and description
  - pingback/webmetion about the meeting (e.g., microblogs by Bob to
    start with, and link backs to anyone else who mentions the meeting
    if we want to be fancy)
  - audio/video of the events
  - post-meeting notes (e.g., links to slides and presentation material,
    links mentioned during the event, questions that people thought
    were interest)
  - transcript (this would also be fancy given the amount of work it
    would take but valuable for search-ability and accessibility)
* contact information and links to other locations on the web
* guidelines for submitting and doing presentations
* aggregation of member blogs
* links to members and their published code
* links to other FLOSS groups in the region
* wiki section to be able to collect other information about FLOSS in
the region
* archived pages for the FLOSS Fund

I think that bostron.rb[1] is a nice example for a user group site.
Might provider some inspiration.

Andrew

[1] http://bostonrb.org/
	
On 11/07/15 01:35, Paul Nijjar wrote:
> 
> Come on, folks. So far it seems that the answer to the questions of 
> 
> - What is working?
> - What is not working?
> - What changes do you feel should be made?
> 
> is "the website is too dynamic, so please make it static and also set
> up a Gitlab instance to host the git repository to which you hand out
> keys"?
> 
> Clearly I did not frame the questions clearly enough.
> 
> - Paul 
> 
> On Sat, Jul 11, 2015 at 12:09:10AM -0400, Andrew Sullivan Cant wrote:
>> Oh dear, I think that I might have brainwashed Bob with talk of static web sites. :)
>>
>> Given that kwlug.org does not change that much, and discussion is handled in the mailing list it seems like a good option.
>> We could remove the general posting functionality, and just aggregate the FLOSS related blogs of members.
>>
>> Hubert mentioned this:
>>> One way to get all that with a static site generator is to set up a git
>>> repository on github/gitlab/etc., and give several people write access.
>>> Then you can set up a hook that will tell the web server to pull from
>>> the git repository and rebuild the site every time someone does a push
>>> to the repository.
>>
>> I think this would probably work well. I would pick Gitlab, just because they do actually release the code for their service.
>>
>>
>> Jekyll[1] is a pretty popular and would be a good option. I have been using middleman [2] for my personal site [3] and kwruby.ca [4], which are both still pretty simple. It seems like a good option too. They both have large collections of plugins.
>>
>> I have tried ikiwiki and found it fiddly, and eventually switched to middleman.
>>
>> Andrew
>>
>> [1] http://jekyllrb.com/
>> [2] https://middlemanapp.com/
>> [3] http://andrewsullivancant.ca/
>> [4] http://kwruby.ca/
>>
>> On 09/07/15 18:40, Chris Irwin wrote:
>>> On Thu, Jul 9, 2015 at 4:26 PM, Hubert Chathi <hubert at uhoreg.ca
>>> <mailto:hubert at uhoreg.ca>> wrote:
>>>
>>>     So I'm not volunteering for anything, but... ;)
>>>
>>>     On Wed, 8 Jul 2015 14:23:16 -0400, Paul Nijjar <paul_nijjar at yahoo.ca
>>>     <mailto:paul_nijjar at yahoo.ca>> said:
>>>
>>>     > Another thing that is nice with Drupal is having multiple logins. I do
>>>     > not want to be the only person with commit access, because at some
>>>     > point other people will need to update KWLUG content.
>>>
>>>     > The third thing is that the content should be updateable by the web,
>>>     > because giving out SSH credentials like candy might not go over well
>>>     > with our generous webhosts.
>>>
>>>     One way to get all that with a static site generator is to set up a git
>>>     repository on github/gitlab/etc., and give several people write access.
>>>     Then you can set up a hook that will tell the web server to pull from
>>>     the git repository and rebuild the site every time someone does a push
>>>     to the repository.
>>>
>>>
>>> Ikiwiki is quite nice in this regard. You push to it (or configure a
>>> pull periodically via cron, etc) and it rebuilds static content via a
>>> git hook.
>>>
>>> It supports editing via the web, and supports comments. The http process
>>> commits them to git, which means you can fetch & merge them in your
>>> local copy.
>>>
>>> -- 
>>> Chris Irwin
>>> <chris at chrisirwin.ca <mailto:chris at chrisirwin.ca>>
>>>
>>>
>>> _______________________________________________
>>> kwlug-disc mailing list
>>> kwlug-disc at kwlug.org
>>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>>
>>
>>
>>
>> _______________________________________________
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20150713/46a87200/attachment.sig>