I want to build a portal in which I want to have below stacks:
Statamic CMS (As the backend)
GraphQL for the API's
Vue js as the frontend
Can anyone help me with the above tech stack, and it will be helpful if there will be any documentation available to develop a website with these stacks.
Thanks!!
I have gone through the documentation of Statamic in which I am confused that I can have all in statamic or not?
Yes, Statamic has built-in support for GraphQL. There's documentation on how the GraphQL API works here.
Statamic doesn't care what you're using to consume the GraphQL API (you could use Vue/React/Vanilla/whatever you want).
Related
What should I ask my programmer to pull the properties that are in the CRM account to multiple wordpress installations.
It is possible using Ruby and creating a REST APIs, according to their site: https://ayuda.easybroker.com/article/330-api-de-easybroker-beta
Because you can't use JavaScript, TypeScript, React / React Native, Vue, Angular or similar. If you are going to use a programming language other than Ruby, you will need to create the interactions yourself. And it has to be on the back-end.
Does anyone know who can do it and how much does it cost?
I'm using a headless CMS (strapi) for my backend. My requirement is to send a notification to fe client once a comment is created in the backend.
I need to know whether strapi supports graphql subscriptions (if so can you please share sample code)or is their a better approach to solve this?
Strapi does not support this now, but graphql subscriptions are under consideration on the strapi roadmap.
Feel free to vote for it to push this topic.
I am testing a graphql api and I want to integrate with my system in laravel. Is there any documentation to do this? If possible to consume and send the values in graphql?
Note: I wanted to do it right
The question is too generic.
First of all, I recommend to check the official site: https://graphql.org/learn/
If you are going to consume an already existing graphql, you need a graphql client library.
Check a good list of client libraries: https://graphql.org/code/#graphql-clients
Client libraries have good documentation on how to install and use them.
If you are going to create/provide your own graphql api endpoint (that is a different story), you need a graphql server library.
Server libraries: https://graphql.org/code/#php
Laravel package (a wrapper for https://github.com/webonyx/graphql-php): https://github.com/rebing/graphql-laravel
try this library https://github.com/rebing/graphql-laravel, it's simple with good documentation
I am building a nativescript app that requires a search functionality. I am using firebase for my backend and I would ideally like to use a hosted search service like algolia for the same - however the algolia-search and algolia-search-helper plugins required are not supported in nativescript. I am open to using other search services like elasticsearch too, but am not sure how to go about it.
Any suggestions on how I can implement search in my nativescript app would be great.
You could call the Algolia REST API directly.
Some references:
Making HTTP requests from NativeScript
Algolia REST API documentation
(Note: Algolia doesn't usually recommend using the REST API directly because the API clients contain some DNS-related failover logic. If you are creating a large, high-availability production app, this is something to keep in mind.)
Our company is about to start a real estate project and have decided to go with the laravel 5.3 framework. The first phase is to write the apis and then these apis will be consumed by the mobile team and the frontend team to build the official mobile app and the web portal respectively.
Now I am confused whether to use laravel's built-in Resource controllers (as instructed in this tutorial http://www.programmableweb.com/news/how-to-build-restful-apis-using-php-and-laravel/how-to/2014/08/13) or use the Dingo Api framework.
Could you please help me which one should I go for and why as per the requirements i mentioned above?
Thanks in advance
Since, Laravel 5.3 comes with Passport (for api authentication), I would suggest you to use Resource controller, which is very simple and easy to work with, and also it create a meaningful end points
Route::resource('post','PostController');
GET /post/{post}
POST /post
EDIT /post/{post}/edit
DELETE /post/{post}