Skip to content

Add contribute page to complete NACSE static site structure#1

Merged
orgito1015 merged 2 commits intomainfrom
copilot/setup-static-website-structure
Feb 1, 2026
Merged

Add contribute page to complete NACSE static site structure#1
orgito1015 merged 2 commits intomainfrom
copilot/setup-static-website-structure

Conversation

Copy link
Contributor

Copilot AI commented Feb 1, 2026

Completes the NACSE (Newsletter of Applied Cybersecurity & Systems Engineering) static website structure for GitHub Pages deployment at nacse.github.io.

Changes

  • Added pages/contribute.html with submission guidelines, attribution policy, and contact information

All other required files (index.html, assets/css/style.css, issues/2026-01.html, pages/about.html, .github/workflows/jekyll-gh-pages.yml, README.md) were already in place with correct content.

Site Structure

/
├── index.html                # Landing page
├── assets/css/style.css      # Dark theme, no frameworks
├── issues/2026-01.html       # First edition
├── pages/
│   ├── about.html           
│   └── contribute.html       # NEW
└── .github/workflows/jekyll-gh-pages.yml

Screenshots

Landing Page
Landing

Contribute Page
Contribute

First Issue
Issue

Original prompt

You are working inside a GitHub repository named nacse.github.io that will be deployed with GitHub Pages using GitHub Actions.

Your task is to fully set up a professional static website for NACSE — Newsletter of Applied Cybersecurity & Systems Engineering with the following requirements:

  1. Repository structure

Create and organize the repository with this structure:

/
├─ index.html # Landing page
├─ assets/
│ ├─ css/
│ │ └─ style.css # Shared styling
├─ issues/
│ └─ 2026-01.html # First edition: "New Blog #1 — Presenting NACSE"
├─ pages/
│ ├─ about.html # About NACSE
│ └─ contribute.html # How to contribute
├─ .github/
│ └─ workflows/
│ └─ jekyll-gh-pages.yml # GitHub Pages deployment workflow
└─ README.md

  1. Content requirements

The site must be clean, minimal, dark-themed, and professional.

The landing page (index.html) must:

Clearly state the name NACSE

Include the subtitle Newsletter of Applied Cybersecurity & Systems Engineering

Explain that NACSE is a monthly newsletter

Include a link to the latest issue

Include a short contribution section stating that articles are published under the contributor’s name with full author credit

End with: An initiative by Tech with Orgito.

The first issue page (issues/2026-01.html) must be titled:
New Blog #1 — Presenting NACSE

The About page must clearly explain the scope and focus of NACSE.

The Contribute page must clearly state:

Articles, tutorials, and applied write-ups are welcome

Submissions are published under the author’s name with full credit

Contributors can reach out via LinkedIn or Discord

  1. Styling

Use plain HTML and CSS only

No frameworks

Dark background

Typography suitable for technical editorial content

  1. GitHub Pages

Ensure the workflow deploys via GitHub Actions

The site must work at https://nacse.github.io

  1. README

Describe what NACSE is

Link to the live site

Mention that it is an initiative by Tech with Orgito

Generate all necessary files with correct content and commit them to the repository.

Do not ask questions — proceed with implementation.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: orgito1015 <86354243+orgito1015@users.noreply.github.com>
Copilot AI changed the title [WIP] Set up professional static website for NACSE Add contribute page to complete NACSE static site structure Feb 1, 2026
Copilot AI requested a review from orgito1015 February 1, 2026 16:09
@orgito1015 orgito1015 marked this pull request as ready for review February 1, 2026 16:23
@orgito1015 orgito1015 merged commit d258c18 into main Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants