You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18-13Lines changed: 18 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,33 +5,39 @@
5
5
## Adding new content to the website
6
6
7
7
### **Adding up blogs.**
8
+
8
9
Add your article as a new markdown file in the [Blogs directory](https://github.com/intelowlproject/intelowlproject.github.io/tree/develop/Blogs) with the same title as the file.
9
10
10
-
If you are an IntelOwl contributor and you would like to add content on this blog which is related to IntelOwl, feel free to fork this repository and submit an article! We will review it and publish it!
11
+
If you are an IntelOwl contributor and you would like to add content on this blog which is related to IntelOwl, feel free to fork this repository and submit an article! We will review it and publish it!
11
12
12
13
### **Adding up a new feature/testimonial/sponsor.**
13
14
14
15
In [Constants folder](https://github.com/intelowlproject/intelowlproject.github.io/tree/develop/constants), you can add the content for specific section in thier specific file in form of these json objects, no need to scour the codebase.
15
16
16
17
Features in `featuresdata.ts`
17
-
```(json)
18
+
19
+
```(json)
18
20
{
19
-
"color": "lighter",
20
-
"title":"feature name",
21
-
"description":"feature desc"
21
+
"color": "lighter",
22
+
"title":"feature name",
23
+
"description":"feature desc"
22
24
}
23
25
```
26
+
24
27
(color here defines the shade of the container which would be rendered.)
25
28
26
29
Testimonials in `testimonialdata.ts`
27
-
```(json)
30
+
31
+
```(json)
28
32
{
29
-
name: "meh",
30
-
designation: "engineer",
31
-
review: "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
33
+
name: "meh",
34
+
designation: "engineer",
35
+
review: "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
32
36
}
33
37
```
38
+
34
39
Sponsors in `sponsordata.ts`
40
+
35
41
```
36
42
{
37
43
companyname: "ushfhjhb",
@@ -42,8 +48,8 @@ Sponsors in `sponsordata.ts`
42
48
}
43
49
```
44
50
45
-
46
51
Faq's in `faqdata.ts`
52
+
47
53
```
48
54
{
49
55
question: "Lorem ipsum dolor sit a",
@@ -52,15 +58,14 @@ Faq's in `faqdata.ts`
52
58
```
53
59
54
60
### **Contributor Notes**
55
-
Make sure to go through the [contribute](https://intelowl.readthedocs.io/en/latest/Contribute.html#create-a-pull-request) section here, before creating your pr.
56
61
62
+
Make sure to go through the [contribute](https://intelowlproject.github.io/docs//Contribute.html#create-a-pull-request) section here, before creating your pr.
57
63
58
64
While testing any markdown related changes, if you run into any issue, you can do `npx --no-install contentlayer build` to generate the contentlayer content yourself, through your vscode terminal.
answer:'That is super fast and straightforward: follow the guide <a href="https://intelowl.readthedocs.io/en/latest/Installation.html" target="_blank">here</a>'
5
-
},
6
-
{
7
-
question: "I have several technical doubts regarding that can't just be answered at Issues. Whom I should contact? ",
8
-
answer:'Join our <a href="https://gsoc-slack.honeynet.org/" target="_blank" >Slack community</a> where all our Development goes on. Otherwise you can contact the authors via the <a href="https://twitter.com/intel_owl" target="_blank" >official IntelOwl Twitter account</a>'
9
-
},
10
-
{
11
-
question: "I have found one API / external service which can be included in IntelOwl. What next?",
12
-
answer:'Great! Head over to <a href="https://github.com/intelowlproject/IntelOwl/issues" >GitHub Issues</a> and open a new one. Contribute to it if you wish, else just leave it there. Rest of things will be taken care of by us.'
13
-
},
14
-
{
15
-
question: "I would like to sponsor IntelOwl How can I do it?",
16
-
answer:'Great! You can go towards the <a href="https://opencollective.com/intelowl-project/donate" target="_blank">Open Collective site</a> and choose how much you would like to contribute! Even a little donation is really meaningful for us! If you are a company, please remember that the donation can be deducted from taxes because, thanks to Open Collective, we have the same legal status of a non-profit association'
17
-
},
18
-
]
19
-
20
-
2
+
{
3
+
question: "How can I install IntelOwl?",
4
+
answer:
5
+
'That is super fast and straightforward: follow the guide <a href="https://intelowlproject.github.io/docs//Installation.html" target="_blank">here</a>',
6
+
},
7
+
{
8
+
question:
9
+
"I have several technical doubts regarding that can't just be answered at Issues. Whom I should contact? ",
10
+
answer:
11
+
'Join our <a href="https://gsoc-slack.honeynet.org/" target="_blank" >Slack community</a> where all our Development goes on. Otherwise you can contact the authors via the <a href="https://twitter.com/intel_owl" target="_blank" >official IntelOwl Twitter account</a>',
12
+
},
13
+
{
14
+
question:
15
+
"I have found one API / external service which can be included in IntelOwl. What next?",
16
+
answer:
17
+
'Great! Head over to <a href="https://github.com/intelowlproject/IntelOwl/issues" >GitHub Issues</a> and open a new one. Contribute to it if you wish, else just leave it there. Rest of things will be taken care of by us.',
18
+
},
19
+
{
20
+
question: "I would like to sponsor IntelOwl How can I do it?",
21
+
answer:
22
+
'Great! You can go towards the <a href="https://opencollective.com/intelowl-project/donate" target="_blank">Open Collective site</a> and choose how much you would like to contribute! Even a little donation is really meaningful for us! If you are a company, please remember that the donation can be deducted from taxes because, thanks to Open Collective, we have the same legal status of a non-profit association',
As open source project maintainers, we strongly rely on external support to get the resources and time to work on keeping the project alive, with a constant release of new features, bug fixes and general improvements. Thanks to all the following Sponsors!
132
+
As open source project maintainers, we strongly rely on external
133
+
support to get the resources and time to work on keeping the project
134
+
alive, with a constant release of new features, bug fixes and
135
+
general improvements. Thanks to all the following Sponsors!
0 commit comments