Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Revise web site organization to reflect multiple products

Aperta
  • Qualcosa non va?
#12 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
content, documentation

Direzione di ricerca

L'issue non indica file, test o punti di ingresso. Inizia esaminando la struttura attuale del sito nunit.org e i prodotti rappresentati al suo interno, quindi risolvi le questioni aperte relative alle versioni e ai link di release. Il lavoro è completato quando il sito web ha un'organizzazione dei contenuti definita e orientata ai prodotti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

design

@CharliePoole commented on Tue Mar 14 2017

The site was started when NUnit was just NUnit. When we added the VS adapter, we had two products and that didn't seem like enough to add a Products menu. Now (suddenly?) we have a bunch of things so it's past due.

My general idea is that there will be a top-level product menu with all the info (docs, downloads, etc.) for a single product on a page.

I view this as content reorganization. Any changes to the appearance can come separately, later.

@ChrisMaddock commented on Tue Mar 14 2017

I think it would be great to have everything on the website! (Tagged appropriately as: 'development' etc, of course. 😉)

A suggestion, if this area is being redone: Can we not show versions/dates, so it's one less place to keep up-to-date? We currently store all versions in GitHub releases. Could the website just link to GitHub? We could continue to update the 'recent news' for new releases.

@CharliePoole commented on Tue Mar 14 2017

@ChrisMaddock I guess my thinking is that if you have a website, you want to keep it up to date. Knowing when the last release of anything came out seems like a common user desire. I'm pretty sure, once we finalize the website (format, location, etc.) we can figure out ways to make it easier. For example, we can automate or we can have some volunteer who is the webmaster and does all that stuff.

To be clear, I'd be ready to make a decision on this unilaterally if I were hanging around, but I'm not. And the group that is succeeding me is not yet formed so as to make the decision in a formal way. I should really stop programming and get on with that, but what can I say... I'm a programmer. 😄

@CharliePoole commented on Mon Apr 24 2017

Taking my name off this. My role will be to figure out a plan for transitioning the website to the core team or to a webmaster that they designate. Any reorganization of content should happen on the new website.

@jnm2 commented on Wed Jun 28 2017

Xamarin's current templates for Android unit tests have a bootstrapper application that says for NUnitLite, see http://nunitlite.org. That gives a 404. Did it used to redirect?

@CharliePoole commented on Wed Jun 28 2017

It's a domain name I gave up over a year ago, with info and docs for the old nunitlite 1.0, which is what they use. I was already planning to expose it as nunitlite.nunitsoftware.org and add a note that it's a whole different thing from nunitlite as now provided by NUnit.

Where would I file an issue when I have a new URL up?

@ChrisMaddock commented on Wed Jun 28 2017

Not sure if you intentionally or accidentally closed this, @CharliePoole - but I think the original issue is still to do. 🙂

@CharliePoole commented on Wed Jun 28 2017

Probably means something else I intended to close isn't. 😕

@rprouse commented on Wed Jun 28 2017

I am not sure if this is the right repo for the issue, but https://github.com/xamarin/Touch.Unit

@CharliePoole commented on Wed Jun 28 2017

I filed an issue on spouliot/Touch.Unit, from which the xamarin repo is forked. FYI, the docs for the old nunitlite are at nunitsoftware.com/nunitlite.

@rprouse commented on Wed Jun 28 2017

That issue may go ignored. There hasn't been a commit in 4 years and I reached out to the Xamarin people to try to work with them in moving to NUnit 3 and I couldn't get a response despite chatting with Miguel and Nat. I don't think anyone is responsible for it anymore.

@jnm2 commented on Wed Jun 28 2017

They still ship the templates in the product though, so someone has to be responsible for those, right?

@rprouse commented on Wed Jun 28 2017

They still ship the templates in the product though, so someone has to be responsible for those, right?

Probably, we just need to find them 😄

@CharliePoole commented on Thu Jun 29 2017

I believe I found him. I gave him an issue. Him == Sebastien.

In case someone has not seen it before, it's not uncommon in the linux world for the production repo to be a fork of somebody's personal repo, rather than the other way around.

@jnm2 commented on Thu Jun 29 2017

In case someone has not seen it before, it's not uncommon in the linux world for the production repo to be a fork of somebody's personal repo, rather than the other way around.

Why yes, that did grab my attention. 😄

Lingua principale
SCSS
Stelle
6
Fork
14
Merge medio
2h 9m
PR unite (30g)
3

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nunit/nunit.github.io

Tutte le issue di nunit/nunit.github.io

Issue simili

Altre issue su Content

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.