Skip to content

Mapping Overall

The HYIP Project edited this page Jun 17, 2016 · 309 revisions
This wiki is courtesy of The HYIP Project. Find all of them on The Project Map.
🔼 Intro ◀️ Prev 🔁 Reload Next ▶️ Last 🔽

Table of Contents

Overall Map

You have reached the last section of our Mapping System. Here we are going to locate a set of key-value mappings on our project repositories and drive them towards an overall project map.

Here we do our best to explain as you might get confused. However, in order to get easier on following this section we recommend you to make clear yourself to our previous section.

Algorithm

We hope you have enjoyed to what we have explained. You can consider to check all diagram of our mapping on a slideshow available on our blog page.

This slideshow is presenting Step by Step Process is assigned from and back to a routine. Now we are going to explain what we are going to do with this concept in our project.

Routine

As we have explained about portraying, to make clear separation between the processes here we take a new repo and wiki and named it as hyip which we took from our project title.

Based on our documentation about GitHub Pages we recommend to use User Repository for the main process, and take the Organization for hyip process.

  • The process of `info` will stand as User Repository
  • The Process of `hyip info` will stand as Organization Repository
Tip: As recomended by GitHub on multiple accounts it is recomended using only one user account to manage both personal and professional repositories.

Portraying

  • The Process of `hyip info` be displayed as Organization Pages
  • The process of `info` will be displayed as Project Pages
Follow to the diagram, all the code of main process will be put on User. Out of those main processes such of code will be arranged so it can be displayed on Organization and described on their correspond wikis.

Parameter

When applying the steps outside a routine then the diagram will be shown as below: So an Organizational will get two of main repos. One for its own routine and another one is the associated repo when a spreading is taken a place.

Spreading

Here is the appearance of repositories will look like:

Taken the picture above then the arrangement of repositories can be explained as below:

Since we are on spreading direction so we take the info and hyipworld.github.io in to the mapping which development on each processes are consist of 3 (three) routes as listed below:

  • Read & selecting the valuable information for writing them in to the associated wiki
  • Writing the repo, scripting in to the appropriate programming language(s)
  • Reading the repo, process of portraying the current status of repo
Each of process will need to put either user or organization accounts under which the writing for the development is taken a place. This formation shall be provided by two (2) accounts, consist of an account that associated with the place where the wiki is written and another one for the repo.

So when they goes in to a tabulation it will look like as shown below:

🔘 Type Repo 🐮 Form Route
🕒 main info 🐄 🔀 🏡
🕓 hyip world 🐘 🏠 🎦

Chanel Group on main info

# Form Route
1 Repo Writing
2 Wiki Writing
3 Repo Scripting
4 Wiki Scripting
5 Repo Portraying
6 Wiki Portraying

Chanel Group on hyip world

# Form Route
1 Repo Writing
2 Wiki Writing
3 Repo Scripting
4 Wiki Scripting
5 Repo Portraying
6 Wiki Portraying

Combine the Groups

# Form Route
1 Repo Writing
2 Repo 🔀 Scripting
3 Repo 🏡 Portraying
4 Wiki Writing
5 Wiki 🎦 Scripting
6 Wiki 🏠 Portraying

So the result of combination of the above will be as below:

🔘 Type Repo 🐮 Form Route Channel
🕒 main info 🐄 🔀 🏡
🕓 hyip world 🐘 🏠 🎦
Note:
  • The selection on the brand of channel links are not mandatory to be the same as per our selection shown on the tabulation above. You can choose the brands to whatever you like.
  • However four (4) of the same brands will be required to be uniform as the combination of routes will get always four (4) internal processes which symbols are 🔀, 🏡, 🎦, and 🏠.

Opposite

The same also applied to the correspond Organization:

Similar explanation is also applied to the above repos:

By the same explanation as the appearance then the combination will be as shown below:
🔘 Type Repo 🐮 Form Route Channel
🕐 main world 🐘 🔀 🏡
🕛 hyip info 🐄 🏠 🎦

