From the dev meeting in Feb 2019 editing the html is a clear pain point that hinders site updates by the team.

Our About section includes mostly folks who are currently active developers, but also includes folks who are not currently active. Also, people who have made significant contributions in the past are not included. I propose we have two sections. Something simple like "Current Core Developers" and "Past Core Developers" would alleviate this discrepancy. Thoughts?

tobler's first release was the end of december (iirc), but we could add a retroactive announcement just for the sake of completeness. Would that be worth it?

It seems that the website is not updated with changes to this repo. Any idea how to configure it?

the main page, pysal.org, has no title.

It needs to have a title.

We used to have recorded the list of guidelines needed for subpackages to get distributed in the old website. We called this the "submodule contract," mimicking the sklearn contract.

We should probably put this into our contributing documentation. This would require

• finding it in the old website source
• moving it into the wiki

Once I get confirmation on #208, we need to make an entry for the current spopt AGILE project:

Rongbo Xu, Nick Bearman, Huanfa Chen, Qunshan Zhao, James Gaboardi, and Levi Wolf are working on a project to further develop the Location Allocation components within spopt. This project will also enable spopt to be applied across a wider variety of location-allocation tasks, these tools will contribute to a project in the Institute of Education at UCL to help large-scale student teacher training placement allocation. This is a joint project between the University of Glasgow and University College London, with funding from AGILE and the two universities.

cc @qszhao @nickbearman @ljwolf @rongboxu @huanfachen @paddyroddy
xref https://github.com/UCL/ioe-teacher-training-placements/issues/29#issuecomment-1436146016

the submodule contracts have diverged between the site & the wiki.

we need to:

1. update the site's submodule contract from the wiki
2. delete the submodule contract in the wiki
3. update any links to submodule contract coming in from elsewhere (maybe the migrating directions?)

In the move to the new site we lost the old one.

Brainstorming features to add/upgrade to pysal.org

More dynamic carousel (#205)

• arrows are invisible, auto-rotation is too slow
• should include
  • recent items from pysal.org/news
  • examples from the package pages
  • recent publications that cite PySAL
    • google scholar notifications
    • could be a standing item at PySAL dev meetings
• Aside from the logo, items should be different each time someone loads the website e.g.
  • one package example, one news item, one recent publication that cites PySAL
  • each of the above items falls into a category - could have different buckets of categories that the carousel pulls from

Inconsistent paging for some packages

One goal of the refactor is to structure these pages more consistently. Some packages lead to a pysal.org html page, while others go to a github repository or a 404. The list of packages that do not direct to an internal page are:

• momenpy goes to external site
• pointpats goes to external 404
• mgwr goes to external site
• spglm goes to github repository
• spint goes to github repository
• spreg only has a video
• spvcm goes to github repository
• legendgram goes to github repository

Where should installation be?

Currently, installation page is nested inside documentation in the menu bar. We discussed shifting it to an individual item in the menu bar to make it more discoverable.

Toolit should probably read Toolkit.

Shouldn't this function be described as the spatial error model?

Now that we have decided on a fresh logo scheme, it may be time to give some attention to the website infrastructure. There are a ton of artifacts from the old website design and the guts could use a clean up, etc. I suggest we cut a release for posterity/reproducibility's sake (like what we did in logo) and then trim the fat from pysal.github.io.

Should news entries go into _data/news.yml or content/news/*.md? We have been putting them into the latter for several years now and I just want to make sure that is the correct place?

• remove spvcm from site -- archived
• create news blurb?

xref:

• pysal/pysal#1337
• pysal/spvcm#18

We have the same three images for a while now.
It would be interesting to explore more dynamic content for the carousel.

xref: sjsrey/pysal-dinghy#1

and replaced with a notebook or link to notebooks from our workshops?

Add GitHub docs instructions as an alternative to Read the Docs.

pysal/spaghetti#301

https://github.com/pysal/pysal.github.io/runs/409755481

If the user goes to pysal.github.io, it is straightforward to access the documentation in pysal.readthedocs.org However, if the user wants to go back to the (up to date) home page in pysal.github.io from pysal.readthedocs.org, there is currently no link. This could involve setting up a way so that docs generated by sphinx pointed to pysal.github.io in certain pages (home, upcoming events, news and funding). Alternatively, these pages could be removed from sphinx and kept only under pysal.github.io

pysal#1147 mentions this pretty well 🙃

We need to link to the notebooks here, not in the subpackages.

News, upcoming events, etc.

It should be a package under the model module.

From the dev meeting we want to move to a simplified build structure for the site. The current submodule approach is overly complex and hinders updates by the team.

it would be nice to do a row of sponsor logos at the bottom of the landing page similar to pandas and scikit. Apart from numfocus, nsf, the assorted universities, do we have others we could feature?

The length of spaghetti's description causes the "Visit The Page" button to not be visible on the flip tile.

Should we make an announcement on here and the gitter channel regarding our acceptance as NumFocus Affiliated Project?

@knaaptime @weikang9009 @sjsrey

change default branch from master to main.

xref pysal/mapclassify#130, pysal/spreg#106

Following the enhancements detailed in pysal/logo#25, the logos on pysal.org should be updated.

issue was brought up before. should we still try add these?

Issue:
The Pysal website currently displays an outdated version of the Twitter logo. The logo being used is not in sync with the latest branding guidelines.

Steps to Reproduce:

Visit the Pysal website.
Navigate to the section displaying social media links.
Observe the Twitter logo and compare it with the latest Twitter branding guidelines.
Expected Result:
The Twitter logo should adhere to the most recent branding guidelines provided by Twitter.

Actual Result:
The current Twitter logo appears to be outdated and may not align with the latest branding standards.

https://twitter.com/michaelaye/status/1279191459418091520

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://pysal.org/explore/
2. Click on 'Visit the page' of the pointpats card
3. Link https://pointpats.readthedocs.io/en/master/ opens
4. See 404

Expected behavior
The documentation at https://pysal.org/pointpats/ is shown

Removed rest of template as it's not relevant to this bug

For new users:

1. git clone --recurse-submodules [email protected]:pysal/pysal.site
   this grabs the current copy of both the build scripts (which are in pysal/pysal.site), and the current user-facing website (which is in pysal/pysal.github.io). For git purposes, think of this like two independent repos. The first, pysal.site, stores all the stuff we used to build the website, plus a snapshot of the website (in build/html). The second, pysal.github.io, lives within build/html, and is tracked independently. There's a remote (called origin by default) for both, and both refer to pysal's copy.
2. Each individual who wants to work on the site needs to add their fork of the public-facing website and the private-facing build stuff. To do this:
   1. cd pysal.site/build/html changes the working directory to the public-facing website.
   2. pick a good, memorable name for your personal copy. I often call mine wolf. Then, git remote add wolf [email protected]:ljwolf/pysal.github.io. This adds my fork to the public-facing site and calls it wolf.
   3. go back to the git root: cd ../../ and make sure you're in pysal.site
   4. Then, to add your fork of the private building area, use git remote add wolf [email protected]:ljwolf/pysal.site.

Now, your repository has the two modules, the "root" module pysal.site, which is the private building area, and the "submodule", stored in build/html, which refers to pysal.github.io and which only contains static html files.

Every time you run make html, this dumps into the public submodule, build/html, which is linked to https://github.com/pysal/pysal.github.io.
Changes to build/html can be added from inside and pushed to pysal.github.io.
But, pysal.site only records the commit referring to changes in pysal.github,.io.

on the index page the link to spreg is bad:

https://github.com/pysal/pysal/tree/master/pysal/spreg