adafruit / circuitpython-org Goto Github PK

Instead of "Zoom zoom", the release titles should also include their tag. So, it'd be "4.1.0-beta.0 - Zoom zoom".

Here is what I would like to see for the LIBRARIES page.

Main page would be three sections:

• CircuitPython Libraries
  • (quick intro to libraries)
• Download Instructions (heading):
  • Embedded links to the latest bundles.
  • Instructions on copying individual libraries to CIRCUITPY drive.
• Contributing (heading):
  • Quick bit about contributing to the libraries
  • New Libraries list (updated by script)
  • Updated libraries list (updated by script)
  • Link to Contributing page.

Contributing page:
Contributing page linked from the LIBRARIES main page will be information aggregated from all the libraries, updated by a script. It will be text blocks interspersed with lists of links to PRs/Issues/Repos (supplied by the script). The formatting will involve section headings, text and links. I would provide text content.

The script:
The script would supply the assets for the lists on the main page and for building the Contributing page. The script will be written by @sommersoft. It will be designed to update the New/Updated libraries lists, and the Contributing page, on a to-be-determined time interval, likely starting with weekly. We would add a cron job to Travis for circuitpython-org to run the script.

For both the lists on the main page, and the content on the Contributing page, the script can run and update a json file which can be used to populate the pages.

Terrible mock-up included.

For @ptorrone

@jwcooper as ya do updates to the head-area please add

<link rel="alternate" type="application/rss+xml" title="CircuitPython news!" href="https://blog.adafruit.com/category/circuitpython/feed/" />

to head on circuitpython.org

this way it'll show up in rss readers, etc.

Try typing "circuit play" (or even "circuit " (trailing space)) into the search box. No boards will be found.

Be able in search or on download screen to select all boards, microcontrollers, or Single Board Computers. Some people may not know what board they want but do know they want a SBC vs. a uC.

That way folks can link to searches for particular downloads. (A list of all boards by one manufacturer for example.)

It would be sweet to have the library bundle download link next to the related .uf2 download button.

(Tagging @jwcooper)

On Chrome (73.0.3683.75), the div.download's are of uneven size, even though there's nothing in the source to cause this. F12 says this is due to the "user agent stylesheet", supplied directly by Chrome, which is apparently adding a

div {
    display: block;
}

See how the first div on this screenshot is shorter:

div's are of uniform size on Firefox

The Javascript for changing the anchor link on the download button based on the language dropdown isn't working. The Javascript is set up to change <a class="download-button">, but that class is used for the link to the release itself, in the "Past Releases" section. The dropdowns for the stable and unstable releases aren't changing the URL for their respective buttons, which are <a class="download-button-{{stable}}"> in the template code. And I think maybe it should be {{version.stable}}` as well?

we do not need news.html and we can just link to https://blog.adafruit.com/category/circuitpython/ from NEWS at the top.

It would be super handy if a person could tell what was supported for a board by looking at its download page.

Extra credit for filtering by feature on the downloads index

Installation instruction links on Blinka boards (ex: https://circuitpython.org/blinka/beaglebone_black/) are broken.

Help menu item is chopped off at bottom on mobile devices See image here:

It'll be convenient to have hyperlinked learn guides to Adafruit portal for contributed boards from Adafruit.

I just noticed it looks like aramcon_badge_2019 is showing up as an unknown board.

It looks like the following boards are missing:
ndgarage_ndbit6
meowbit_v121

Issue #396 is already open for the ndbit6, but since there hasn't been any movement on it, I may just try and get something up in the meantime.

The circuitpython.org lists all boards that have descriptions, but not all of those boards are getting built automatically. That results in broken links to firmware downloads. We probably shouldn't link to firmware downloads that are not there.

The photo for the Arduino Nano 33 BLE is actually a photo of an Arduino Nano 33 BLE Sense, its sensor filled cousin. Would you mind replacing the photo?

EDIT: Maybe we could reuse that photo if we're adding the Arduino Nano 33 BLE Sense? Also, if the sensor on your new LPS2x breakout is the LPS22HB or something similar, then the board is fully compatiBLE(hahaha) with CircuitPython!

add AWESOME on top menu (before HELP) and link to:
https://github.com/adafruit/awesome-circuitpython

OR! if it's possible to make a page on the site like ... https://circuitpython.org/awesome

and have it render what is on: https://github.com/adafruit/awesome-circuitpython

would be cool too.

whatever ya'll think is best @jwcooper @tannewt

On the top nav after Awesome, please add Newsletter

and link to:
https://www.adafruitdaily.com/category/circuitpython/

I'll look into it. It may be as simple as a board id changing.

Accept-Language: : en-US,en;q=0.9,fr;q=0.8
Result: French
Expected: English because the weight is 0.9 for en, en-US

Accept-Language: en-CA,en-US;q=0.7,en;q=0.3
Result: English
Expected: English

hi @jwcooper let me know if we need to chatter on vid, etc. here it goes.

we want to have /blinka be a listing of all the linux boards that support blinka. it would function the same way we do downloads.

another section on the repo /boards is where we'd put the .md files to display, we'd use the front matter tag features: etc.. all the same, BUT we would not at this time need to have anything automatically coming in. we will manually add the board names, text, etc, etc.

@tannewt if i missed anything or how to explain this better, please comment in!

please add BLINKA after LIBRARIES at top nav and link to: https://circuitpython.org/blinka

add LIBRARIES to the top, after DOWNLOADS on https://circuitpython.org/ and link to: https://github.com/adafruit/Adafruit_CircuitPython_Bundle/blob/master/circuitpython_library_list.md

download the road maybe we can just render that page on a page on https://circuitpython.org/ like .libraries.hml

Going to https://www.circuitpython.org/ generates a cert warning on Firefox.

@jwcooper The bundle download buttons are missing from the Libraries page, only on desktop browsers (mobile works). I verified it on Chrome on Linux, and Firefox on Mac and Linux.

If you could take a look, that would be great. Thanks!

Now that we have some bootloader updates, it would be nice to be able to point people to circuitpython.org to download them as well.

In order to keep track of the changes, I'm creating this issue so after PR in Blinka is merged, all boards added in Blinka should be also added here.

P.D: @makermelissa we can do same procedure as in Blinka for this issue (assign it to me) I'll take care after boards are added.

Please include the GitHub issue label data in the libraries.json file used to generate /libraries/contributing so we can include an option in the UI to filter by label.

This should do it: https://github.com/marketplace/actions/image-actions

Tracking ID
UA-7723544-8

The mirror of awesome-circuitpython is not current. The file was changed several days ago but the circuitpython.org copy did not change as it points to an older copy.

Change so that the current copy is always pulled
https://github.com/adafruit/awesome-circuitpython/blob/master/README.md

would be good to use the github api for up-to-date stats on downloads and have a human-readable page here:

https://www.circuitpython.org/stats

OR

if it's easier, use the JSON file that runs download stats.
https://github.com/adafruit/circuitpython-org/blob/master/_data/files.json

extra extra credit, totally OK with putting google analytics there too so folks can see site traffic, etc.

On the Install dependencies check, it is saying:

Run bundle install
  bundle install
  shell: /bin/bash -e {0}
/opt/hostedtoolcache/Ruby/2.7.0/x64/lib/ruby/2.7.0/rubygems.rb:275:in `find_spec_for_exe': Could not find 'bundler' (1.17.3) required by your /home/runner/work/circuitpython-org/circuitpython-org/Gemfile.lock. (Gem::GemNotFoundException)
To update to the latest version installed on your system, run `bundle update --bundler`.
To install the missing version, run `gem install bundler:1.17.3`
	from /opt/hostedtoolcache/Ruby/2.7.0/x64/lib/ruby/2.7.0/rubygems.rb:294:in `activate_bin_path'
	from /opt/hostedtoolcache/Ruby/2.7.0/x64/bin/bundle:23:in `<main>'
