bcgov / nr-theme Goto Github PK
View Code? Open in Web Editor NEWCommon repo for FSA theme
License: Apache License 2.0
Common repo for FSA theme
License: Apache License 2.0
Wait for #122 to decide if Helper Text size needs to be increased.
test
Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).
In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means it's critical that we work to make our content as discoverable as possible. Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.
Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca
email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic
.
That's it, you're done!!!
Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz
to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.
If your org is not in the list below, or the table contains errors, please create an issue here.
While you're doing this, add additional topics
that would help someone searching for "something". These can be the language used javascript
or R
; something like opendata
or data
for data only repos; or any other key words that are useful.
Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.
If your application is live, add the production URL.
Short Code | Organization Name |
---|---|
AEST | Advanced Education, Skills & Training |
AGRI | Agriculture |
ALC | Agriculture Land Commission |
AG | Attorney General |
MCF | Children & Family Development |
CITZ | Citizens' Services |
DBC | Destination BC |
EMBC | Emergency Management BC |
EAO | Environmental Assessment Office |
EDUC | Education |
EMPR | Energy, Mines & Petroleum Resources |
ENV | Environment & Climate Change Strategy |
FIN | Finance |
FLNR | Forests, Lands, Natural Resource Operations & Rural Development |
HLTH | Health |
IRR | Indigenous Relations & Reconciliation |
JEDC | Jobs, Economic Development & Competitiveness |
LBR | Labour Policy & Legislation |
LDB | BC Liquor Distribution Branch |
MMHA | Mental Health & Addictions |
MAH | Municipal Affairs & Housing |
BCPC | Pension Corporation |
PSA | Public Service Agency |
PSSG | Public Safety and Solicitor General |
SDPR | Social Development & Poverty Reduction |
TCA | Tourism, Arts & Culture |
TRAN | Transportation & Infrastructure |
NOTE See an error or omission? Please create an issue here to get it remedied.
According to the title, we expect the labels color to be changed from secondary-text to primary-text.
This is currently listed in the change log.
As requested by Jack on issue #78, tagging @MCatherine1994 and @jazzgrewal
Jack copypasta from Figma - July 8, 2023
Enhancement:
Increase text inputs’ label size and color contrast
Reason:
Users found the input’s labels difficult to read and distinguish
Discussed
Resolution
What changed
Labels color style
Text color will change
Components:
Themes:
Participants:
Andrea Kolot
Jack Sam
Olga Liberchuk
Michelly Marsoleta
Marina Carvalho
Maria Fernanda Ferreira
Maria Eduarda Guimarães
Sabina Donnelly
Check if the pull request title matches the requirement for release please
Can we change the url/repo name to nr-fds-theme? Or is that crazy at this point?
@DerekRoberts
Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.
It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.
I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)
Teams are encouraged to favour modern inclusive phrasing both in their communication as well as in any source checked into their repositories. You'll find a table at the end of this text with preferred phrasing to socialize with your team.
We're aligning our development community to favour inclusive phrasing for common technical expressions. There is a table below that outlines the phrases that are being retired along with the preferred alternatives.
During your team scrum, technical meetings, documentation, the code you write, etc. use the inclusive phrasing from the table below. That's it - it really is that easy.
For the curious mind, the Public Service Agency (PSA) has published a guide describing how Words Matter in our daily communication. Its an insightful read and a good reminder to be curious and open minded.
The word "master" is not inherently bad or non-inclusive. For example people get a masters degree; become a master of their craft; or master a skill. It's generally when the word "master" is used along side the word "slave" that it becomes non-inclusive.
Some teams choose to use the word main
for the default branch of a repo as opposed to the more commonly used master
branch. While it's not required or recommended, your team is empowered to do what works for them. If you do rename the master
branch consider using main
so that we have consistency among the repos within our organization.
Non-Inclusive | Inclusive | |
---|---|---|
Whitelist | => | Allowlist |
Blacklist | => | Denylist |
Master / Slave | => | Leader / Follower; Primary / Standby; etc |
Grandfathered | => | Legacy status |
Sanity check | => | Quick check; Confidence check; etc |
Dummy value | => | Placeholder value; Sample value; etc |
This list is not comprehensive. If you're aware of other outdated nomenclature please create an issue (PR preferred) with your suggestion.
The proposal is to ensure that the smallest text in FDS applications is 16px (12pt font) out of Figma and that the FDS stylesheets retain relative sizing capability where 16px is equal to 1em.
This proposal originated out of a conversation between Chantelle/Andrea (Aug 21, 2023) regarding CLIENT's external form having perhaps too many levels of hierarchy (too many different font sizes). This will be addressed in a TBD ticket.
In Team Alliance's collab session (Aug 22, 2023), Ziad brought up wanting to ensure that what comes out of Figma and gets implemented in code still retains the ability for someone's browser to go bigger or smaller based on browser preferences.
In the attached screenshot from CLIENT's external application, the small helper text is currently set at 12px font (which is 16px) with 16px vertical spacing.
Testing sprint and application
SPAR lead the way on designing the style/components for displaying read-only text that is important to display to users. CLIENT subsequently followed the same style.
A good time to review and commit to or re-do the standards for read-only content.
Define standard for:
Proposal: Should landing pages be responsible responsive to device theme preferences or stay in light mode only?
Background: The designers agreed to the Theme Toggle not appearing on the landing page only appearing on the blue header (as to not have to design a toggle that would also have to show up on the white and black backgrounds of the landing pages)
For Team Silva, Jazz implemented code for all of SILVA (including the landing page) to detect device theme settings. So after the Theme Toggle decision to have landing pages be light mode only, SILVA's landing page still detects device theme settings. There is no Theme Toggle on the landing so users do not have to the option to switch the theme.
We asked Chantelle if this was a problem (Sep 7 2023). Chantelle recognized this as a feature, as opposed to a problem. Chantelle wanted Team Silva to survey other teams if they want to adopt this approach for their landing pages.
This proposal originated out of a conversation between Chantelle/Andrea (Aug 21, 2023) regarding CLIENT's external form having perhaps too many levels of hierarchy (too many different font sizes with potentially hard-to-read light shades of grey).
This will require a review by all FDS teams.
For example - labels vs help text look about the same size but different and chaotic
Keep colour as text-primary.
Hi folks!
According to the title, we expect the labels color to be changed from secondary-text
to primary-text
.
This is currently listed in the change log.
This issue is also blocking a task for us at SPAR...
Thanks!
Create custom stylesheet for the following components, and the custom style needs to match in the Figma Design System:
Also if Figma can use any version control, so we know our stylesheet is for which version of the design system
The new label color is not being correctly applied, the identifier is not specific enough. This task aims to fix that.
Review navegation tab inline, it needs more visual emphasis.
Find a better solution for the release process. Fine with release-please now, but would like to know any other options. This is low priority.
Carbon's website seems to be showing 5
https://v10.carbondesignsystem.com/guidelines/2x-grid/overview/#breakpoints
A lot of our Figma files show 6.
Reference link: https://www.figma.com/file/5BnF5T2ncoZVpSbCbj30Mr/FAM-mockups?type=design&node-id=3272%3A67804&mode=design&t=8jGCmq6NapuCu1Kl-1
We need to enhance how typography is presented in the design system.
Describe the task
Understand what issues users are running into using FREP and how they are resolved
Acceptance Criteria
Additional context
link to Jira service desk tickets: https://apps.nrs.gov.bc.ca/int/jira/browse/SD-15647?jql=text%20~%20%22frep%22
test
Proposal: Do we want to incorporate BC Sans 2.0's Light and Light Italic characters to our typography choices?
BC Sans 2.0 was released in July 2023. It now includes Light and Light Italic in addition to Regular and Bold from 1.0.
Currently we manually trigger the npm package publish pipeline whenever release-please created a new git tag version, and we want to make this trigger automatically.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.