steckdev wrote:The architecture that needs to be designed is an open source Rest API that would enable any developer to request scriptures, conference talks, or other pieces of information. With this designed as a defined Rest API then any other device that will/can come along can use this architecture without them having to evaluate and encourage the open-source community that thrives in this type of project. I want to contribute and make a difference but we just don't have an ability to access the information.
Sure. I guess I meant we need to come up with a project organization. I intend on starting the project in nodejs for the time being until the project becomes too complex or there's a demand to switch languages. Does the lds tech community have any language preferences? So far my alexa skills have been fairly small, so I'm not sure the best way to organize the project and I'm open to suggestions. Also, it would be good to have some documentation on what the vocal interactions are like so we don't have to redesign them later to support new features. I'd love to design something that could be used by other similar services. Perhaps there is a resource for each service that calls into a common library for finding the file. Just my 2 cents