##[error]Process completed with exit code 1.

PR coming soon

In the thanks section the word "focused" is currently misspelled "focussed".

Thank you to Adafruit for continuing to support CircuitPython's beginner-focussed development.

Currently we have the below. It would be clearer if the stable release were the first one listed, so it's the most obvious to download. Mentioned by @devoh in Discord.

Now that we're getting so many boards, it would be nice to display a count of the boards that are currently displayed on the page. Like for instance, if you just went to the page and there were 94 boards, it would say that. If you narrowed down the search, then it would display that number.

In the CircuitPython documentation, we have a matrix that shows the available built-in modules for each board. https://circuitpython.readthedocs.io/en/latest/shared-bindings/support_matrix.html

I feel the current location and layout are cumbersome, involve lots of scrolling, and not easy to find.

I would like to extend this information to circuitpython.org, so it's more visible to users. The matrix information in the documentation is built with a Python script, which is easily extended to use elsewhere.

I have some various implementation ideas:

• Minimum:
  • Available modules are simply listed on each board's page, and only apply to the current stable release.
  • Information resides in _data/files.json, and is delivered with the current updates to that file.
• Intermediate:
  • Includes Minimum, but includes available modules for both stable and current unstable releases.
• The Full Monty 🐍:
  • Includes Minimum and Intermediate, but in a way that also allows for filtering on the downloads page based on available module(s). However, this could be tricky and/or confusing with having both stable and unstable version information.
  • Might need the information to live outside of _data/files.json, though I expect not with the current Jinja templating.

As a frontend-design-challenged individual, I defer all of that to the experts. 😄

image missing from https://circuitpython.org/awesome looks like ya'll are on it, here is the issue.

Blip doesn't use a bootloader since it has bootloader on board, however there is only .UF2 link on board page. I do see that some boards do have a .bin download link (maybe even .hex), for example: https://circuitpython.org/board/pca10059/.

What needs to change to blip's page to make that happen?

@ndGarage could you submit a PR to add your new board? Thanks.

@edspark I'll get the pictures and .md page added sometime tomorrow! Thanks @ladyada

add DISCORD on top after NEWS and before HELP on https://circuitpython.org/

link to:

https://adafru.it/discord

would be a good feature to add a list of names in a file to not-display, something like...

disallow...
feather_radiofruit_zigbee
datalore_ip_m4
cp32-m4
gb_m4
pca10040

these can stay as we'll have some images soon...
sam32
meowmeow
catwan_usbstick

i'll do PRs for those soon.

Suggestion for CircuitPython.Org/downloads - sort by date board added - get the newest first

phillip torrone 11:59 AM
yah, add that as a feature request as an issue in github
would be, click the filter button
then..
Sort By
Downloads
Board Name (A To Z)
Board Name (Z To A)
adding Date (Most recent)

We should have compiled versions of mpy-cross available to download.

If I understand correctly, previous availability was done manually by adding it to a release's assets. Since they aren't built dynamically, I would guess that they could live here in assets/.