I think the most important thing to iron out first is what the short-term
and long-term requirements are, and the basic technical design of the
website.

In particular, what are the features that require a dynamic backend rather
than a static site (e.g. something that could be hosted on a CDN or GitHub
Pages)? Do those need to be hosted together with the main site? Having a
static base site decoupled from the dynamic features would allow us to
always be able to have a basic available website for download links,
documentation, etc, even if the dynamic backend is broken / DDOSed. Even
features like blog posts etc can be easily generated by a static site
generator (e.g. Jekyll or other newer/fancier ones), but features like
plugin scripts discovery would not really be possible as they would require
an actual server.

I actually didn't know vim.org supported user accounts. What do those do?
For uploading scripts?

I think it's worth also looking at Neovim's site for comparison. I know we
don't want to just do what Neovim does, obviously, but they have spent
quite a lot of effort on building up a modern site, and do some of what
this new website proposal lists as goals, so I think it would be a good
idea to at least look at what they do for comparison. The Neovim site has:

   - news/blogs (https://neovim.io/news/)
   - builtin docs (https://neovim.io/doc/), whereas in Vim right now you
   have to go to a third party like https://vimhelp.org/, which is probably
   fine. They also put in a lot of work to create reflowable docs. This is a
   massive cans of worms that Shane is referring to above, which I don't think
   we have to do, but just something to be aware of.
   - It links to an external script discovery page (https://dotfyle.com/)
   - That site also has a "This Week in Neovim" (
   https://dotfyle.com/this-week-in-neovim/54) blog.

Nice-to-haves (as in, not needed immediately):

   - Personally I think having a nice script discovery page is actually
   quite useful. It's a nice-to-have but it helps people have a centralized
   place to find plugins to install (it's obviously an optional aspect to use
   plugins).


   - I also think Vim should eventually try to have something similar to
   the "This Week in Neovim", or just *something *that could communicate
   regular Vim updates (weekly or monthly or quarterly) and new features/bug
   fixes to the user. Right now when I write MacVim release notes (example
   <https://github.com/macvim-dev/macvim/releases/tag/release-178>) I have
   to scour through every Vim commit to distill what the interesting bits are
   to the end user. It would be nice if there's a centralized spot for Vim
   users who are not MacVim users. Not sure if this needs to be from the
   official page or not.


   - I also think having vim docs available on the web is really useful as
   I don't always have Vim available, and an URL is much easier to reference
   from Reddit and release notes (e.g. I link to online documentation
in my releases
   notes for MacVim <https://github.com/macvim-dev/macvim/releases>
   whenever it contains ":h <topic>"). We already have https://vimhelp.org
   so maybe it works as-is. There is a different discussion on Vim GitHub
   about the formatting but I'm more just talking about the availability of
   the documentation.


On Thu, Oct 12, 2023 at 7:04 PM shane qian <[email protected]> wrote:

> I think the more important is stable vs/than nice.
> or if you'd like to rephrase its looking, I would  recommend other 'org'
> website, e.g 'GNU'.
>
> and/but not really move vim help doc to website instead of native tui
> ':help', doc in web page did not always mean 'modern' as someone said in
> the repo, wish we insisted what is vim it was.
>
> --
> shane.xb.qian
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/OS3P286MB09134F75A2F37803246CF51CEBD2A%40OS3P286MB0913.JPNP286.PROD.OUTLOOK.COM
> <https://groups.google.com/d/msgid/vim_dev/OS3P286MB09134F75A2F37803246CF51CEBD2A%40OS3P286MB0913.JPNP286.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>
> .
>

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAHTeOx9z%2BUrv269MVoARTR1uULNbsoa_%3DWSkNr%2B1LHUsp%2BgQsg%40mail.gmail.com.

Raspunde prin e-mail lui