"I'd just like to interject for a moment. What you're referring to as NASA, is in fact, NASA/JPL, or as I've recently taken to calling it, NASA plus JPL. JPL is not a government agency unto itself, but rather another free component of a fully functioning NASA agency made useful by the labs, production facilities.."
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#:~....
I would wager the intention there is that the prefix is unnecessary or that it could otherwise reflect the name of the toolkit as opposed to the country. As an American I also find it a little "yeehaw, 'murica" and not the norm for design frameworks, but it's much ado about nothing.
Somewhere in London some intern at gov.uk is still not finished rewriting all the god-save-the-queen-hr-<color> CSS class names to god-save-the-king-...
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/ ♥
I know about NASA Eyes. That's the greatest and most realistic illustration of the space I've ever seen in the browser. The Beta version of my project might look similar to NASA Eyes, but it'll start to differ soon once developed further.
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.
> 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.
> 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 :(
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.
If you’re a dev or have access to devs then the ecosystem is exactly what you’re trying to avoid with few exceptions. You simply don’t gain anything over a solid web framework with decent CRUD editing on top, except familiarity.
It’s a malleable tool, but at some relatively early point you’re fighting against it more than you benefit from it over something like GP suggests. Just slows you down and erodes confidence.
WP is best if you have no or limited dev resources.
Having developed with both of these options, Wagtail gives the developer complete control over what models and plugins go into the system and when upgrades happen. For some situations this is a good thing, for others it is not.
> the ecosystem of WP seems to be a magnitude greater
Define "greater", right? WP has more plugins, but many of them don't work, or are vulnerable, or throw in a bunch of random messaging and nagware, or slow down the site. In one sense, the Wagtail ecosystem is a lot smaller but what's there is of a higher quality. It's the old "Macs don't get viruses because they don't have the market share to warrant the attention" phenomenon.
Django developer here. I have limited experience with WP but used Drupal back in the day, and from everything I've heard WP is the same with respect to what I'm going to say.
You can touch your nose two ways right? You can just reach up, or you can contort your arm and reach around your head. Working with Drupal very much felt like the latter.
I had to jump through so many hoops to do everything. Just one example: If I wanted to turn off a Preview button in one part of the site, the code in that view had to check what application was running, or ALL the preview buttons in the whole site would disappear (i.e. there was no app scope). Drupal databases were hairy balls of complication, but that's the case with every system I've looked at that has to support "every" use-case.
With Django you just build what you need and you're done. It's very straightforward. Your code and your data model can stay really simple. I built out whole sites really fast with it, even when I was a relatively inexperienced developer.
It's not about the size of the ecosystem, because with a tool like Django it's really simple to just build what you need yourself.
That said, this model works best if you have access to at least one developer. If you're not willing to cough up for that, you're at the mercy of things like WordPress.
I would never want to host or be responsible for a WP site just because of the security vulnerabilities and potential for abuse (it could start serving spam/malware/etc), but especially not under my/my company's domain and put my reputation and users on the line.
Our company has a website that uses WP and a blog that uses Wagtail. Personally I like the Wagtail/Draftail UI a lot better than messing around in Wordpress.
