https ://ifcopenshell.org/

SSL do not work - Error 502

Although it's necessary for us to keep on hacking away on the code, it's also necessary to provide a better web presence. Ideally, someone (hey, is that someone you? :) will take charge of the IfcOpenShell and BlenderBIM Add-on website :) This involves graphic design, creating interesting screenshots, coming up with engaging code samples (or the idea of them, we'll write the code!), writing HTML / CSS / JS, taking a critical look at what content users want to see, and basically all the usual stuff involved in building and maintaining a website.

The website will be static content. No user sign ups and so on so don't worry about backend. We can also provide and help manage servers / domains / ssl.

Note that a lot of content may be delegated to a dedicated documentation website (after all most visitors are devs or powerusers) so the actual pages for the site will be quite minimal, but we hope quite visually engaging and has the necessary calls to action for visitors (e.g. go to docs, ask for help on forums, download via this link, etc).

Nothing is set is stone, so as is with most FOSS projects, the one who implements, decides :)

Current sites: http://ifcopenshell.org (dev-focused lib/engine/cli apps) https://blenderbim.org (user focused blender-based gui)

1. Redesign both websites to have a common look and feel as they are part of the same umbrella.
2. The design should be modern and beautiful :)
3. It must be very clear for a new IfcOpenShell user to discover what makes it special
4. It must be very clear for a new BlenderBIM Add-on user to discover what it is and what its features are
5. A C++ user should be able to quickly be able to write and compile their first Hello World
6. A Python user should be able to quickly write their first hello world, including exposure to the utils and api, some of IfcOpenShell's key scripting strengths
7. It should be clear what all the utils are for IfcOpenShell (IfcClash, IfcDiff, IfcCSV, etc)
8. All documentation must have a cohesive template design and standardised structure
9. All CLI utils must have clear CLI running instructions
10. Basic guides should be written for common BlenderBIM GUI tasks (view, create new, common editing things)
11. User should readily identify how to contribute
12. User should readily identify how to ask for help through different mediums (bugs, forum, chat, paid private consultation, etc)
13. Fundraising should be prominent in key parts of the site (e.g. blenderbim download) to encourage raising funds towards goals, with clear vision of results of funding communicated to users
14. IfcOpenShell and BlenderBIM Add-on to direct all funding towards OpenSourceBIM OpenCollective.
15. OpenSourceBIM OpenCollective page to be updated with new text, goals, tiers, graphics, etc
16. The continuous confusion of "how do i install IfcOpenShell" needs to be solved :) Pip? Conda? Custom download? Compile?
17. Compilation instructions for C++ may perhaps be migrated to sphinx docs and reviewed to make sure it is up to date, especially on platforms where common bugs crop up (Mac? latest visual studio I've noticed?)

Not a big deal, the website is awesome, but in big screens, the "Let's get started" piece gets overlayed by the "desing2.png" image:

I gave it a quick look, and I believe it has to do with mixing absolute and relative units in

and the row class from bootstrap.min.css (which seems autogenerated and I don't know where it comes from).