-
Notifications
You must be signed in to change notification settings - Fork 14
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
Research on whether to create a template or guide for automation graphics #121
Comments
Suggestion that we allow image submissions but offer project image design as one of our "value ads" |
We have agreed to develop a guide for developers to either create their own logo with best practices or open an issue to get a UI designer to do it for them. @superbunker is going to draft the guide. |
title: Creating a Good Project Image
|
Issue for reference: hackforla/knowledgebase-content#105 |
Guide drafted, still quite rough. May need to narrow the focus so it doesn't get too long? |
@superbunker will update the header with 3 # and also include a menu for navigation. |
Guide updated—changed formatting, added menu with anchors. Still working on content for image rights/attribution details, and overall design advice. Question about formatting: for standards and accessibility, should we stick to the heading hierarchy? (eg: only use H3 below an H2) |
Converted to bullet style, reduced the design advice, focused a bit more on "don't get us sued" issues. |
Include the following elements: |
Added specific to do items to guide... haven't done them yet. |
|
@susantangux can you confirm the Guide for readability/sense from your perspective or otherwise confirm it looks good? Saying limit to callouts/confirmation as the issue has been worked on for a couple of weeks and reviewed once so should be 95% there for MVP purposes. |
I have reviewed the Image Guide and it looks really good. I have the following comments/suggestions:
|
created file, added content from #121
I've reviewed "Creating a Good Project Image" guide and it looks good! My only comment is regarding "How to Credit Images" - current guide lists 4 items for image credit: 1) Title, 2) Creator, 3) Linked Source, and 4) License, but Niven requested adding the following elements also (from HfLA Website doc):
@NivenPrasad - Please confirm. Thx! |
The list above (Content to Type) was originally included for reference but it was subsequently decided, after further work by @superbunker and then discussion amongst the team, that the final guide didn't need to include those items. |
Changes merged, issue closed |
Overview
We need to research whether we need a template or guide for automation graphics.
Action Items
Resources/Instructions
The text was updated successfully, but these errors were encountered: