GrassOps is targeting a few modern web app feature that conflict with each other, namely SEO optimization and client-side interactivity. I see GrassOps as eventually having publicly available resources that benefit from being SEO optimized, such as compiled community knowledge wikis. Visitors won't necessarily be visiting the site
Alright, so we've got the login and create accounts functionality pretty much working. I can invite people to join, and people can create and manage their account details, with some level of security. Awesome! What's next? Communities I'm currently working on the infrastructure to
Invitations I've gotten invitations working for the GrassOps application - which means accounts can start getting created. There are a couple of notes for creating accounts in GrassOps: * GrassOps is in very early stages, and accounts are primarily for the purpose of beta testing, as the app has
The GrassOps app is now connected to the internet! You can see the site at https://app.grassops.org/. I haven't implemented invitations, so unfortunately nobody can create accounts yet 😦 I've decided to adjust the required authentication needs to the following: * Signing in with Username and
The first milestone for GrassOps to be a usable platform is simply creating an account. Because GrassOps will be hyperlocal, relevant to real identities, and a place for sensitive information, it's important to me to have a secure and bot-resistent onboarding process right from the start. I'
I've written a first post before, on a different blog, almost a year ago. I'm writing another, in a new place, because this platform allows me to streamline my publication and avoid tedious maintenance work. What is GrassOps? It's an online, publicly available service