librelist archives

« back to archive

Re: Rewrite the site via Camping

Re: Rewrite the site via Camping

From:
Fela Winkelmolen
Date:
2010-07-09 @ 08:49
One thing I forgot to mention, eventually it would be nice to have the ability 
to share user contributed lessons using the website. 

> > - wiki, would be nice to have for 1.0
> 
> For what purpose, exactly? I think github's wiki is good for technical
> documentation, and just static html content is fine for user documentation
> on the site.

I thought for hosting tutorials, work-arounds, and to host the documentation 
there to allow users to correct and improve the documentation more easily. But 
perhaps the preferred way of sharing tutorals should be by lessons. Still I 
think a wiki is a good way to allow users to easily share knowledge...


> > - users being watched by each user (similarly as what currently is
> > implemented)
> 
> Totally. Friends. :)

Friends sounds nicer, altought I personally don't like the fact that for 
example facebook calling all contacts friends.... Also, friends are usually 
understood to be two way, while watchings can be one way. I think one way 
makes more sense in this case?


> The MVP I'd like to see for the site has this stuff, in order of priority:
> 
> * Accounts with saved/shared programs
> * Watching other people's changes
> * Messages
> * Forum
> * User Documentation
> 
> I only put user docs at the bottom because I think that we're going to get
> a lot of publicity on Whyday, and we need to retain as much of that
> community as possible. If documentation takes an extra week to get up, but
> people stick around to help on the forum, then we're successful.

I agree. (What does MVP stand for??)



What about hosting, currently I suppose the free plan of heroku is being 
used?? I hope we get more than 5 MB of data quickly =) Perhaps at a certain 
point we could ask some ruby-friendly hosting service for free hosting?

Re: [shoes] Re: Rewrite the site via Camping

From:
Devyn Cairns
Date:
2010-07-09 @ 21:20
On Fri, Jul 9, 2010 at 1:49 AM, Fela Winkelmolen <fela.kde@gmail.com> wrote:

> One thing I forgot to mention, eventually it would be nice to have the
> ability
> to share user contributed lessons using the website.
>
> > > - wiki, would be nice to have for 1.0
> >
> > For what purpose, exactly? I think github's wiki is good for technical
> > documentation, and just static html content is fine for user
> documentation
> > on the site.
>
> I thought for hosting tutorials, work-arounds, and to host the
> documentation
> there to allow users to correct and improve the documentation more easily.
> But
> perhaps the preferred way of sharing tutorals should be by lessons. Still I
> think a wiki is a good way to allow users to easily share knowledge...
>
>
> > > - users being watched by each user (similarly as what currently is
> > > implemented)
> >
> > Totally. Friends. :)
>
> Friends sounds nicer, altought I personally don't like the fact that for
> example facebook calling all contacts friends.... Also, friends are usually
> understood to be two way, while watchings can be one way. I think one way
> makes more sense in this case?
>
>
> > The MVP I'd like to see for the site has this stuff, in order of
> priority:
> >
> > * Accounts with saved/shared programs
> > * Watching other people's changes
> > * Messages
> > * Forum
> > * User Documentation
> >
> > I only put user docs at the bottom because I think that we're going to
> get
> > a lot of publicity on Whyday, and we need to retain as much of that
> > community as possible. If documentation takes an extra week to get up,
> but
> > people stick around to help on the forum, then we're successful.
>
> I agree. (What does MVP stand for??)
>
>
>
> What about hosting, currently I suppose the free plan of heroku is being
> used?? I hope we get more than 5 MB of data quickly =) Perhaps at a certain
> point we could ask some ruby-friendly hosting service for free hosting?
>

Heroku will likely give you more space if you need it—they're very kind to
open-source projects ;] When you do, just email their support.

-- 
    ~devyn