At IKAUE, what we have done is create “reactive documentation”. Systems that act substitutes for the traditional documentation that we might have in the company. It is about fulfill the same objective: standardiz, serv .
A Knowledge Center, and giv clear
Guidelines on how the work is expected to be done. Anly what we will do is add all the details to. A custom so that this is the entry route. F to solve the company’s problems.
There is no need to read all the documentation anymore
We can just k our . will k us the queries and give us the complex data. It will help us with the configurations, explain what data exists and give office 365 databe us ide about what we should look at to solve different problems.
We use an example the development of
The custom that we have developed for «IKrawlerJS». IKrawlerJS is a crawler developed by IKAUE, which we use with our clients. Fhe development apply neuromarket to your social networks of this In addition, we have given examples of well-made queries and crawl. F configurations of different types.
We’ve loaded a number of resources into
Ehe custom s system, so the system is now able. S to answer any questions we might have about us our own crawler . It will tell us what each field and data it contains means. S how to extract different reports and queries to. Google BigQuery ( queries that are also bed on our best practices), it will give us ide of what we could look. S at to solve different SEO problems. A for almost all of our work related to our crawler .
To do this, we have had
To create and upload various documents tg data with many details about. A what each piece of data is, what processes the crawler performs and all the configuration. S details that can be performed.