Skip to content

Staff Page#123

Open
yl6 wants to merge 17 commits into
masterfrom
yl6/staff-page
Open

Staff Page#123
yl6 wants to merge 17 commits into
masterfrom
yl6/staff-page

Conversation

@yl6

@yl6 yl6 commented Apr 26, 2019

Copy link
Copy Markdown
Collaborator

The staff page is currently done similarly to the projects page. We can probably(...should definitely) use YAML instead of markdown.

Comment thread _layouts/staff.html Outdated
Comment thread _layouts/staff.html
<img class="thumb" id="pokemon" frameborder="0"></img>
{% endif %}
<div class="text-wrapper">
<a class="title" href="mailto:{{ person.email }}">

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a mail 📧 icon indicating that the name is clickable and leads to their email?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally feel like it's pretty obvious that the names are clickable?

Comment thread _sass/vrsite/gallery.scss Outdated

.desc {
overflow: hidden;
text-overflow: ellipsis;

@ShanTulshi ShanTulshi Apr 29, 2019

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we hide the overflow at all? Given that users will have no way of seeing the expanded text

Edit: This should probably be in _sass/vrsite/staff.scss, not here.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed overflow to scroll and so now the description for each person doesn't have character limits and the text is scrollable to read.

Comment thread _sass/vrsite/staff.scss
}
}
}
} No newline at end of file

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's aim to separate out the gallery as its own feature and apply it here and on the projects page. (#93) That way, we can minimize the amount of duplicated CSS. For now, can we move the duplicate CSS as an include? Any variations between the two implementations can be referenced as variables.

Comment thread _staff/test_1.md
Comment thread _config.yml Outdated
Comment thread _staff/test_1.md Outdated
Comment thread _staff/test_5.md Outdated
image: https://raw.githubusercontent.com/PokeAPI/sprites/master/sprites/pokemon/44.png
desc: |
description for person 1
---

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we moving staff descriptions from individual files to one big YAML? I don't remember, but I would be in support of such a move.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes we are! I'll work on it.

Comment thread _staff/test_5.md Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants