Difference between revisions of "DeveloperWiki:Website suggestions"

From ArchWiki
Jump to: navigation, search
m (Direct package links by name: typo)
(Direct package links by name: re)
Line 48: Line 48:
  
 
::--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 06:47, 11 November 2018 (UTC)
 
::--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 06:47, 11 November 2018 (UTC)
 +
 +
::Figuring out if a pkgname is unique or not is very easy [https://git.archlinux.org/archweb.git/tree/main/models.py#n88 in SQL] - just {{ic|1=SELECT pkgname, repo, arch FROM Package WHERE pkgname = ?}} and if you get just 1 result, you can show the package view, otherwise you have to show the package search view. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 08:30, 11 November 2018 (UTC)
  
 
=== Adopting archweb_manpages ===
 
=== Adopting archweb_manpages ===

Revision as of 08:30, 11 November 2018

Introduction

This article is intended as a sandbox of ideas for the Arch Linux website. Feel free to add suggestions and any thoughts you might have about how the Arch Linux website can be improved.

This article is part of the DeveloperWiki.

Ideas and Suggestions

OpenID

Implement an OpenID-like identity system for the official Arch Linux websites.

  • If we could integrate login/pass throughout AUR, Wiki, Forums, and Bugs this way ... well I'm afraid I'd get a bit moist.  :)
    georgia_tech_swagger
  • Might also consider Mozilla Persona[1], which should be easier to implement than full blown openID.

I completely agree with this idea. I dreamed this since registration. Is it possible to implement? Also, it would be great that it would be possible to login to external arch wikis. — Agent0 (talk|contribs) 11:12, 22 July 2015 (UTC)

Developer/Fellows profiles

Condense the developer profiles pages, reducing photo sizes and dropping relatively unimportant fields such as: Favourite Distros, Year of Birth, Interests, Other Contacts, etc.

  • I don't like this idea. I like any distro that has a soul and flavor to it. Sterile "strictly-business" design and community should be left to the Wall Street distros.
    georgia_tech_swagger

Navbar for internal Arch sites

Look at the feasibility of creating a unified navbar that would sit at the top of all Arch community sites (bbs.archlinux, wiki.archlinux, etc.), providing an exact copy of the main website hierarchy via drop-down menus (using CSS of course).

Embed Ads by Google into content

Consider placing the Ads by Google inside actual page content (or at least below the navigation) and removing it from the header entirely.

The ads have been removed some time ago due to Google having issues with Arch violating the terms of service or something. -- Karol 15:13, 27 November 2011 (EST)

URI Linking

Implement a pacman:// URI as an option to quickly let users quickly install packages from webpages and same the functionality for AUR packages. 9mmtylenol

I think it is easy to implement. It is very similar to apt urls. It is even possible to install several packages at once. But what is the difference in using such apt:vlc links from such apt://vlc ? — Agent0 (talk|contribs) 16:10, 28 July 2015 (UTC)

Focus in Search

Is it possible to make ArchWiki to automatically focus on search box? It is common behavior. Look for example to youtube or wikipedia. I feel uncomfortable, when I go to wiki.archlinux.org and additionally need to use mouse to focus on search field. I know about Alt + Shift + f, but it is not working, because alt+shift changes keyboard layout. — Agent0 (talk|contribs) 12:29, 17 November 2015 (UTC)

On HTML5 you just have to add the "autofocus" attribute to the input (in this case the element with id="searchInput"). -- nucularJohn

Direct package links by name

On the ArchWiki we can only link to packages using the package search, for example pacman links to https://www.archlinux.org/packages/?name=pacman, requiring the reader to always click twice to get to a package page. It would be nice if there were another argument like direct to directly take you to the respective package.

--Larivact (talk) 14:06, 4 November 2018 (UTC)

Packages can exist in multiple repositories, and formerly, in multiple architectures. This is why we never did this. Do you have a suggestion for figuring out which package it refers to? -- Eschwartz (talk) 01:35, 11 November 2018 (UTC)
Redirect to a stable package with the given name if it exists, otherwise return a 404. Exemplary URL:
https://www.archlinux.org/packages/?stable_by_name=pacman
--Larivact (talk) 06:47, 11 November 2018 (UTC)
Figuring out if a pkgname is unique or not is very easy in SQL - just SELECT pkgname, repo, arch FROM Package WHERE pkgname = ? and if you get just 1 result, you can show the package view, otherwise you have to show the package search view. -- Lahwaacz (talk) 08:30, 11 November 2018 (UTC)

Adopting archweb_manpages

Lahwaacz developed and hosts https://jlk.fjfi.cvut.cz/arch/manpages/, which is used on the ArchWiki for links to man pages, e.g. pacman(8). See Template talk:Man#Sources and the GitHub repository. I think this should be adopted as an official Arch Linux project if only for a nicer domain name (man.archlinux.org).

--Larivact (talk) 14:27, 4 November 2018 (UTC)