search

biojs / organisation

A hub for organising the community and ourselves
2 stars 1 forks source link

New homepage or temp placeholder #9

Closed yochannah closed 6 years ago

yochannah commented 6 years ago

biojs is down - see https://github.com/biojs/organisation/issues/8 One possible temp solution that could become the long-term solution is to set up a placeholder gh-page homepage. This doesn't require any additional hosting or passwords beyond what we already have I think, so long as we can re-direct the domain to point to the new page.

Things to include as a minimum:

yochannah commented 6 years ago

If you are interested in contributing to this issue please leave a comment!

yochannah commented 6 years ago

See also https://github.com/biojs/organisation/issues/4 for discussions of a possible design - but any basic page that we could point to would be better than a perfectly designed page right now while biojs is completely down

ljgarcia commented 6 years ago

+1 for the gh-pages solution Quick question about Google groups, did not we say that we were moving all to GitHub issues? Are we keeping them at the end?

yochannah commented 6 years ago

We definitely discussed the option of doing so! I'm reluctant to completely close down the mailing groups - it might be easier for some to post to a mailing group than to a github issue, and I think we can't do without some email contact option. I don't mind monitoring the two groups for spam and queries in general.

ljgarcia commented 6 years ago

Thanks for the clarification regarding the lists. Now, about the github pages, how should we start? Anyone in particular looking at it? Will it be discussed during the next meeting?

yochannah commented 6 years ago

@xwatkins has indicated he might be able to help out...

ljgarcia commented 6 years ago

Great! I just gave @xwatkins permissions to create repos so we are advancing on this. It is a good start!

ljgarcia commented 6 years ago

Great! I just gave @xwatkins permissions to create repos so we are advancing on this. It is a good start!

xwatkins commented 6 years ago

Do you have a snapshot of the content of the old biojs.net? It would be great to have some kind of mission statement, and a few tiles (I think there was 3 or 4 like re-use, re-something...?!). Basically I need some content! 🙌

yochannah commented 6 years ago

Much like @DennisSchwartz, I had trouble recreating the biojs.net site locally - it seemed to be missing content compared to what was on the live site?

The wayback machine version of biojs.net is probably our best bet for now: https://web.archive.org/web/20170723191208/http://biojs.net

yochannah commented 6 years ago

Oh, and @rowlandm has restored the mock he did last month: https://github.com/biojs/organisation/issues/4#issuecomment-345782470

xwatkins commented 6 years ago

Of course, wayback machine to the rescue! Should have something in the next couple of days

DennisSchwartz commented 6 years ago

@yochannah I actually managed to run it locally, the problem were that all the links don't seem to work.

~It's just a bad idea to run a static site compiled with Jekyll on top of Ghost. Just like duct taping stuff together haha.~

UPDATE: Actually not true.

yochannah commented 6 years ago

It's Jekyll and ghost? Oh my. Is the consensus that we shall have to abandon ghost and go full steam ahead with the gh-pages option? Add thumbs-up emojis or comment to indicate agreement. (Seems sanest to me not to require external resources when gh-pages can do it all).

DennisSchwartz commented 6 years ago

The only reason we were using Ghost was that Manny specifically asked us to have a CMS. So it seemed like an easy solution to just convert the site we had to a Ghost template. I can take a look if we can just extract that into a gh-pages Jekyll site again.

@xwatkins Are you starting again from scratch? I'm sure your web dev skills are better than mine were two years ago 😄 but you still might wanna see if you can re-use some of the old code.

DennisSchwartz commented 6 years ago

One of the reasons I'm asking is, let's not hack something together quickly if we can somehow manage to get something up that gives us time to actually design what we would the new page to look like. Just a thought :)

xwatkins commented 6 years ago

I agree this should take a lot more thought and planning and probably be part of a strategy as a whole, so I was just going to quickly knock together a landing page for the project. As this is fairly simple as a first step I didn't think it was worth looking into using Jekyll / Ghost, although it doesn't mean we can't explore this later depending on requirements.

DennisSchwartz commented 6 years ago

Yeah that makes sense.

Also, I have to take back my earlier statement. There is no Jekyll involved in this! It's a regular ghost theme with Handlebar templates. There is however, a lot of postinstall compiling with sass and ruby going on and I'm not sure why.

The bundler calls made me think it's Jekyll.

rowlandm commented 6 years ago

I'm happy with the gh option.

xwatkins commented 6 years ago

Ok, just pushed something very very basic based on old site and what I could gather from the thread above. Let me know if anything is missing/wrong etc...

xwatkins commented 6 years ago

Just noticed an issue in Firefox with the background SVG, will see if I can fix it.

rowlandm commented 6 years ago

Explore Components link doesn't work (pointing to www.biojs.io)

Regards,

Rowland Mosbergen | Stemformatics Project Manager