Forming

Let's combine the tabulation:

🔘 Type Repo 🐮 Form Route Channel
🕒 main info 🐄 🔀 🏡
🕓 hyip world 🐘 🏠 🎦
🕐 main world 🐘 🔀 🏡
🕛 hyip info 🐄 🏠 🎦

This form showing the process that is happened on a spreading as the beginning phase when a parameter is assigned.

However the complete process is happened on a settlement which is involving all the three (3) employments that generated on an employment and combined by a merging.

Employment

By the concept of forming as explained above then three (3) kind of employments will be generated. This concept will be applied through all the elements involved and that consequently also including our sites as well.

We have declared that this project is stand as our employments. As the concept implementation, our main site consist of three (3) main programs that is presenting each of the three (3) employments named site monitor & rating, online news / blogspot, and project map and team.

The table above is represent the form and route on the 1st-employment which form is generated on the beginning phase but the settlement on it is done on the last step of the whole process when the 2nd and 3rd employment are completed.

Routing

Forming of 2nd-employment:

🔘 Type Repo 🐮 Form Route Channel
🕐 main rating 🐝 🔀 🏡
🕐 hyip monitor 🏠 🎦
🕐 main monitor 🔀 🏡
🕐 hyip rating 🐝 🏠 🎦
The process of 2nd-employment is begin as shown on mapping below:

Note:
  • The routing of the 2nd-employment is indicated by the first (1st) and the 2nd of separated lines
  • Therefore it is started on the repo of main rating and finished on the wiki of main monitor
  • Counting on all the steps then it will be eight (8) routes all together.

Settlement

Forming of 3rd employment:

🔘 Type Repo 🐮 Form Route Channel
🕐 main team 🐜 🔀 🏡
🕛 hyip script 🏇 🏠 🎦
🕐 main script 🏇 🔀 🏡
🕛 hyip team 🐜 🏠 🎦
While the process of 3rd-employment is begin as shown on mapping below:

Note:
  • The routing of the rdd-employment is indicated by the 2nd and the 3rd of separated lines
  • Therefore it is started on the repo of main team and finished on the wiki of mainscript
  • Counting on all the steps then it will be also eight (8) routes all together.

Channel

On our concept the channel links will stand as an important role particularly on focusing a settlement on every step of process. They will also be taken as initial form on further development when a parameter is assigned in the child processes.

The channel selection will best if they are set in hexagonal configuration plus one general link that works as a combination of all of them. You can then configure them to twelve (12) or twenty four (24) child processes so it will be able to implement one-to-one-mapping.

The page location and position on a site are not mandatory. They will become important when a nature is assigned to a page as it will become the base on further development.

An easy way to figure out the kind of channel you can see them on our blog which have six (6) main pages that also stand as main menu. Here are the tabulation of the pages and their configuration of the concept implementation.

# 📷 Page Title 🐮
1 Hyip Business 🐄
2 Hyip Rating 🐝
3 Hyip Monitors
4 Hyip Forums 🐜
5 Hyip Script 🏇
6 Hyip World 🐘

Try to click the picture (:camera:) or nature (🐮) of each pages, you will see a map showing a pair of our related repos and wikis that connected to the page as a user profile. You may see also that every other page than the six (6) main pages like mapping is put under the sub menus.

Beside the six (6) pages there also a main link stand as the site address. The link is assigned to display every other posting that are made and set to be correlated to each of the pages using category and tagging and that together with the pages follow our concept of the six (6) to become all the (7).

This kind of formation will also be the mapping key elsewhere. Check our networking profiles of Hyip Monitoring & Rating(1), Marketing Strategy(2), Application Script(3), Topic Discussion(4), News & Blogging(5), and Social Coding(6) that all is shown in the bottom of our main site(7).

Comparation

