navapbc / platform Goto Github PK
View Code? Open in Web Editor NEWA platform that empowers teams to accelerate delivery through self-service tools and training.
License: Apache License 2.0
A platform that empowers teams to accelerate delivery through self-service tools and training.
License: Apache License 2.0
The E2E starter proof-of-concept should have:
In addition, the proof-of-concept should address the technical implementation considerations found in the related 🔒 tech spec:
This work will help answer the last outstanding question in the "End-to-end starter" 🔒 tech spec around whether it makes sense to create a separate E2E starter template or to embed an E2E starter in existing application templates.
Related repository: https://github.com/navapbc/template-e2e
Idea: common resources like user
can have common Flask blueprints.
While this idea isn't fully fleshed out, and it isn't 100% clear if Flask blueprints in an importable package is the right technical direction, but the idea of building tools around common data schemas could be further explored.
idea from Kevin Boyer: API endpoint returns a static list of the contributors to the project
see slack thread
More complex user-facing applications, especially ones that intake claims/applications/cases often need to manage the application flow. A best practice is to manage this with a state machine and abstract it into a flow management module. This approach also provides useful product development tools like visualizing the application flow as a flowchart diagram.
This issue is to capture the idea of making a reusable module for this functionality. The current vision for the implementation approach would be to implement this as a separate npm module, and it could be imported by default in https://github.com/navapbc/template-application-nextjs. That would make it easier to rip out than if the code was baked into the application template itself.
Scope of this ticket should include designing the npm module (e.g. in a tech spec) prior to implementation
Move repo setup instructions out of the template repo readme(s) and into the platform repo, so there’s a single place to maintain
It takes a lot of time to create architecture diagrams on a project. It would be beneficial to have templates for the common architecture patterns, especially ones that use the infra template's default system design.
The templates could probably just live in LucidChart for now.
Once the template's are created it would be good to have some documentation in template-infra about the templates.
Now that we split up the infra and application templates, we need to help the user of the platform understand how to use the two pieces together. We'll probably need to provide some instructions (and perhaps some tools if applicable) for the user to be able to use the template-infra with either of the template applications (template-application-nextjs or template-application-flask).
Each platform template is a separate repo because we want to maintain modularity and isolate dependencies. However, our projects frequently prefer to have a single monorepo to more easily manage a project.
Add a guide (or script) to support teams who wish to do this.
Related (or duplicate?): navapbc/template-infra#238
We now need to support multiple application stacks (python in addition to javascript), but don't want to duplicate the infra code. So the solution we are proposing is to separate out the reusable infra from the application repos. The result will be several repos:
Other possible scope would be to add some reference implementations
see slack thread
How do we automatically test the platform e2e, from installation to deployment?
We may want a template for static applications sooner than later.
Note that even for the NextJS template, it will have a Storybook component that is a static application that should be deployed.
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.