52 | {% endblock %}
53 |
--------------------------------------------------------------------------------
/gmt/static/JavaScript/writers/create-articles.js:
--------------------------------------------------------------------------------
1 | const checkbox = document.getElementById('is_published');
2 | const submitBtn = document.getElementById('submit-btn');
3 | checkbox.addEventListener('change', (event) => {
4 | submitBtn.disabled = !event.target.checked;
5 | });
6 | const preview = document.getElementById('wmd-preview');
7 | const input = document.getElementById('wmd-input');
8 |
9 | preview.addEventListener('DOMSubtreeModified', () => {
10 | if (preview.offsetHeight > 300) {
11 | input.style.height = preview.offsetHeight + 'px';
12 | }
13 | });
14 |
15 | input.addEventListener('input', () => {
16 | if (input.value === '') {
17 | input.style.height = '300px';
18 | }
19 | });
20 |
21 | // on load function
22 | document.addEventListener('DOMContentLoaded', () => {
23 | setTimeout(() => {
24 | // gets the ul element which contains li items with span children(the icons)
25 | const iconList = document.getElementById('wmd-button-row');
26 | for (let i = 0; i < iconList.children.length; i++) {
27 | // checks if the item is a button
28 | if (iconList.children[i].classList.contains('wmd-button'))
29 | // sets the background image of the span child
30 | iconList.children[i].children[0].style.backgroundImage = "url('https://cdn.goodmorningtech.news/website/writers/iconpack.png')";
31 | }
32 | }, 1000)
33 | });
34 |
35 | toggleCategory = (category) => {
36 | const element = document.getElementById(category);
37 | const cross = element.parentElement.getElementsByClassName('fas ml-2')[0]
38 | if (cross.classList.contains('fa-plus')) {
39 | if (categories === maxCategories) {
40 | element.checked = false;
41 | alert('You can only add 3 categories to an article. To add more remove other ones.');
42 | return;
43 | } else {
44 | categories++;
45 | }
46 | } else {
47 | categories--;
48 | }
49 | element.parentElement.classList.toggle('border-[1px]');
50 | element.parentElement.classList.toggle('border-[2px]');
51 | element.parentElement.classList.toggle('shadow-lg');
52 | element.parentElement.classList.toggle('border-black');
53 |
54 | // gets text-somecolor-800 class from parent and adds a border with that color
55 | const color = element.parentElement.classList.toString().split(' ').filter((item) => item.includes('text-')).filter((item) => item.includes('-800'))[0].split('text-')[1];
56 | element.parentElement.classList.toggle(`border-${color}`);
57 |
58 | cross.classList.toggle('fa-plus');
59 | cross.classList.toggle('fa-xmark');
60 | }
61 |
62 | const categoryList = document.getElementById('category-list');
63 | const maxCategories = 3;
64 | let categories = 0;
65 |
--------------------------------------------------------------------------------
/gmt/views/api.py:
--------------------------------------------------------------------------------
1 | import datetime
2 |
3 | from bson import ObjectId
4 | from flask import Blueprint, Response, render_template, request, current_app
5 | from flask_login import current_user
6 | from flask_mail import Message
7 |
8 | from gmt import mongo, mail
9 | from gmt.utils import parse_json, rate_limit
10 |
11 | bp = Blueprint("api", __name__)
12 |
13 |
14 | @bp.route("/api/", methods=("POST", "GET"))
15 | def api():
16 | if current_user.is_authenticated:
17 | current_user.writer = mongo.db.writers.find_one(
18 | {"_id": ObjectId(current_user.id)}
19 | )
20 |
21 | if request.method == "POST":
22 | user_email = request.form.get("email")
23 |
24 | user = mongo.db.users.find_one({"email": user_email, "confirmed": True})
25 | if not user:
26 | return render_template(
27 | "api/api.html",
28 | error="To get an API key, you must be subscribed with the email you enter.",
29 | )
30 |
31 | msg = Message(
32 | "Your API Key",
33 | recipients=[user_email],
34 | sender=("Good Morning Tech", current_app.config["MAIL_USERNAME"]),
35 | body=f"""The API key for your account is: {user["_id"]}\nIf you didn't request this, you can safely ignore this email.""",
36 | )
37 | mail.send(msg)
38 | return render_template(
39 | "api/api.html",
40 | error=None,
41 | success="Your API key has been sent to your email address.",
42 | )
43 |
44 | return render_template("api/api.html", error=None)
45 |
46 |
47 | @bp.route("/api/news/")
48 | @rate_limit(limit=100, per=60)
49 | def news():
50 | api_key = request.headers.get("X-API-KEY")
51 | if not api_key:
52 | return Response(status=401)
53 |
54 | if not ObjectId.is_valid(api_key):
55 | return Response(status=401)
56 |
57 | user = mongo.db.users.find_one({"_id": ObjectId(api_key)})
58 | # if the user with that id isn't in the db, return 401
59 | if not user:
60 | return Response(status=401)
61 |
62 | sources = request.args.get("sources")
63 | if sources:
64 | sources = sources.split(",")
65 | posts = list(
66 | mongo.db.articles.find(
67 | {
68 | "source": {"$in": sources},
69 | "date": {
70 | "$gte": datetime.datetime.utcnow()
71 | - datetime.timedelta(hours=25)
72 | },
73 | }
74 | )
75 | )
76 | else:
77 | posts = list(
78 | mongo.db.articles.find(
79 | {
80 | "date": {
81 | "$gte": datetime.datetime.utcnow()
82 | - datetime.timedelta(hours=25)
83 | }
84 | }
85 | )
86 | )
87 |
88 | return parse_json(posts)
89 |
--------------------------------------------------------------------------------
/gmt/templates/general/privacy_policy.html:
--------------------------------------------------------------------------------
1 | {% extends "layout.html" %}
2 | {% block title %}Privacy Policy{% endblock %}
3 | {% block body %}
4 |
5 |
Privacy Policy
6 |
7 |
8 | We take your privacy seriously. Please read this Privacy Policy to learn more about how we collect, use and protect your personal information.
9 |
10 |
1. Information Collection and Use
11 |
We may collect the following types of personal information:
12 |
13 |
Contact information such as name and email address
14 |
User provided Information. (Social media accounts for example)
15 |
16 |
We use this information to send you news.
17 |
18 | We will not sell, distribute or lease your personal information to third parties unless we have your permission or are required by law to do so.
19 |
20 |
2. Security
21 |
22 | We are committed to ensuring that your information is secure. In order to prevent unauthorized access or disclosure, we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online.
23 |
24 |
3. Cookies
25 |
26 | We use cookies to keep the website running, like saving your log in. A cookie is a small text file that a website saves on your computer or mobile device when you visit the site. You can control cookies through your browser settings.
27 |
28 |
4. Links to Other Websites
29 |
30 | Our website may contain links to other websites of interest. However, once you have used these links to leave our site, you should note that we do not have any control over that other website. Therefore, we cannot be responsible for the protection and privacy of any information which you provide while visiting such sites and such sites are not governed by this Privacy Policy.
31 |
32 |
5. Changes to This Privacy Policy
33 |
34 | We reserve the right to update or change this Privacy Policy at any time. If we make material changes to this Privacy Policy, we will notify you either through the email address you have provided us, or by placing a prominent notice on our website.
35 |
36 |
37 | If you have any questions or concerns about this Privacy Policy, please contact us at support@goodmorningtech.news.
38 |
39 |
40 | {% endblock %}
41 |
--------------------------------------------------------------------------------
/.github/workflows/codeql.yml:
--------------------------------------------------------------------------------
1 | # For most projects, this workflow file will not need changing; you simply need
2 | # to commit it to your repository.
3 | #
4 | # You may wish to alter this file to override the set of languages analyzed,
5 | # or to provide custom queries or build logic.
6 | #
7 | # ******** NOTE ********
8 | # We have attempted to detect the languages in your repository. Please check
9 | # the `language` matrix defined below to confirm you have the correct set of
10 | # supported CodeQL languages.
11 | #
12 | name: "CodeQL"
13 |
14 | on:
15 | push:
16 | branches: [ "master" ]
17 | pull_request:
18 | # The branches below must be a subset of the branches above
19 | branches: [ "master" ]
20 | schedule:
21 | - cron: '33 7 * * 6'
22 |
23 | jobs:
24 | analyze:
25 | name: Analyze
26 | runs-on: ubuntu-latest
27 | permissions:
28 | actions: read
29 | contents: read
30 | security-events: write
31 |
32 | strategy:
33 | fail-fast: false
34 | matrix:
35 | language: [ 'python' ]
36 | # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ]
37 | # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
38 |
39 | steps:
40 | - name: Checkout repository
41 | uses: actions/checkout@v3
42 |
43 | # Initializes the CodeQL tools for scanning.
44 | - name: Initialize CodeQL
45 | uses: github/codeql-action/init@v2
46 | with:
47 | languages: ${{ matrix.language }}
48 | # If you wish to specify custom queries, you can do so here or in a config file.
49 | # By default, queries listed here will override any specified in a config file.
50 | # Prefix the list here with "+" to use these queries and those in the config file.
51 |
52 | # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
53 | # queries: security-extended,security-and-quality
54 |
55 |
56 | # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
57 | # If this step fails, then you should remove it and run the build manually (see below)
58 | - name: Autobuild
59 | uses: github/codeql-action/autobuild@v2
60 |
61 | # ℹ️ Command-line programs to run using the OS shell.
62 | # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
63 |
64 | # If the Autobuild fails above, remove it and uncomment the following three lines.
65 | # modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance.
66 |
67 | # - run: |
68 | # echo "Run, Build Application using script"
69 | # ./location_of_script_within_repo/buildscript.sh
70 |
71 | - name: Perform CodeQL Analysis
72 | uses: github/codeql-action/analyze@v2
73 | with:
74 | category: "/language:${{matrix.language}}"
75 |
--------------------------------------------------------------------------------
/gmt/templates/auth/unsubscribe.html:
--------------------------------------------------------------------------------
1 | {% extends "layout.html" %}
2 | {% block title %}Unsubscribe{% endblock %}
3 | {% block body %}
4 |
20 |
22 |
23 |
26 |
27 |
28 |
29 | We hate to see you leave...
30 |
31 |
32 | Enter your email below & we'll send you a link and some instructions to help you unsubscribe.
33 |
34 | {% if error %}
{{ error }}
{% endif %}
35 |
50 |
51 | In case you ever change your mind, we'll always be there for you. Visit this link.
52 |
8 | By using our website, you agree to comply with and be bound by the following terms and conditions of use:
9 |
10 |
1. Introduction
11 |
12 | These Terms and Conditions ("Agreement") are between you ("User" or "you") and our company ("Company", "we", or "us"). This Agreement sets forth the general terms and conditions of your use of the website and any of its products or services.
13 |
14 |
2. Prohibited Uses
15 |
16 |
Illegal activities
17 |
Posting content that violates intellectual property rights
18 |
Spamming other users
19 |
Distributing malware or other harmful software
20 |
21 |
3. Disclaimer of Warranties
22 |
23 | The website and its products are provided “as is” without warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, or non-infringement.
24 |
25 |
4. Limitation of Liability
26 |
27 | In no event shall we or our suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption) arising out of the use or inability to use the materials on our website, even if we or an authorized representative has been notified orally or in writing of the possibility of such damage.
28 |
29 |
5. Indemnification
30 |
31 | You agree to indemnify and hold us harmless from any liability, loss, claim, and expense (including reasonable attorney's fees) related to your violation of this Agreement or use of the website and any of its products or services.
32 |
33 |
6. Governing Law
34 |
35 | This Agreement shall be governed by and construed in accordance with the laws of the State of California, United States, without giving effect to any principles of conflicts of law.
36 |
37 |
7. Changes to These Terms and Conditions
38 |
39 | We reserve the right, at our sole discretion, to modify or replace these Terms and Conditions at any time. If a revision is material, we will provide at least 30 days notice prior to any new terms taking effect. What constitutes a material change will be determined at our sole discretion.
40 |
41 |
If you have any questions about these Terms of Service, please contact us at support@goodmorningtech.news.
8 | These guidelines outline the expectations for writers creating content on behalf of Good Morning Tech for use in our newsletters. These guidelines apply to any writer who creates content on behalf of the Company, including employees and independent contractors.
9 |
10 |
Original content
11 |
12 | Good Morning Tech values original research and insights. All writers must strive to deliver unique information, whether through exclusive data or interviews with industry experts. Plagiarism is strictly prohibited.
13 |
14 |
Tone
15 |
16 | Our newsletters are personal in nature. Therefore, writers should maintain a conversational tone that is engaging and easy to read. Technical language and jargon should be avoided whenever possible. All content should be written in a manner that is sensitive to our readers.
17 |
18 |
Supporting Evidence
19 |
20 | While Good Morning Tech values unique insights, it is also critical to provide supporting evidence for such insights. This includes links to relevant studies, reports or news articles. Writers should always respect copyright laws and fair use guidelines when referencing other sources.
21 |
22 |
Objectivity and Bias
23 |
24 | Our readers trust us to provide accurate and balanced information. Therefore, writers must remain objective and unbiased in their writing. If an article has a strong point of view, it must be clearly labeled as an opinion piece. The Company reserves the right to reject content which breaches its standards of impartiality.
25 |
26 |
Attribution
27 |
28 | If a writer references another source in their work, it is essential that they provide clear attribution. This includes proper citation and providing a link to the original article wherever possible. The Company retains the right to verify all references made in any submitted content.
29 |
30 |
Proofreading and Fact-Checking
31 |
32 | Accuracy is paramount when it comes to writing for our newsletters. Therefore, all writers must thoroughly proofread their work and fact-check any information before submitting it. The Company reserves the right to verify all facts presented in any submitted content.
33 |
34 |
Feedback
35 |
36 | Writers must be open to receiving feedback from editors and other team members. This will help to ensure that the final product is the best it can be. All critique and feedback will be delivered in a respectful and constructive manner.
37 |
38 |
Conclusion
39 |
40 | Good Morning Tech values originality, accuracy, objectivity, and professionalism in all content created for our newsletters. By adhering to these guidelines, writers will be contributing towards maintaining standards and quality of our newsletters.
41 |
42 |
Acceptance
43 |
44 | All writers must accept these guidelines before creating their first article. By submitting content or accepting payment, writers acknowledge their acceptance of these guidelines.
45 |
Python for the backend. HTML5, CSS3 and Javascript for the frontend
14 |
15 | Tech Stack
16 |
17 |
18 | For the backend we used Flask together with MongoDB for the Database. For the
19 | frontend we used Jinja Templates and Tailwind. For the website hosting we used Vercel and for the emails and
20 | Images we used Cybrancee.
21 |
22 | For a more detailed technical breakdown, check out Levani's article about it. (not yet written)
23 |
46 | Special thanks to Lewis Menelaws(Coding with Lewis) for having faith in the project and giving us
47 | the goodmorningtech.news domain.
48 |
49 |
50 | Disclaimer news content
51 |
52 |
53 | We would like to take a moment to clarify that not all of the news content on
54 | our website is our original work. As a news aggregator, we strive to provide our readers with the latest and
55 | most accurate news from various reliable sources.
56 | While we do publish some original content, a significant portion of the news articles you will find on our
57 | website are sourced from other news outlets. We carefully select and curate the news stories that we believe are
58 | most relevant and informative to our readers, and we always provide proper attribution to the original sources.
59 | We encourage our readers to visit the original sources of the news articles we publish to gain a more
60 | comprehensive understanding of the topics covered. We also welcome any feedback or suggestions on how we can
61 | improve our news coverage and better serve our readers.
62 | Thank you for your continued support and trust in our website as a source of news and information.
63 |
64 |
65 | {% endblock %}
66 |
--------------------------------------------------------------------------------
/gmt/static/JavaScript/writers/user-apply.js:
--------------------------------------------------------------------------------
1 | let totalSteps = document.getElementById('totalSteps');
2 | let currentStep = document.getElementById('currentStep');
3 |
4 | let email = document.getElementById('userEmail');
5 | let contact = document.getElementById('userContact');
6 | let displayName = document.getElementById('username');
7 |
8 | let stepOne = document.getElementById('stepOne');
9 | let stepOneBtn = document.getElementById('nextBtnStepOne');
10 |
11 | const progressBar = document.getElementById('progressBar');
12 |
13 | stepOneBtn.addEventListener('click', function () {
14 | if (email.value === '' || contact.value === '' || displayName.value === '') {
15 | if (email.value === '') {
16 | email.classList.add('border-red-500', 'border-2');
17 | }
18 | if (contact.value === '') {
19 | contact.classList.add('border-red-500', 'border-2');
20 | }
21 | if (displayName.value === '') {
22 | displayName.classList.add('border-red-500', 'border-2');
23 | }
24 | } else {
25 | stepOne.classList.add('hidden');
26 | stepTwo.classList.remove('hidden');
27 | currentStep.textContent = 2;
28 | progressBar.classList.remove('w-1/3');
29 | progressBar.classList.add('w-2/3');
30 | }
31 | });
32 |
33 | email.addEventListener('blur', function () {
34 | email.classList.remove('border-red-500', 'border-2');
35 | });
36 | contact.addEventListener('blur', function () {
37 | contact.classList.remove('border-red-500', 'border-2');
38 | });
39 | displayName.addEventListener('blur', function () {
40 | displayName.classList.remove('border-red-500', 'border-2');
41 | });
42 |
43 | const checkEmail = () => {
44 | if (email.value.includes('@') && email.value.includes('.')) {
45 | email.classList.remove('border-red-500', 'border-2');
46 | email.classList.add('border-green-500', 'border-2');
47 | } else {
48 | email.classList.remove('border-green-500', 'border-2');
49 | email.classList.add('border-red-500', 'border-2');
50 | }
51 | }
52 | email.addEventListener('click', checkEmail);
53 | email.addEventListener('input', checkEmail);
54 | email.addEventListener('blur', checkEmail);
55 |
56 | let goBackBtnStepTwo = document.getElementById('backBtnStepTwo');
57 | let stepTwoBtn = document.getElementById('nextBtnStepTwo');
58 | let stepTwo = document.getElementById('stepTwo');
59 |
60 | let whyWrite = document.getElementById('whyWrite');
61 | let topics = document.getElementById('topics');
62 |
63 | goBackBtnStepTwo.addEventListener('click', function () {
64 | stepTwo.classList.add('hidden');
65 | stepOne.classList.remove('hidden');
66 | currentStep.textContent = 1;
67 | progressBar.classList.remove('w-2/3');
68 | progressBar.classList.add('w-1/3');
69 | });
70 |
71 | stepTwoBtn.addEventListener('click', function () {
72 | if (whyWrite.value === '' || topics.value === '') {
73 | if (whyWrite.value === '') {
74 | whyWrite.classList.add('border-red-500', 'border-2');
75 | }
76 | if (topics.value === '') {
77 | topics.classList.add('border-red-500', 'border-2');
78 | }
79 | } else {
80 | stepTwo.classList.add('hidden');
81 | stepThree.classList.remove('hidden');
82 | currentStep.textContent = 3;
83 | progressBar.classList.remove('w-2/3');
84 | progressBar.classList.add('w-full');
85 | }
86 | }
87 | );
88 |
89 | whyWrite.addEventListener('blur', function () {
90 | whyWrite.classList.remove('border-red-500', 'border-2');
91 | });
92 |
93 | topics.addEventListener('blur', function () {
94 | topics.classList.remove('border-red-500', 'border-2');
95 | });
96 |
97 | let goBackBtnStepThree = document.getElementById('backBtnStepThree');
98 | let stepThree = document.getElementById('stepThree');
99 |
100 | goBackBtnStepThree.addEventListener('click', function () {
101 | stepThree.classList.add('hidden');
102 | stepTwo.classList.remove('hidden');
103 | currentStep.textContent = 2;
104 | progressBar.classList.remove('w-full');
105 | progressBar.classList.add('w-2/3');
106 | });
107 |
108 | let submitFormBtn = document.getElementById('submitFormBtn');
109 | let sample = document.getElementById('sample');
110 | let article = document.getElementById('article');
111 | let checkbox = document.getElementById('terms');
112 |
113 | const checkButton = () => {
114 | submitFormBtn.disabled = article.value === '' || checkbox.checked === false;
115 | }
116 |
117 | document.addEventListener('DOMContentLoaded', checkButton);
118 | article.addEventListener('input', checkButton);
119 | checkbox.addEventListener('click', checkButton);
120 |
121 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to GoodMorningTech 💻📝
2 |
3 | Thank you for your interest in contributing to GoodMorningTech! 🙌 Whether you're a programmer 💻, writer 📝, or community helper 🤝, your contributions are greatly appreciated.
4 |
5 | ## Table of Contents
6 | 1. [How to Contribute](#how-to-contribute-)
7 | 2. [Code of Conduct](#code-of-conduct-)
8 | 3. [Getting Started](#getting-started-)
9 | 4. [Bug Reporting](#bug-reporting-)
10 | 5. [Enhancement Requests](#enhancement-requests-)
11 | 6. [Contact Information](#contact-information-)
12 |
13 | ## How to Contribute 🤔
14 |
15 | Here are a few ways you can contribute to the GoodMorningTech project:
16 |
17 | - **Programming**: If you have programming experience and would like to contribute to the code base, check out the [open issues](https://github.com/GoodMorninTech/GoodMorningTech/issues) to see what needs to be done or create an issue or pull request, and we will review it. Before you start working on a new feature or bug fix, make sure to fork the project and work on the development branch and open a pull request when you're ready to submit your changes. 💻
18 |
19 | - **Writing**: If you have a passion for writing and would like to contribute to our news, Apply at this link [Application Link](https://goodmorningtech.news/writers/apply), if we accept you we will reach out. 📝
20 |
21 | - **Community Help**: If you'd like to help out the community in any way, let us know, or join our [discord](https://discord.goodmorningtech.news)! We're always looking for ways to improve and make a positive impact. 🤝
22 |
23 | ## Code of Conduct 📜
24 |
25 | To ensure that the GoodMorningTech community is welcoming and inclusive to all, we have a [Code of Conduct](CODE_OF_CONDUCT.md) that all contributors must follow. Please take a moment to read it before contributing.
26 |
27 | ## Getting Started 🚀
28 |
29 | To get started fork the Repository on GitHub.
30 |
31 | ### Prerequisites
32 | - Python
33 | - Node.js
34 |
35 | If you don't have these just install them from the official websites.
36 |
37 | #### Cloning the repository
38 | Clone the forked repository(make sure to insert your username):
39 | ```
40 | git clone https://github.com/YOURGITHUBUSERNAME/GoodMorningTech.git
41 | ```
42 | Move into the new directory:
43 | ```
44 | cd GoodMorningTech
45 | ```
46 | #### Configuration
47 | Create an `instance` folder:
48 | ```
49 | mkdir instance
50 | ```
51 | Move the configuration template into `instance` and rename it to `config.py`:
52 | Windows:
53 | ```
54 | copy config.template.py config.py
55 | move config.py instance
56 | ```
57 | Linux:
58 | ```
59 | cp config.template.py config.py
60 | mkdir instance
61 | mv config.py instance/config.py
62 | ```
63 | Edit the configuration file and set the fields to your liking.
64 |
65 | For the database to work create a mongoDB database and set the `MONGO_URI` to your database.
66 |
67 | To use the email functionality set the `MAIL_USERNAME`,`MAIL_PASSWORD` and `MAIL_SERVER`
68 | to your email credentials, for gmail you might need to configure extra stuff,
69 | look up recent guides on how to use SMTP with gmail.
70 |
71 | Alternatively you can configure everything from environment variables, make sure to set all the variables in `config.template.py`.
72 |
73 | #### Set Up for Development
74 | Install the development requirements:
75 | ```
76 | pip install -r requirements-dev.txt
77 | ```
78 | ```
79 | npm install
80 | ```
81 |
82 | [//]: # (#### Install pre-commit hooks:)
83 |
84 | [//]: # (```)
85 |
86 | [//]: # (pre-commit install)
87 |
88 | [//]: # (```)
89 |
90 | #### Running the Server
91 | Install the requirements:
92 | ```
93 | pip install -r requirements.txt
94 | ```
95 | Run the application:
96 | ```
97 | python -m flask --app gmt --debug run
98 | ```
99 | and in separate terminal run the tailwind compiler:
100 | ```
101 | npm run tailwind
102 | ```
103 |
104 | ## Bug Reporting 🐛
105 |
106 | If you find a bug in the project, we would love to know about it! Before reporting a bug, please check the [open issues](https://github.com/GoodMorninTech/GoodMorningTech/issues) to see if it has already been reported. If not, please create a new issue and provide as much detail as possible about the bug, including steps to reproduce it.
107 |
108 | ## Enhancement Requests 💡
109 |
110 | If you have an idea for a new feature or enhancement, we'd love to hear about it! Before creating a new enhancement request, please check the [open issues](https://github.com/GoodMorninTech/GoodMorningTech/issues) to see if it has already been suggested. If not, please create a new issue and provide as much detail as possible about the enhancement.
111 |
112 | ## Contact Information 📞
113 |
114 | If you have any questions or would like to get in touch with us, feel free to send us an email at [support@goodmorningtech.news](mailto:support@goodmorningtech.news) or join our Discord server at [discord.goodmorningtech.news](https://discord.goodmorningtech.news/). We're always here to help and support you in your contributions! 🤗
115 |
--------------------------------------------------------------------------------
/gmt/static/JavaScript/writers/create-profile.js:
--------------------------------------------------------------------------------
1 | let totalSteps = document.getElementById('totalSteps');
2 | let currentStep = document.getElementById('currentStep');
3 |
4 | let email = document.getElementById('userEmail');
5 | let name = document.getElementById('username');
6 | let displayName = document.getElementById('displayName');
7 |
8 | let stepOne = document.getElementById('stepOne');
9 | let stepOneBtn = document.getElementById('nextBtnStepOne');
10 |
11 | const progressBar = document.getElementById('progressBar');
12 |
13 | stepOneBtn.addEventListener('click', function () {
14 | if (email.value === '' || name.value === '' || displayName.value === '') {
15 | if (email.value === '') {
16 | email.classList.add('border-red-500', 'border-2');
17 | }
18 | if (name.value === '') {
19 | name.classList.add('border-red-500', 'border-2');
20 | }
21 | if (displayName.value === '') {
22 | displayName.classList.add('border-red-500', 'border-2');
23 | }
24 | } else {
25 | stepOne.classList.add('hidden');
26 | stepTwo.classList.remove('hidden');
27 | currentStep.textContent = 2;
28 | progressBar.classList.remove('w-1/3');
29 | progressBar.classList.add('w-2/3');
30 | }
31 | });
32 |
33 | email.addEventListener('blur', function () {
34 | email.classList.remove('border-red-500', 'border-2');
35 | });
36 | name.addEventListener('blur', function () {
37 | name.classList.remove('border-red-500', 'border-2');
38 | });
39 | displayName.addEventListener('blur', function () {
40 | displayName.classList.remove('border-red-500', 'border-2');
41 | });
42 |
43 | const checkEmail = () => {
44 | if (email.value.includes('@') && email.value.includes('.')) {
45 | email.classList.remove('border-red-500', 'border-2');
46 | email.classList.add('border-green-500', 'border-2');
47 | } else {
48 | email.classList.remove('border-green-500', 'border-2');
49 | email.classList.add('border-red-500', 'border-2');
50 | }
51 | }
52 | email.addEventListener('click', checkEmail);
53 | email.addEventListener('input', checkEmail);
54 | email.addEventListener('blur', checkEmail);
55 |
56 | let goBackBtnStepTwo = document.getElementById('backBtnStepTwo');
57 | let stepTwoBtn = document.getElementById('nextBtnStepTwo');
58 | let stepTwo = document.getElementById('stepTwo');
59 |
60 | let password = document.getElementById('password');
61 | let repeatPassword = document.getElementById('repeatPassword');
62 |
63 | goBackBtnStepTwo.addEventListener('click', function () {
64 | stepTwo.classList.add('hidden');
65 | stepOne.classList.remove('hidden');
66 | currentStep.textContent = 1;
67 | progressBar.classList.remove('w-2/3');
68 | progressBar.classList.add('w-1/3');
69 | });
70 |
71 | stepTwoBtn.addEventListener('click', function () {
72 | if (password.value === '' || repeatPassword.value === '') {
73 | if (password.value === '') {
74 | password.classList.add('border-red-500', 'border-2');
75 | }
76 | if (repeatPassword.value === '') {
77 | repeatPassword.classList.add('border-red-500', 'border-2');
78 | }
79 | } else {
80 | if (password.value === repeatPassword.value) {
81 | stepTwo.classList.add('hidden');
82 | stepThree.classList.remove('hidden');
83 | currentStep.textContent = 3;
84 | progressBar.classList.remove('w-2/3');
85 | progressBar.classList.add('w-full');
86 | } else {
87 | password.classList.add('border-red-500', 'border-2');
88 | repeatPassword.classList.add('border-red-500', 'border-2');
89 | window.alert('Your passwords do not match!');
90 | }
91 | }
92 | });
93 |
94 | password.addEventListener('blur', function () {
95 | password.classList.remove('border-red-500', 'border-2');
96 | });
97 |
98 | repeatPassword.addEventListener('blur', function () {
99 | repeatPassword.classList.remove('border-red-500', 'border-2');
100 | });
101 |
102 | let goBackBtnStepThree = document.getElementById('backBtnStepThree');
103 | let stepThree = document.getElementById('stepThree');
104 |
105 | goBackBtnStepThree.addEventListener('click', function () {
106 | stepThree.classList.add('hidden');
107 | stepTwo.classList.remove('hidden');
108 | currentStep.textContent = 2;
109 | progressBar.classList.remove('w-full');
110 | progressBar.classList.add('w-2/3');
111 | });
112 |
113 | let submitFormBtn = document.getElementById('submitFormBtn');
114 | let aboutMe = document.getElementById('aboutMe');
115 | let timezone = document.getElementById('timezone');
116 | let checkbox = document.getElementById('terms');
117 |
118 | const checkButton = () => {
119 | submitFormBtn.disabled = aboutMe.value === '' || checkbox.checked === false;
120 | }
121 |
122 | document.addEventListener('DOMContentLoaded', checkButton);
123 | aboutMe.addEventListener('input', checkButton);
124 | checkbox.addEventListener('click', checkButton);
125 |
126 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement.
63 | All complaints will be reviewed and investigated promptly and fairly.
64 |
65 | All community leaders are obligated to respect the privacy and security of the
66 | reporter of any incident.
67 |
68 | ## Enforcement Guidelines
69 |
70 | Community leaders will follow these Community Impact Guidelines in determining
71 | the consequences for any action they deem in violation of this Code of Conduct:
72 |
73 | ### 1. Correction
74 |
75 | **Community Impact**: Use of inappropriate language or other behavior deemed
76 | unprofessional or unwelcome in the community.
77 |
78 | **Consequence**: A private, written warning from community leaders, providing
79 | clarity around the nature of the violation and an explanation of why the
80 | behavior was inappropriate. A public apology may be requested.
81 |
82 | ### 2. Warning
83 |
84 | **Community Impact**: A violation through a single incident or series
85 | of actions.
86 |
87 | **Consequence**: A warning with consequences for continued behavior. No
88 | interaction with the people involved, including unsolicited interaction with
89 | those enforcing the Code of Conduct, for a specified period of time. This
90 | includes avoiding interactions in community spaces as well as external channels
91 | like social media. Violating these terms may lead to a temporary or
92 | permanent ban.
93 |
94 | ### 3. Temporary Ban
95 |
96 | **Community Impact**: A serious violation of community standards, including
97 | sustained inappropriate behavior.
98 |
99 | **Consequence**: A temporary ban from any sort of interaction or public
100 | communication with the community for a specified period of time. No public or
101 | private interaction with the people involved, including unsolicited interaction
102 | with those enforcing the Code of Conduct, is allowed during this period.
103 | Violating these terms may lead to a permanent ban.
104 |
105 | ### 4. Permanent Ban
106 |
107 | **Community Impact**: Demonstrating a pattern of violation of community
108 | standards, including sustained inappropriate behavior, harassment of an
109 | individual, or aggression toward or disparagement of classes of individuals.
110 |
111 | **Consequence**: A permanent ban from any sort of public interaction within
112 | the community.
113 |
114 | ## Attribution
115 |
116 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
117 | version 2.0, available at
118 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
119 |
120 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
121 | enforcement ladder](https://github.com/mozilla/diversity).
122 |
123 | [homepage]: https://www.contributor-covenant.org
124 |
125 | For answers to common questions about this code of conduct, see the FAQ at
126 | https://www.contributor-covenant.org/faq. Translations are available at
127 | https://www.contributor-covenant.org/translations.
128 |
--------------------------------------------------------------------------------
/gmt/templates/articles/article.html:
--------------------------------------------------------------------------------
1 | {% extends "layout.html" %}
2 | {% block title %}{{ article.title }}{% endblock %}
3 | {% block head %}
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | {% endblock %}
16 | {% block body %}
17 |
18 |
19 |
{{ article.title }}
20 |
21 | Published on: {{ article.date.strftime("%B %d, %Y") }}
22 |
51 |
52 |
53 |
54 |
55 | ## Learn more about this project
56 |
57 |
58 |
59 |
60 | ### Built With
61 | 
62 | 
63 | 
64 |
65 | 
66 | 
67 | 
68 | 
69 |
70 | 
71 | 
72 | 
73 |
74 | 
75 | 
76 | 
77 |
78 |
79 |
80 | ### Features
81 |
82 | - Timezone Selection
83 | - Day and time Selection
84 | - Article Count Selection
85 |
86 | ## Get started
87 | ### Contribute
88 | Contributing to this project is quite simple & straight forward. We'd request you to view our [contributing](https://github.com/GoodMorninTech/GoodMorningTech/blob/master/CONTRIBUTING.md) file before getting started and follow our [code of conduct](https://github.com/GoodMorninTech/GoodMorningTech/blob/master/CODE_OF_CONDUCT.md).
89 |
90 | ### Setting up on your local machine
91 | [Check out this guide](https://github.com/GoodMorninTech/GoodMorningTech/blob/master/CONTRIBUTING.md#getting-started)
92 |
93 | ## What's Planned Ahead:
94 | - [x] Time Selection
95 | - [x] Timezone Selection
96 | - [x] Addition of more news sources
97 | - [x] Blogging System
98 | - [ ] Changelog System
99 | - [ ] Support for Other Languages
100 | - [ ] French
101 | - [ ] German
102 | - [ ] Spanish
103 | - [ ] Mobile App
104 |
105 | ## Frequently Asked Question's (FAQs):
106 |
107 | #### 1. How does this work?
108 |
109 | It gets the important posts from BBC, The Guardian, Verge & other credible sources and sends them to your email.
110 |
111 | #### 2. How do I subscribe?
112 |
113 | Subscribing is as easy as heading to our [sign up page](https://goodmorningtech.news/subscribe) and giving us your email & filling a small form (we promise we won't flood your inbox).
114 |
115 | #### 3. How do I unsubscribe?
116 |
117 | We hate to see you leave, you can head to [this page](https://goodmorningtech.news/unsubscribe) and enter your email ID, we'll then send you a link to verify your exit. Alternatively, each newsletter we send you has a footer with an unsubscribe link.
118 |
119 | #### 4. How do you guys fund your project if it's completely free?
120 | We rely on donations/sponsors!
121 |
122 | ## License
123 |
124 | [MIT](https://choosealicense.com/licenses/mit/)
125 |
126 |
127 | ## Contact Us
128 | 
129 | 
130 | 
131 |
132 |
133 | ## Our team
134 | - [OpenSourceSimon](https://github.com/OpenSourceSimon) - Backend
135 | - [Kappq](https://github.com/kappq) - Backend
136 | - [ImmaHarry](https://github.com/immaharry) - Site Designer & Frontend
137 | - [LevaniVashadze](https://github.com/LevaniVashadze) - Backend & Frontend
138 |
--------------------------------------------------------------------------------
/gmt/templates/writers/portal.html:
--------------------------------------------------------------------------------
1 | {% extends "layout.html" %}
2 | {% block title %}Portal{% endblock %}
3 | {% block body %}
4 |
5 |
40 | Get tech news to your
41 | Discord Community
42 |
43 |
44 | Get the latest tech news straight to your Discord
45 | community on a channel of your choice! Get all of the customizing options offered on the email
46 | newsletter using our open-source Discord Bot,
47 | Morning!
48 |
26 | 
38 | 
41 | Return Home
43 | 
4 | 
58 |
59 |
60 | ### Built With
61 | 
62 | 
63 | 
64 | 
64 | 
69 | 
83 | 
100 | 
126 |