When all the routes on 2nd and 3rd employment is completed then the mapping will come to the main repo of world which is the 1st route of the 1st-employment as shown below:
Here the process will be step further the same as the 2nd and the 3rd employment for another three (3) routes for doing a comparison up to the condition of the mapping as shown below:
This mapping condition will be the key value of our mapping system. Where the result of all the process are began to be verified in correlation to our setting target which we have written in 'the info's wiki'. On our case 'the info's wiki' is no other than this wiki that you are reading now..

Unrouting

When you follow the step which has been passed by the process you can mark that there are the same number of eight (8) steps happen either by the 2nd and the 3rd employment.

This is a kind of pairing that you will find by the whole of our system. Every kind of process that was occurred then it will got the same kind of form or route by the opposite direction.

The eight (8) steps were done. You see there is three (3) steps also happen which did their task for a comparison. So then another three (3) steps will also happen to make they even.

The another three (3) steps will happen on opposite direction just exactly follow to what we have explained where they will be occurred on the paired form of the first three (3) steps is happen means it will be occurred on the main of info and the hyip world.

See the grey box that staying now on the wiki of main info. It will go three (3) steps on opposite direction of the route from the three (3) steps of the black box up to the mapping condition as shown below:

The opposite route of the grey box is called UnRouting stand as the verification to the result of comparison process.

The special thing with the UnRouting is that the process involves the whole system as a part of overall mapping which we have described on the beginning of our concept explanation.

Portraying on Repo

The eight (8) steps were done. You see there is three (3) steps also happen which did their task for a comparison. So then another three (3) steps will also happen to make they even.

On Repo

By this UnRouting so now it left only the last process that happen within two (2) steps consist of one step of black box and one step of grey box formed in an opposite direction to each other.

Unforming

The another three (3) steps will happen on opposite direction just exactly follow to what we have explained where they will be occurred on the paired form of the first three (3) steps is happen means it will be occurred on the main of info and the hyip world.

This step is in correlation with the structure and GitHub API.

We shall get a programmatic way to translate what we have written on this wiki to become the process on the repo.
We have do the writing in this wiki then we shall go this vise versa (unrouted).
That will become the key value of all the mapping.

Key Value Mapping

Means that what you read on this wiki is what that written in the repo.
It is left now the last (two) steps to finalize all the process.

This step is called "UnFormed". Stand as the key of all process that were done where the whole process can be declared as successfully gain the target when the two (2) box are satisfy each other.

Means the repo and wiki are in the same algorithm.
See here everything is back to normal.
All back to a routine.
Settled.

Conclusion

Congratulations! You've finally reached the end of our Documentation Section of Mapping on our project. Hopefully you can follow and enable to understand to what we have explained.

It might be on your question now about what really the content of each repos and wikis are. Well they will be a quite similar with what we have described on this section.

As you are aware this section is about a process of what we called as `info`. We collect, create and write on the code to proceed all aspect into the repo in related to its part on the concept, and explain it in the same configuration into the topics arrangement of its wiki.

You may find that we started this wiki with the concept on how we are going to read an info, how we write the info, following with on how we manage and organize it till a kind of its routing in our mapping system on the last chapter of the section that you are reading now.

You will get also a similar thing on other sections as well. Just for example you may see a kind of route mapping on our blog that correlated with our `monitor` section, or you may find a site ranking of hyip forum and hyip monitor that were made in relevant with the topic of `rating`.

So kind of the same thing are done also on each of sections provided in a different topic and purposes as they have their own assignment on the system follow to the concept.

That is all what we can say about our concept. We can’t say that all are true but at least here is our chance of to explain a way to find something that we believe is being true.

Every empirical case on the nature or in our live on this universe are sometimes not easy to define of what the true is. So the best is to let them answer by themselves. What we need is only to find a way to understand when they speak on their languages.

Just do the way they want. Not of what you think.
Let them find their way to help you get what you want.

Thank you for reading our concept. We appreciate your taking the time for it. You may now just take a look to the appearance of all the system on our Project Map.

This wiki is courtesy of The HYIP Project. Find all of them on The Project Map.
🔼 Intro ◀️ Prev 🔁 Reload Next ▶️ Last 🔽
Clone this wiki locally