Skip to content

Design V2 of the website #11

Closed
Closed

Description

@GBKS

V1, which is a placeholder site, is being discussed here. For V2, @AlexaAker has kicked us off with some good design concepts and explorations, so I thought I'd create a dedicated issue for V2 to gather and continue this work.

Since we are still figuring out both content and visual design for the site, I assume we'll go back and forth on a few different ideas and explorations. This should be a fun process. Please add any relevant links I missed.

Activity

  1. self-assigned this
    on Aug 1, 2020
  2. pedromvpg commented on Aug 3, 2020

    @pedromvpg
    Collaborator

    I've started working on some more mockup content for a "Output selection" page on the guide.

    Using it to test the process of editing content in the jekyll, github, and figma flow.

    Hoping this can be the starting point for discussion of how we're collaborating on content and what the design of the guide needs to accommodate.

    Working page here:
    https://pedromvpg.github.io/bitcoin-design-guide/guide/wallet-components/output-selection

    Some questions:

    • does this process make it easy for designers and writers to edit and contribute, like a wiki?
    • does figma offer an easy way to fork, duplicate, and version control projects?
    • what other functionality needs to be tested? Zoom in on images, video, etc...

    Any feedback greatly appreciated.

  3. timrauhut commented on Aug 4, 2020

    @timrauhut
    Contributor

    Some questions:

    * does this process make it easy for designers and writers to edit and contribute, like a wiki?
    

    I like the approach with the forking for the article editing. It provides a nice history. I'm not sure how the process feels like for people without any git knowledge. Would be interesting if it's too difficult or not. But I think for a first start it's nice. Later on, we could evaluate things like https://www.netlifycms.org/ which has some nice workflows for static content.

  4. GBKS commented on Aug 5, 2020

    @GBKS
    ContributorAuthor

    Can you explain a bit more what you are suggesting in terms of process and collaborating on content?

    A few thoughts:

    • I think a lot of first drafts will be written in Google Docs or elsewhere before they go into the repo. Much easier to collaborate that way. I can also imagine us directly help people who are not comfortable with Github do this import
    • I would not expect any non-developers to use command-line git. For small changes, github.com direct editing works. Otherwise, the Github desktop app is pretty straightforward to use. Either way, we need to create good tutorials (or find tutorials elsewhere we can recommend, like the video here)
    • Figma has public community files that can be remixed (forked). There's no system for merging forked content back in though, so either we replace the Figma link in Jekyll to the new file, or update the original file manually
    • I'd like to see some options around theming whole pages or parts of pages like in the image below. For pages maybe just black and white, and for sections maybe either a color, image, pattern or gradient (would have to be careful here not to go overboard)
    • I'd also like to have to option of providing a large header image above the title
    • What does "{: .no_toc }" do in your markdown file?

    Bitcoin guide site 200801

    Thank you so much for tackling this.

  5. Bosch-0 commented on Aug 5, 2020

    @Bosch-0
    Collaborator

    Figma has public community files that can be remixed (forked). There's no system for merging forked content back in though, so either we replace the Figma link in Jekyll to the new file, or update the original file manually

    Could we not just have a 'main' page in the figma file that is the designs that will be showcased then create seperate pages in figma for changes to the design which we can agree on as a community to 'merge' into the main page.

    Something like below:
    image

  6. GBKS commented on Aug 5, 2020

    @GBKS
    ContributorAuthor

    @Bosch-0 beyond 3 editors per file, you need to upgrade to a paid plan.

  7. GBKS commented on Aug 11, 2020

    @GBKS
    ContributorAuthor

    Just a bit of exploration on a possible V2. It's super rough. I tried to wrap my head around what content sections we might want to what could go in there, and tested out a few more illustrations (found on Behance) for the header to drive home the main tagline. Not married to anything here, but I thought I'd share. It's in the same Figma file as always (main file and community file).

    Home page V2 200811

  8. GBKS commented on Sep 1, 2020

    @GBKS
    ContributorAuthor

    White canvas style 200828

    Reposting from Slack. This visual concept expands the idea of bitcoin as a blank canvas. Page content is super minimal, almost like a coloring book, and various different visual styles can be applied. This is super flexible and would allow for many different expressions, from corporate polished to artsy to cypherpunkish etc. This approach would be a way for different community members to put their own spin on things without feeling overly restricted.

  9. added
    DesignTask is about designing something.
    and removed
    Help wantedExtra attention is needed
    on Dec 10, 2020
  10. danielnordh commented on Dec 16, 2020

    @danielnordh
    Contributor

    Suggest closing this issue

  11. GBKS commented on Dec 17, 2020

    @GBKS
    ContributorAuthor

    We're now on V3 of the website. V1 was a basic placeholder, V2 was a proper self-contained homepage and V3 added sub-pages and the guide to that. There is still some refinements needed on V3, which we can handle in separate issues. Whether we need a V4 or what that would include is up for discussion. The Figma file for the site is here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

DesignTask is about designing something.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions