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

[services] Design and Development Services Page #59

Merged
merged 25 commits into from
Jul 10, 2020
Merged

[services] Design and Development Services Page #59

merged 25 commits into from
Jul 10, 2020

Conversation

stacyk
Copy link
Member

@stacyk stacyk commented Jun 25, 2020

Cute animal pic

paige-cody-TgbyVWS9UDY-unsplash

Link to Trello card (if applicable)

https://trello.com/c/bruLAag5/63-i-want-fleshed-out-content-for-the-design-and-development-service-detail-page

Description

The commit messages say what you did; this should explain why and/or how.

  • Description is in Trello card
    Checklist of progress is in Trello as well

Steps to test/reproduce

Please explain how to best reproduce the issue and/or test the changes locally (including the pages/URLs/views/states to review).
view the /services/development/ page and the XD File: https://xd.adobe.com/view/b8f11a7c-c6a3-4524-410f-d08c6df679b3-cec0/screen/bb6add8a-7784-40d2-b82b-e649fa02174c/Service-Tag-Page

Show me

Provide screenshots/animated gifs/videos if necessary.
WIP

@stacyk stacyk added the WIP Work in progress/wait to review label Jun 25, 2020
@stacyk
Copy link
Member Author

stacyk commented Jun 25, 2020

content/services/development.md Outdated Show resolved Hide resolved
content/services/development.md Outdated Show resolved Hide resolved
@stacyk stacyk added Ready for Review and removed WIP Work in progress/wait to review labels Jun 30, 2020
Comment on lines 40 to 43
{% call layout.grid('narrow-columns') %}

{% call layout.block('item') %}

Copy link
Member Author

Choose a reason for hiding this comment

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

@mirisuzanne @jgerigmeyer I wasn't sure if line break matter as much here as they were in RST blog. I am not sure if we have a preferred amount of space between these calls and the end ones (there are three in a row after the second column of content).

Copy link
Member

Choose a reason for hiding this comment

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

@stacyk Generally, spacing shouldn't matter too much – but it can have some impact on how the file is read as markdown. We don't have specific conventions, I tend to base it on what blocks are related or what seems most readable.

Copy link
Member

@mirisuzanne mirisuzanne left a comment

Choose a reason for hiding this comment

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

Looks great! I left a few ideas for cleanup, but overall I think this is working.

src/scss/patterns/_lists.scss Outdated Show resolved Hide resolved
content/_includes/layout.macros.njk Outdated Show resolved Hide resolved

{% call layout.grid('narrow-columns') %}

{% call layout.block('item') %}
Copy link
Member

Choose a reason for hiding this comment

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

maybe call this grid-item or column-item or something that connects it to the narrow-columns grid? Alternately, consider using yaml data for these, like we do with icon blocks? We don't need to go that direction, but I tend to consider it when we otherwise need nested calls…

Copy link
Member Author

Choose a reason for hiding this comment

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

I had it in the yaml, but I think it is more readable when the content is the order it appears on the page in general (plus I tend do always mess something up when it comes to yaml). I know we have content in the front matter for many parts of the site. I am old school ¯_(ツ)_/¯

Copy link
Member

Choose a reason for hiding this comment

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

lol, yeah - I agree it's a trade-off. I'm just careful about nested calls, because I never understand how they handle context. But this seems to work, so I guess you got it right! 😂

Copy link
Member

Choose a reason for hiding this comment

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

(Sidenote: Nunjucks is buggy and I don't trust it 😬)

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

@jgerigmeyer are you asking to change this to using the yaml content instead of what is in here now? I'm not sure what you are saying.

Copy link
Member

Choose a reason for hiding this comment

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

@stacyk I wasn't saying that specifically, no. But I think we should all be vaguely aware of the existing bugs in Nunjucks, and hand-test any uses of caller (especially nested usage) or set to be sure it's actually working as we want.

src/scss/config/_color.scss Outdated Show resolved Hide resolved
src/scss/patterns/_lists.scss Outdated Show resolved Hide resolved
src/scss/patterns/_sections.scss Outdated Show resolved Hide resolved
src/scss/patterns/_sections.scss Show resolved Hide resolved
* main:
  Re-add codepen.
  update redirects
  Adjust redirects.
  Fix CI
  Upgrade deps, docs.
  Update links to sites.
  Update homepage links.
  Remaining (known) link fixes.
  Start fixing external links
  Add remaining redirects (I think).
  Another round fixing broken links.
  Cleanup broken links and unused images
  Add checklinks netlify plugin.
  First pass at fixing/standardizing links.
src/scss/patterns/_lists.scss Outdated Show resolved Hide resolved
* main:
  Upgrade JS deps.
  Stylguide fixes
  Remove duplicate svg viewbox/height/width (needs discussion).
  CSS-only click-anywhere-to-close on dropdown menues
  Add fieldset content wrapper for styling
  Upgrade deps, docs.
  Upgrade CCS
  Organize and document
  Radio cleanup
  Markup for new color controls
@stacyk stacyk added WIP Work in progress/wait to review and removed Ready for Review labels Jul 7, 2020
Copy link
Member Author

@stacyk stacyk left a comment

Choose a reason for hiding this comment

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

@mirisuzanne can I not use /// @group type in different files? I see the title on the page is in the middle (split between two pages of css).

src/scss/patterns/_sections.scss Show resolved Hide resolved
@stacyk stacyk added Ready for Review and removed WIP Work in progress/wait to review labels Jul 8, 2020
@stacyk stacyk requested a review from mirisuzanne July 8, 2020 17:36
@mirisuzanne
Copy link
Member

@mirisuzanne can I not use /// @group type in different files? I see the title on the page is in the middle (split between two pages of css).

@stacyk you can - we just need to move that title to the "first place". It's not ideal, but ¯\_(ツ)_/¯

@stacyk
Copy link
Member Author

stacyk commented Jul 8, 2020

OK, I fixed the typography styleguide page title order. Back to @mirisuzanne for final review.

* main:
  align pagination left
  Switch pagination order
  Fix oss sorting
  Fix tests.
  Fix posts sorting
  No more in-person conferences
  Simplify pagination markup, and fix a11y
  Add docs and (failing?) tests
  Style pagination
  Fix sorting and add dates
  paginate the main resource list
@mirisuzanne mirisuzanne merged commit 6cc13d9 into main Jul 10, 2020
@mirisuzanne mirisuzanne deleted the services branch July 10, 2020 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants