vim / website_next_generation Goto Github PK

The new website

License: Vim License

website_next_generation's Introduction

Overview

This is the relaunch of the new www.vim.org website. We have found a small team that will take on the beautiful task of rebuilding the website with current design and new concepts.

The new development should not take place behind closed doors, we want to make the new development public and transparent for you.

Soon there will be a test system where you can follow the current status successively.

Of course, we will involve you, the community, in the design by collecting ideas and feedback.

Requirements

Add your requirements here:

Functional Requirements

The website should continue important components
- User Accounts
- Vim Scripts community space (Filing, Versioning, Search, ...)
- Blog, Announcements
Existing contents should be migrated

Non-Functional Requirements

We want to continue using MySQL 8 as the database system.
We want the website to be fundamentally secure and avoid typical web application vulnerabilities (like SQL injection, XSS, ...) by design.
The hashing of the user passwords is to be migrated to a hashing procedure that corresponds to the state of the art.
The frontend/backend stack shall:
- should be maintainable and expandable in the future with reasonable effort
- be opensource based
- the components used should be vital
- shall be efficient with server resources

Idea collection

This is a unfinished and unstructed list of ideas:

Tutorial section
Vim tips revival
The vim tricks
My personal ".vimrc", with annotations about motivations
Blog posts and annountements for the maintainers and artive editors
Link resource section
"How to contribute" section
Vim distributions for the various platforms

website_next_generation's People

Contributors

Stargazers

Watchers

Forkers

rheber jmarsman kalisankevin signal-coder cs558i rg4sun sgrwfwn sidarth-23 seanpm2001 wildgladiator

website_next_generation's Issues

Please include a memorial to Bram Moolenaar, his relentless development of Vim, his charity work and an archive of his personal website.

The new Vim website must pay its respects to vim. I have used vim and the fedora vim enhanced package, and I appreciate all that Bram did to make the tool that I used as my text editor when in the terminal. I found the command prompt to be generally useful, and it made sense to me. ":q" is about as simple as it gets. I would also endorse updating the Vim license to replace the GPL v2 with the GNU Affero GPL v3 or later.

Create 'home' page

-Creating single page collection for 'home' page in Strapi
-Create frontend with backend 'home' endpoint connection

Make vim.org a thing

I can't remember if this was an issue with the previous vim.org, but it definitely is an issue with the current vim.org, if you ask me.

The website is hosted at www.vim.org. Using that instead of vim.org is of course a matter of taste and apparently www.vim.org has been chosen. However, at least make it so vim.org can also be resolved to an IP address, just like with www.vim.org, and set up a redirection from vim.org to www.vim.org if you're so inclined, but please, don't leave it as it is now where typing in vim.org in the address bar of your web browser leaves you only with a DNS error instead of a website. That is really unhelpful.

Implement User Authentication

Description:
We need to implement user authentication on our website to enhance security and provide personalized experiences. The existing users are stored in our database, so seamless integration is necessary.

Objectives:

Implement user authentication functionality.
Support both new user registration and existing user login.
Ensure smooth integration with the existing user database.
Provide multiple ways of login via providers such as GitHub

DevOps, CI/CD, Rollback Automations

Hi All,

I just wanted to let you know that this project can count on me to create the CI/CD and Rollback workflows using GitHub Actions or other tooling.

If the project has any other requirements inside SRE and DevOps scope, I would be glad to help.

I know that could sound like an exaggeration at this moment, but since the project is also an education project, students may find it interesting to have a bit of DevOps.

Best regards to the Vim community!

Add "News" Content Type in Strapi CMS

Objective

Add a "News" content type to the Strapi CMS for the Vim website, enabling easy management and publication of news updates and announcements.

Details

Content Type: "News" as "newsposts"
Fields:
- Title
- Content
Permissions: Set up appropriate permissions for creating, editing, and deleting news entries.
Integration: Ensure seamless integration of the "News" content type with the website frontend. Include news in the home-page response.