Our company remains committed to being a trusted partner for the supply of reliable, sustainably produced helium in North America.” “This is an exciting year for us, and we plan to add two additional helium production facilities before year-end 2022, while also doubling the capacity of one of our existing production plants. North American Helium continues to increase its level of investment in Saskatchewan as we advance exploration and development projects slated for 2023.” Mr. We have been diligent in our approach to obtaining a deep understanding of the helium reservoir and trapping systems on our substantial land position and remain firmly on track to double helium production in 2022. Marlon McDougall, President and COO stated, “As NAH continues to execute on its operating and development plans, we are now realizing our goal of creating a new global helium production hub in Saskatchewan. This facility is located near the Village of Mankota in southwest Saskatchewan.Ĭommenting on this operational milestone, Mr. (“ NAH” or the “ Company”) today announced it has successfully brought its third helium purification facility on production in May with zero operational issues. The Tailwind docs are a really great resource for getting up to speed quickly on the syntax, but here is a brief example to show the power of Tailwind.CALGARY, Alberta-( BUSINESS WIRE)-North American Helium Inc.
#HELIUM EXPLORER CODE#
Moving the Explorer's styling code to Tailwind will be a gradual transition, and it might turn out that Tailwind isn't the best fit for Explorer in the end, in which case this section of the README will be updated accordingly. There is a / file at the root of the project which defines things like the website's color palette, breakpoints (sm, md, lg, xl), and in the future, things like font sizes, font weights, spacing tokens, and whatever else makes sense to include.
But inline styles don't allow for media queries, which are increasingly necessary to create a good mobile-first experience.Īs the Explorer website becomes more mature and the broader Helium product family adopts a more cohesive design, customizing UI elements in a consistent way across the Explorer will become more necessary, especially considering that around 50% of the Explorer's visitors are visiting from mobile devices. And systems like Ant Design can also become hard to work with when something like their column and row system doesn't quite align with the way you think a layout should look, or you want to remove or add extra padding somewhere for example.Īnd on the other hand, inline styles are a nice option for keeping the styles attached to the JSX code, and for conditionally styling things based on some logic.
Right now, the Explorer is styled using a combination of the Ant Design system, inline styles, and classes found in the /styles/Explorer.css file.Īnt Design is a really powerful way to quickly implement various complex UI elements that would take a long time to build manually (e.g.: tables with pagination, date pickers, search bars) as well as common UI elements that have a lot of nuance in functionality (e.g.: checkboxes, buttons, tooltips, etc.) But sometimes systems like Ant can be very limiting and opinionated when it comes to customizing those UI elements. Push your changes to GitHub and create a PR against the master branch, linking the PR to any relevant issues.Git checkout -b witness-list-enhancements
0 kommentar(er)
