by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Julian Stirling
    @julianstirling_gitlab
    Hi Everyone. Moving the discussion over here
    Alan Long
    @alalo_gitlab
    Here is a figma file in which I'll be creating some UI mockups. To scroll and navigate between the screens (when I've got further) press the play arrow in the top right corner. https://www.figma.com/file/L5j2QxaIyMpIs9SUHSL0FX/GitBuilder?node-id=3515%3A2
    Julian Stirling
    @julianstirling_gitlab
    I had a poke at changing something. I did it on the browser side. Not sure if I can make the image on the left be the same? This is a cool tool! There is some stuff here for logos https://gitlab.com/gitbuilding/visualidentity
    If feel free to suggest changes.
    Julian Stirling
    @julianstirling_gitlab
    @alalo_gitlab is it possible to export from Figma in a HTML/CSSy way?
    Alan Long
    @alalo_gitlab
    Nah I've just been making a screen outside of the browser and then copy & pasting it in for export
    Not export but you can click on an element, then in the right side bar select the code tab at the top. I've haven't found it super useful yet but its a neat feature
    Frame 2.png
    Alan Long
    @alalo_gitlab
    In terms of branches, you can create new pages in the left sidebar. We can keep versions separate there
    Julian Stirling
    @julianstirling_gitlab
    Sounds like a plan
    Kaspar Emanuel
    @kasbah
    interesting article about using image-maps for annotations: https://videoinu.com/blog/image-maps-in-2020/
    links to this one from 2004 which has a simple demo: https://kryogenix.org/code/browser/annimg/annimg.html
    Julian Stirling
    @julianstirling_gitlab
    Cool, worth thinking about.
    Kaspar Emanuel
    @kasbah
    made an issue for it so we don't lose the links: gitbuilding/gitbuilding#129
    Alan Long
    @alalo_gitlab
    I've been thinking about the name, this is just a suggestion. www.making.it is owned but unused.
    engineering.it, buiding.it and designing.it and all used sadly but anything that fits in [blank]ing.it could work
    Alan Long
    @alalo_gitlab
    Sorry that animations too fast I'll create a still...
    makingit.png
    makingit.png
    Kaspar Emanuel
    @kasbah
    We had some discussion about the name before: gitbuilding/gitbuilding#18
    Honestly, after some time it's grown on me.
    I also own the domain buildinstructions.com (and variations: no "s", .org etc) but held them for a year and did nothing with them, so will probably let them expire.
    (.it has bad associations for me personally because I first created kitspace.org as kitnic.it and had to rebrand it after realising it was a bad name)
    Julian Stirling
    @julianstirling_gitlab
    I think changing the name would be problematic as we have a website, we are part of the OSS program in GitLab, we are on JOGL, here, etc. Would be a lot of time and effort. The name seems to be polarising, some people like it, some don't, but I think we would need a really solid reason to put that effort in.
    I am also not keen on ".it" domains as most search engines then categorise your site as Italian. We also have to be an EU citizen to hold a .it domain which we are not soon :(
    Alan Long
    @alalo_gitlab
    Fair, these are all good reasons not to make a change. Are people interested in a different logo? I don't want to tread on toes, just provide options if they're useful.
    Julian Stirling
    @julianstirling_gitlab
    Charlotte drew be the logo and I think it is a nice parody of the Git Logo. I think the key design work that would end up in the project now is the layout of the documentation. It is quite a subtle challenge because we want people to be able to write anything within reason in markdown and then do a simple conversion to HTML and then the CSS to make the result into attractive and useable documentation

    This is an example output: https://openflexure.gitlab.io/openflexure-block-stage/
    And we have automatically generated pages such as https://openflexure.gitlab.io/openflexure-block-stage/Hardware/Nut_M3_Brass

    I think the default layout is a bit garish

    Kaspar Emanuel
    @kasbah
    the table styling is what i see as the main design issue at the moment: it takes away attention from the info you are there to look at
    it's been discussed before, maybe there is an issue for it already
    Julian Stirling
    @julianstirling_gitlab
    gitbuilding/gitbuilding#92
    The current layout is in the "Designs" section which you can get to under the thumbs up/thumbs down
    Alan Long
    @alalo_gitlab
    I'm not sure what you refer to with table styling @kasbah
    Julian Stirling
    @julianstirling_gitlab
    That looks nice. I do agree side by side instructions are clear and pretty. I do wonder how we automatically generate them automatically from markdown. Any ideas Kaspar, perhaps by breaking up at the h2 heading?
    By table styling Kaspar was talking bout the bright red tables on these pages https://openflexure.gitlab.io/openflexure-block-stage/Hardware/Nut_M3_Brass
    Alan Long
    @alalo_gitlab
    So with the part page, would that be a database of parts that can be associated with part lists in submitted project's part lists or is that info embedded in each markdown file submitted? As in would each person who posts their design have to detail the specifics of generic parts like screws?
    Julian Stirling
    @julianstirling_gitlab
    Yeah we have a format for part libraries, essentially databases of the parts. The idea is not so much that there would a platform with centrally held part databases but that you would be able to make and share libraries of parts
    Right now we GitBuilding is a program that turns documentation in slightly modified markdown, plus some part libraries into a functioning documentation website. So we need to improve how these pages look even without thinking about platforms.
    Julian Stirling
    @julianstirling_gitlab
    Making nice documentation is not the only problem for making open hardware. The interactions with the Git based platforms (or other version control paltforms) is also hard for many hardware people.
    We have a plan to add features into the software to make it easier to interact with these platforms. This will allow make it easier to share designs and to have the platform auto-create the website with the documentation.
    The final thought is that it would be really nice to skin one of the platforms so the platform itself was more hardware friendly and displays the docs without going to a separate website.
    So the M3 nut in that project was defined in this library/database of parts:
    https://gitlab.com/openflexure/openflexure-block-stage/-/blob/master/docs/Hardware.yaml
    Alan Long
    @alalo_gitlab
    Yeah this kind of step by step UI makes sense in either case. Majority of people who view a git repo will simply clone it and never submit a merge request later, I don't see why hardware would be different.
    Following that assumption, it makes sense to think of potential users as falling into two groups — consumers, someone who wants to use a design hosted on the site and contributors, someone who will contribute to a design on the site (the later being a subset of the former).
    Alan Long
    @alalo_gitlab
    So many users of the site will only want to consume the work of others in which case providing them a simple UI like this makes a lot of sense I think. With that said it will be important to think about how we encourage users to move from consuming to contributing and make that process frictionless.
    Andre Maia Chagas
    @amchagas
    hello world!
    Kaspar Emanuel
    @kasbah
    hi andre, to do a proper gitbuilding hello world you have to write it into some gitbuilding docs and post a screenshot :)
    Andre Maia Chagas
    @amchagas
    I know! Julian has already given me that task... :P
    hence me being here...
    Kaspar Emanuel
    @kasbah
    :thumbsup:
    Julian Stirling
    @julianstirling_gitlab
    Hi Andre, thanks for being here :D