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
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.
If feel free to suggest changes.
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
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
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
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)
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 :(
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 :(
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
it's been discussed before, maybe there is an issue for it already
gitbuilding/gitbuilding#92
The current layout is in the "Designs" section which you can get to under the thumbs up/thumbs down
The current layout is in the "Designs" section which you can get to under the thumbs up/thumbs down
Is this the kind of thing you're thinking? https://www.figma.com/proto/L5j2QxaIyMpIs9SUHSL0FX/GitBuilding-Platform?node-id=3596%3A207&viewport=-1644%2C968%2C0.6650980114936829&scaling=scale-down
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
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?
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.
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.
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
https://gitlab.com/openflexure/openflexure-block-stage/-/blob/master/docs/Hardware.yaml
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).
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.
hence me being here...