Centre for Stem Cell Systems

Department of Anatomy and Neuroscience | Faculty of Medicine, Dentistry and Health Sciences

Room 1.36, Level 1, Kenneth Myer Building

The University of Melbourne, Victoria 3010 Australia

T: +61 3 834 46623 *E: *rowland@stemformatics.org rowland@stemformatics.org

I acknowledge the Wurundjeri people of the Kulin Nation as the Traditional Owners of the land on which I work, and pay my respects to the Elders, past and present.

[image: cid:image002.jpg@01D31D8F.E823DE70]

CRICOS: 00116K

This email and any attachments may contain personal information or information that is otherwise confidential or the subject of copyright. Any use, disclosure or copying of any part of it is prohibited. The University does not warrant that this email or any attachments are free from viruses or defects. Please check any attachments for viruses and defects before opening them. If this email is received in error, please delete it and notify us by return email.

On Thu, Nov 23, 2017 at 10:56 PM, Xavier Watkins notifications@github.com wrote:

Just noticed an issue in Firefox with the background SVG, will see if I can fix it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/biojs/organisation/issues/9#issuecomment-346599283, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZo0pY4JvLSA2bqLlt--kmCbq3qQUAkks5s5V1dgaJpZM4QkLY5 .

xwatkins commented 6 years ago

both fixed.

4ndr01d3 commented 6 years ago

Hey guys, sorry I missed the call. So I'm wondering, what are the features that makes necessary a server for the registry? Isn't possible to create a client that gets info directly from npm and github and builds the registry on the fly? Just an idea, BTW @xwatkins I'm happy to contribute coding, just let me know how can I help.

DennisSchwartz commented 6 years ago

@4ndr01d3 That's basically what's happening in the registry-workmen. But it's still a server-side issue. It's also needed for the examples.

So we need to create a proper discussion about the requirements of the BioJS website.

4ndr01d3 commented 6 years ago

@DennisSchwartz that's what I though, and from what I can see we can do all the workmen tasks on a js client, from the workmen README:

  1. Search for all packages with a special tag on npm ('biojs', bionode') + remove duplicate packages (uniq)
  2. Query npm -> package.json
  3. Run extensions 3.1. npm: history stats 3.2. github 3.2.1. github info 3.2.2. github stats 3.2.3. Optional: Query github for snippets (ls "snippets")
  4. Run post processing (e.g. removal of duplicate keywords)
  5. Store the result in a DB

From what I can see, most of this is to be able to provide more info on the list of components, and to be able to filter/search on it. If we limit that list to what we get on https://registry.npmjs.org/-/v1/search?text=keywords:biojs the rests can become queries to github when the "page" of the component is open. The snippets will require a bit of extra work, but I think the component page can be built on the fly. Which makes me think the registry can be completely client based and therefore hosted completely on github pages.

Am I missing something?

rowlandm commented 6 years ago

Hey @4ndr01d3

I hear what you are saying, we want to reduce our complexity and not have a server. But I think that due to the complexity of searching / snippets and our international audience we need to actually have a server to reduce complexity of the code and to provide a decent user experience (ie make it fast).

It's actually going to be very difficult to drive down complexity in this situation.

Search for all packages with a special tag on npm ('biojs', bionode') + remove duplicate packages (uniq) This is an expensive query. You will be bringing back all the metadata needed across all packages and then filtering them on the client. This isn't scalable in the long term.

In Australia, we had issues with biojs.io taking ages to load and to add client processing on 500+ components in the future is going to be pretty intense. There are problems associated with things like dataTables when the number of rows is too high (pagination doesn't help) [link]

It's better to do this processing on the server into a DB. Cronjob every X minutes or so. Then when the user hit's the front page you get these aggregated views that are inexpensive to download. Then you can do a search via ajax and get back a cut down version of the components you have found.

This is a relatively basic website but perhaps you are right in that for the community this will be too advanced? I get the feeling that the majority of the community is either new to Javascript and web development or are self-taught?

Perhaps we should discuss this in #13 ?

rowlandm commented 6 years ago

Has anyone looked at this in greater detail?

yochannah commented 6 years ago

ok, running some thoughts through my brain & I'm going to try to use this thread to discuss this further and sound out thoughts:

First: We have people volunteering to help out in gitter all the time but we don't have clear-cut tasks to give them. So, let's break our tasks into small do-able chunks with easy steps to get people started - but I need to understand better what we want.

@rowlandm, I know one of the big things, for you, is to make sure performance is better worldwide. Looking at the workmen readme it seems that the workmen server probably does most of what we need without too much alteration - it fetches the packages via cronjob. Does that sound correct?

As such I suggest the following tasks:

Does that sound sane and correct? If yes, I'll set up the tasks on github and tag them to attract newbies similar to this one: https://github.com/intermine/bluegenes/issues/197