raylus

yes!

Note this is NASA/JPL, not NASA-wide, JPL is a NASA center (FFRDC).

haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥

In our foundational setup for the new https://beta.nasa.gov and https://beta.science.nasa.gov websites, we've adopted the US Web Design System (USWDS). While our other core products primarily rely on Tailwind, we are quite familiar with this toolkit. In my opinion, comparing the two is not entirely straightforward, but the USWDS toolkit has been implemented effectively, despite some of its "America First" usa-* class names.

The decision to use the same toolkit across our projects is largely influenced by the 21st Century Integrated Digital Experience Act (IDEA), which mandates federal agencies to modernize their websites and digital services. You can find more information about IDEA here: https://www.hhs.gov/web/governance/21st-century-idea.html#:~....

Congrats to the Nuxt team!

One hint: just imagine using your digital signature (NFT or whatever you call it) and traveling in space with your VR devices in your browser? Sounds cool?! This is where this project is heading to.

Same bit of confusion as above, and by your name being 'cryptography' I guess I'm just hoping this isn't a planet-based NFT project :(

Check out https://eyes.nasa.gov

Wagtail CMS https://wagtail.org/ is the answer to this, and doesn't technically 'replace' the existing Django dashboard, new admin interface is being sponsored by Google, https://www.youtube.com/watch?v=qD6reQ7T8fQ

No problem, the Wagtail community on Slack [https://wagtailcms.slack.com] along with the docs [https://docs.wagtail.org/] are great resources.

I've used WP for years and still have stores and sites humming along just fine with my own theme and minimal plugins (pre-gutenberg), it had been my tool of choice throughout the start of my professional career. Those WP sites proudly filled my resume and PHP was my go to backend language until around 6 years ago.

Honestly, I was skeptical of Wagtail before developing blocks to work with their StreamField concept and diving into how clean and clear the Python models can be written as well as how all the data is clearly typed. Our team has decoupled implementations where we use Wagtail's GraphQL API and a modern Javascript frontend, along with traditional Django template driven sites. The ecosystem for Wagtail and Django is larger than you may think, but you are correct it that may take a few weeks to build out some integration that could have been plug-and-play in the WP plugin ecosystem, I usually take weeks to vet any off-the-shelf plugin and look into all of its code anyways.

Django [https://www.djangoproject.com/] + Wagtail CMS [https://wagtail.org/] have been great alternatives for our team.

Whew, DevOps fire alarms are going off!

github.com is pretty broken

use js + scroll-wheel observer, profit.

JPL Engineer here, any questions I could convey to the slack I'll be glad to feed back to HN

Thanks!! Also wanted to mention, NASA is separate from JPL for the most part as far as web services go.

JNCO jeans website, Angelfire sites, Homestar runner (‘99) to name a few.

Also former resident of Wilmington, no comment other than that.

maybe your search doesn't work, not sure...

http://imgur.com/a/Wtp5l

what's up with their site?

Can't open osx version

You should get together with the people who made horizon and merge the two ideas into a feature.