Mocks for pages listing shared datsets & narratives #305
Comments
|
@eharkins's issue #343 on how to surface groups from the nextstrain.org frontpage made me revisit this issue. In general, I think we need a small set (6 or so) of components that we can reuse across all of the pages we are now creating (/groups, /community etc). These components will handle the styling, so that page authors can focus on the content rather than the aesthetics. It also provides continuity across the site. Six reusable components that will allow the functionality we want for most pages (Colours here identify the components, I'm not proposing we make each component a different colour 😂 )
*How a selection of pages would look One benefit is that the source code for each of these pages would now have a much higher ratio of content to styling. Right now the two are very intertwined.
|
As we expand the number of pages rendered by gatsby it becomes more important to expose a small number of reusable components which pages can use (see [1] for more). Here we implement the concept of "panels" which are displayed in a flexbox layout. Panels may contain custom content (we expose `<Panel>` for this, or they may display a selection of cards `<PanelWithCards`). The exact breakpoints etc need further work, probably at a time when the other components have been implemented. Note that this commit intentionally includes content which should be removed before release, either by subsequent commits or by ammending this commit: * /testing page * wireframes around components [1] #305
temp solution for cards is to allow the Cards component to use flexbox instead of bootstrap for a more compact, two-column layout. This will be refactored when we address the design and flexibility of these components in #305, #347. TODO: - might need to unsquash ncov and narratives cards to be able to read them on mobile - allowing page sections to tile horizontally, e.g. groups alongside sars cov 2 as in james' sketch - more testing
Recent work (including #287 #299 #201 #302) now makes it feasible to create pages listing datasets & narratives shared through nextstrain.org via methods such as community, groups etc. This issue focuses on mocks for the frontend work. Here I don’t consider the problem of collecting this data and keeping it in sync, this issue presumes that such a file is able to be fetched by the client. I also assume that such a file does not include parsing of the dataset file itself, which limits the metadata we are aware of for a given dataset / narrative.
For most of the sources I believe we can use a single template page, with different content (both text & fetched data file). These would be sourced from the following pages:
/pathogens(/corewould redirect here) - representing our core datasets. Table columns would be dataset & date updated./stagingSame table columns as above./groupsPrivate groups should also be shown, implying that the datasets must be dynamically generated by our server. Table columns: “Dataset”, “date updated”, “Group name”./communityConsideration should be taken on whether all datasets are shown, or whether people can opt-out. Table columns: “Dataset”, “date updated”, “GitHub organisation”.We may also wish to have an
/sharingpage, which fetches data from all the above sources. Such a page would imply the others have been implemented!/fetchwould work somewhat differently, but it would be nice to surface a page for this functionality.The text was updated successfully, but these errors were encountered: