Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add styleguide #180

Open
alicetragedy opened this issue Feb 9, 2016 · 8 comments
Open

Add styleguide #180

alicetragedy opened this issue Feb 9, 2016 · 8 comments

Comments

@alicetragedy
Copy link
Member

Given the current inconsistency of the styling (see #179) I think adding a style guide for the future could really help. Maybe we could even use Living Style Guide since it's one of our RGSoC projects :)

@carpodaster
Copy link
Member

Excellent! 🎉

@troubalex
Copy link
Member

Okay, so I've looked more closely at the code now.

I think that before we can make a sensible style guide that also includes components such as headers, media elements, etc it might be wise to refactor the Sass files. There is a lot coming directly from Bootstrap, while other things are spread out over several files, although they should probably live close to each other.

It should't be too much work. The question is though if the site design is more likely to evolve in the near future or to change radically. In the latter case, it might not be worth doing this.

@alicetragedy
Copy link
Member Author

Hey @troubalex, thank you for taking the time to look into it.
We're planning a redesign at the end of the summer, (or, anyway, on time for next year) so maybe it would be a good idea to wait until then to refactor the files and work on the styleguide, as you suggested. I don't want to ask you to do too much work that will then need to be adapted again for the new use case.

@troubalex
Copy link
Member

Sounds good to me. Close or remove milestone?

@alicetragedy alicetragedy removed this from the Kickoff 2016 milestone Jun 10, 2016
@alicetragedy
Copy link
Member Author

I'll add a new, "after the program" milestone and assign the issue to it. Thanks for your help!

@alicetragedy
Copy link
Member Author

I'm going to leave this as part of our redesign/restructuring which will happen over the course of the next months. @troubalex, is this something you'd still potentially be interested in helping with? I can give more detailed information about the plan for after the summer (yes, there is actually, finally, a real plan).

@troubalex
Copy link
Member

It really depends on when, but generally speaking, I'm in. Can you share some details about what is planned?

@alicetragedy
Copy link
Member Author

@troubalex we are currently doing some minor copy changes to get ready for the 2018 edition. After that, in parallel with the preparations for the 2018 edition (so spring 2018), we'll be working with someone on rebranding and developing the tone of voice. Based on that, we'll also rename our program. (note: this rebranding work will only be “conceptual” i.e. we will not develop the brand visually at that point).
After we have all this (so probably mid- to late summer 2018) we are taking it all and using it to develop things such as e.g. a new colour scheme and to work on the restructuring of the website (this means: basically starting from scratch and rethinking what kind of information we want to have on there and who the audience is). I guess, depending on how much involvement you want to have, that would be the time you'd get involved — or later, since I guess we can extract / create a styleguide based on the changes we make to website and brand.
The idea is to launch everything in autumn 2018 in preparation for the 2019 edition. I'd be happy to give you even more details if you want, just don't want to write a novel in here 😂

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

No branches or pull requests

3 participants