[LV2] Feedback request: new LV2 website
ssjackson71 at gmail.com
Mon Nov 24 11:51:20 PST 2014
>Slideshow might be doable by jumping through some hoops, but I don't
>know... pages in Markdown, probably not. Oh well, pros 'n cons...
I know little of markdown or html beyond basic use, but does your markdown
engine support inline html/js/css? I used a css slideshow for the infamous
plugins site. I imagine something suitable could be whipped up to put all
the images in some directory to be put into a slider. Along the lines of
On Mon, Nov 24, 2014 at 12:35 PM, David Robillard <d at drobilla.net> wrote:
> On Mon, 2014-11-24 at 10:56 -0700, Spencer Jackson wrote:
> > My $.02:
> > The site flow is much nicer from a developer perspective. With the old
> > it took me a few months before I really had figured out where the stuff I
> > need is (and I never even knew about the example plugins until after I'd
> > released 2 plugins). The new way leads a curious potential developer to
> > right places naturally I think. Overall it's a nice and clean look.
> Good to hear. I'm trying to make the reference documentation better in
> the same respect (e.g. single doxygen page for each extension API,
> linked to straight from the index).
> > Screenshots are an excellent idea. Almost required nowadays to attract
> > attention. Probably for fairness the best idea is to have a slideshow
> > of thing on the front page so we can display many different hosts and
> > plugins. If there were an easy way to "submit a new LV2 screenshot" then
> > devs of the respective projects and even users could load up a good
> > of images of plugins in action. I know I'd upload my plugin images just
> > the exposure. I haven't a clue how to implement a submit button to upload
> > images to a site folder though. I don't like adding images to git
> > personally, but it could just be done that way.
> Nice idea, but the static/git-backed thing is too nice. Doing a bunch
> of work to implement/run some dynamic screenshot submission thing on the
> server (and gaping security hole, no doubt), which is entirely different
> from how the site works, and people might not actually use anyway, seems
> like a bad use of time when a patch/pull request/simple email can do the
> same job, particularly since they'd need to be curated anyway.
> Slideshow might be doable by jumping through some hoops, but I don't
> know... pages in Markdown, probably not. Oh well, pros 'n cons...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel