[Website] Integral update proposal

> Navigation bar

> ==============

>

> Bar mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-menu-2017-03-06.png

>

> The current navigation bar is growing, so I think it may be good to define a style so that people can build more complex menus if necessary (but I hope it won't get too complex).

>

> I propose the graphic change you see in the mockup—thin black line at the bottom, navigation items are white while idle, and yellow with a black indicator at the bottom when active— as well as the actual items and their ordering.

> Home page

> =========

>

> Home mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-home-view-2017-03-06.png

>

> I propose the changes in the mockup above because of the following reasons:

>

> 1. Some people still confuse Guix with GuixSD.

> 2. Some people still ask if Guix can be used on top of other distributions.

> 3. Some people think pitching GuixSD and Guix to specific crowds is good (of course it is). [1]

>

> To address the first two points, I changed the order of the content so that information refers to GuixSD first, Guix as a part of it, and then added a section that mentions specifically the use of Guix in other distros.

>

> For point three, I added a section that links to blog posts that explain GuixSD and Guix in the context of a particular field (this part requires the current News pages to become a Blog instead. See below).

>

> Finally, Ricardo Wurmus commented that there were too many styles of buttons, and I agree with him, so I made them homogeneous.

> News pages

> ==========

>

> News list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-list-2017-03-06.png

> News details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-blog-post-2017-03-06.png

>

> I suggest to convert News into a blog instead. This could make it easier to add information targeted at different audiences without making the website more complex. Additionally, we could move to the blog content like talks, papers, and posts currently listed in the Help page.

> I remember that Ludovic commented in #guix that he would like a better way to display talks in the website... [2] With the design in the mockup above, you just click on the "Talks" tag, and you have a nice preview and summary of all talks.

> Also, Haunt, the current static site generator used to build the website, can create an atom feed for every tag in the blog, so people can subscribe to whatever topic is more interesting to them. Personally, I'd like to subscribe to a "Security" feed to keep informed about important security updates (see bug #25852). [3]

> Packages pages

> ==============

>

> Package list mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-list-2017-03-06.png

> Package details mockup: https://multimedialib.files.wordpress.com/2017/03/guixsd-package-detail-2017-03-06.png

>

> I actually proposed this update in bug #25227,[4] but decided to review the whole website design, so I put it here for reference.

> Help page

> =========

>

> * Move talks, papers, and posts to the Blog.

> * Allow little boxes to be distributed along the whole width of the screen.

> Contribute page

> ===============

>

> * Allow little boxes to be distributed along the whole width of the screen.

>

>

> Infrastructure

> ==============

>

> Personally, I'd like to be able to access the website at "guixsd.org", and use a git repository for deployment of the static website.

>

> However, we are currently using the resources provided by Savannah for hosting, which means we have to use a CVS repository to deploy the website. As mentioned in bug #25227, using CVS could block the implementation of the packages pages as shown in the mockups above (and maybe filtering blog posts by tag) because CVS could choke on the thousands of pages that would be generated (if we keep using a static website).

>

> To find a solution to this issue, Ludovic sent an email to Savannah admins asking for the possibility of using a dynamic website instead. I don't remember if there was an answer.

> I remember that Ludovic commented in #guix that he would like a better way to display talks in the website... [2] With the design in the mockup above, you just click on the "Talks" tag, and you have a nice preview and summary of all talks.

> Infrastructure

> ==============

>

> Personally, I'd like to be able to access the website at "guixsd.org", and use a git repository for deployment of the static website.

>

> However, we are currently using the resources provided by Savannah for hosting, which means we have to use a CVS repository to deploy the website. As mentioned in bug #25227, using CVS could block the implementation of the packages pages as shown in the mockups above (and maybe filtering blog posts by tag) because CVS could choke on the thousands of pages that would be generated (if we keep using a static website).

>

> To find a solution to this issue, Ludovic sent an email to Savannah admins asking for the possibility of using a dynamic website instead. I don't remember if there was an answer.

> I'd like to say I will take care of this project, but I can't commit

> right now. However, life permitting, I intend to implement the

> proposed changes that can be implemented in the current static site,

> starting next week.

> I have an incomplete implementation

> (https://bitbucket.org/sirgazil/guixsd-website) of a static website that

> includes the features illustrated in the mockups (the features that fit

> in a static website).

> Compared to the current website, this code has a different organization

> (see the "Framework" section below). I'm sending this message because I

> think this is as far as I can go with the implementation (found some

> problems I haven't figured out how to solve, and I'm not skilled enough

> to manipulate packages).

>

> This implementation is missing the following parts:

>

> 1. New screenshots

> 2. Packages pages

> 1. Package detail page

> 2. Packages issues page

> 3. Packages reproducibility page

> 4. Packages JSON file

>

> To complete part (1) someone could provide the screenshots (ideally

> 1920×1080 px) in JPG and add them to the "static/media/img" directory,

> and update the list of screenshots in "apps/base/data.scm".

>

> To complete (2), there are some package related procedures missing

> (https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open).

> I tried to use the code that is already in the current website, but

> couldn't figure things out.

>

> To complete part (2.1), there is an issue to solve: package pages go in

> paths like "/packages/blender-3.0/", but running "haunt build" with

> pages on paths that include "." will render the pages with all the HTML

> content inside a pre element. David, the maintainer of Haunt, does not

> know yet why this would happen. If this issue is solved, there are

> already helper builders in "apps/packages/builders.scm" to generate all

> the pages.

>

> So, for now, the packages pages are working as in the current website,

> but not using tables (to make it easier to adapt the page to several

> screen widths), and packages are distributed in numbered pages to avoid

> big HTML pages that take too long to load.

>

> Also, the JavaScript code that gets package build status is not

> integrated (couldn't figure this one out either).

>

> To complete (2.2), (2.3), and (2.4) someone could add helper builders to

> the packages app, and recycle the related SXML pages already used in the

> current website.

> Hi sirgazil,

>

> It’s always a pleasure to hear from you. :-)

> sirgazil <sirgazil@zoho.com> skribis:

>

>> I have an incomplete implementation

>> (https://bitbucket.org/sirgazil/guixsd-website) of a static website that

>> includes the features illustrated in the mockups (the features that fit

>> in a static website).

> I’ve just built the web site and I like it! The flat buttons look nice,

> the front page looks cleaner, “GuixSD and GNU Guix in your field” sounds

> like a good idea, etc. I really like the blog part with tags and

> everything.

>

> I found it a little bit confusing that talks and papers now appear as if

> they were blog posts, but after all it’s probably better to have it this

> way, especially since tags allow people to find them more easily I guess.

>

> The packages pages look better than what we have (minus the loss of the

> JS code to display the build status ;-)).

>

>> Compared to the current website, this code has a different organization

>> (see the "Framework" section below). I'm sending this message because I

>> think this is as far as I can go with the implementation (found some

>> problems I haven't figured out how to solve, and I'm not skilled enough

>> to manipulate packages).

>>

>> This implementation is missing the following parts:

>>

>> 1. New screenshots

>> 2. Packages pages

>> 1. Package detail page

>> 2. Packages issues page

>> 3. Packages reproducibility page

>> 4. Packages JSON file

>>

>> To complete part (1) someone could provide the screenshots (ideally

>> 1920×1080 px) in JPG and add them to the "static/media/img" directory,

>> and update the list of screenshots in "apps/base/data.scm".

>>

>> To complete (2), there are some package related procedures missing

>> (https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open).

>> I tried to use the code that is already in the current website, but

>> couldn't figure things out.

>>

>> To complete part (2.1), there is an issue to solve: package pages go in

>> paths like "/packages/blender-3.0/", but running "haunt build" with

>> pages on paths that include "." will render the pages with all the HTML

>> content inside a pre element. David, the maintainer of Haunt, does not

>> know yet why this would happen. If this issue is solved, there are

>> already helper builders in "apps/packages/builders.scm" to generate all

>> the pages.

>>

>> So, for now, the packages pages are working as in the current website,

>> but not using tables (to make it easier to adapt the page to several

>> screen widths), and packages are distributed in numbered pages to avoid

>> big HTML pages that take too long to load.

>>

>> Also, the JavaScript code that gets package build status is not

>> integrated (couldn't figure this one out either).

>>

>> To complete (2.2), (2.3), and (2.4) someone could add helper builders to

>> the packages app, and recycle the related SXML pages already used in the

>> current website.

> Sounds good. I haven’t looked at this nor have I looked at the new

> framework, but I’ll hopefully comment soonish. Hopefully David can help

> for the Haunt part, then people can provide screenshots, and we’ll

> figure out the issues with packages pages somehow. :-)

> I think there are a few little changes that were made in the current

> site that were lost in the process. For example, on the front page, we

> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen

> that links to the package definitions at git.sv.gnu.org from the package

> pages no longer include the commit. Anyway, these are really tiny

> issues but we should pay attention to them when we migrate.

> Anyway, a big thank you for all this work! Really impressive work

> once again.

>

> Ludo’.

> On 13/06/17 17:08, Ludovic Courtès wrote:

>> I found it a little bit confusing that talks and papers now appear as if

>> they were blog posts, but after all it’s probably better to have it this

>> way, especially since tags allow people to find them more easily I guess.

>>

>> The packages pages look better than what we have (minus the loss of the

>> JS code to display the build status ;-)).

>

> About the JS, I couldn't figured out exactly how it works, so that I

> could adapt it to the new page structure. Additionally, there is the

> problem that the JS looks for packages in the DOM by id, and package ids

> are not unique, which confuses me. Also, using duplicated id attributes

> is non-valid HTML.

>> I think there are a few little changes that were made in the current

>> site that were lost in the process. For example, on the front page, we

>> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen

>> that links to the package definitions at git.sv.gnu.org from the package

>> pages no longer include the commit. Anyway, these are really tiny

>> issues but we should pay attention to them when we migrate.

>

> I updated the download button.

>

> As for the commit in the links, I tried to add it, but couldn't. I

> implemented this website using the Guix API as a user (installing guix

> with guix), but it seems that the code to generate the commit part in

> the links requires that the guix in the GUILE_LOAD_PATH be a git

> repository, right? Since it uses "git describe" on "guix/config.scm".

> Hello,

>

> sirgazil <sirgazil@zoho.com> skribis:

>

>> On 13/06/17 17:08, Ludovic Courtès wrote:

> [...]

>

>>> I found it a little bit confusing that talks and papers now appear as if

>>> they were blog posts, but after all it’s probably better to have it this

>>> way, especially since tags allow people to find them more easily I guess.

>>>

>>> The packages pages look better than what we have (minus the loss of the

>>> JS code to display the build status ;-)).

>> About the JS, I couldn't figured out exactly how it works, so that I

>> could adapt it to the new page structure. Additionally, there is the

>> problem that the JS looks for packages in the DOM by id, and package ids

>> are not unique, which confuses me. Also, using duplicated id attributes

>> is non-valid HTML.

> The current code that generates the package pages intends to compute

> unique anchor names for each package (see ‘packages->anchors’), and I

> think it’s those IDs that the JS code uses, isn’t it?

>

>>> I think there are a few little changes that were made in the current

>>> site that were lost in the process. For example, on the front page, we

>>> now have “DOWNLOAD v0.13.0” instead of “TEST v0.13.0”. I’ve also seen

>>> that links to the package definitions at git.sv.gnu.org from the package

>>> pages no longer include the commit. Anyway, these are really tiny

>>> issues but we should pay attention to them when we migrate.

>> I updated the download button.

>>

>> As for the commit in the links, I tried to add it, but couldn't. I

>> implemented this website using the Guix API as a user (installing guix

>> with guix), but it seems that the code to generate the commit part in

>> the links requires that the guix in the GUILE_LOAD_PATH be a git

>> repository, right? Since it uses "git describe" on "guix/config.scm".

> Indeed, good point. I guess we could have a fallback case for when ‘git

> describe’ fails.

> On a more practical level, what would you like the workflow to be like

> from there on? I would prefer hosting the source on gnu.org rather than

> {bitbucket,gitlab,github}.com and I would also prefer Git over

> Mercurial, but I don’t want to be a hindrance so I’m open to

> discussions. :-)

> On 15/06/17 02:59, Ludovic Courtès wrote:

>> On a more practical level, what would you like the workflow to be like

>> from there on? I would prefer hosting the source on gnu.org rather than

>> {bitbucket,gitlab,github}.com and I would also prefer Git over

>> Mercurial, but I don’t want to be a hindrance so I’m open to

>> discussions. :-)

>

> No worries. The idea was to move the useful parts to guix-artwork on

> gnu.org.

>

> To be honest, when I started this version of the website I was just

> motivated on implementing the designs and exploring a way to organize

> modules in a haunt website so that data, builders and templates were

> separated. But I was not very interested in dealing with git workflows,

> and strict commit messages. Sorry about that :)

> So, what do we do? Create a branch on guix-artwork and drop these files

> there to complete what is missing? I don't know...

> Howdy!

>

> sirgazil <sirgazil@zoho.com> skribis:

>

>> On 15/06/17 02:59, Ludovic Courtès wrote:

> [...]

>

>>> On a more practical level, what would you like the workflow to be like

>>> from there on? I would prefer hosting the source on gnu.org rather than

>>> {bitbucket,gitlab,github}.com and I would also prefer Git over

>>> Mercurial, but I don’t want to be a hindrance so I’m open to

>>> discussions. :-)

>> No worries. The idea was to move the useful parts to guix-artwork on

>> gnu.org.

>>

>> To be honest, when I started this version of the website I was just

>> motivated on implementing the designs and exploring a way to organize

>> modules in a haunt website so that data, builders and templates were

>> separated. But I was not very interested in dealing with git workflows,

>> and strict commit messages. Sorry about that :)

> No problem, this is perfectly understandable (also I’m fine with relaxed

> conventions on guix-artwork.git).

>

>> So, what do we do? Create a branch on guix-artwork and drop these files

>> there to complete what is missing? I don't know...

> Yes we could do that. Should we investigate the missing bits first? I

> haven’t taken the time to do it yet, sorry about that.

>

> guix-artwork.git.

>

>

>

> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com>:

>

>>

>

> I'm fine with investigating the missing parts before or after moving to

>> guix-artwork.git.

>>

>

> For what it's worth, I vouch for moving all to gnu.org and possibly

> expressing the issues in the appropriate debbugs instance

>

> Then, I might be able to collaborate in sorting out some issues

>

> I never used Mercurial. I should learn from scratch.

>

> Also, I can't access the issues on bitbucket because the login doesn't

> work in Icecat (plus some nonsense about upgrading my account and coming

> mobile apps that require me some voodoo right now)

>

> So I can't see the issues at

> https://bitbucket.org/sirgazil/guixsd-website/

> issues?status=new&status=open

>

>

>

>

> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com

> <mailto:sirgazil@zoho.com>>:

>

>

>

> I'm fine with investigating the missing parts before or after

> moving to

> guix-artwork.git.

>

>

> For what it's worth, I vouch for moving all to gnu.org

> <http://gnu.org> and possibly expressing the issues in the appropriate

> debbugs instance

>

> Then, I might be able to collaborate in sorting out some issues

>

> I never used Mercurial. I should learn from scratch.

>

> Also, I can't access the issues on bitbucket because the login doesn't

> work in Icecat (plus some nonsense about upgrading my account and

> coming mobile apps that require me some voodoo right now)

>

> So I can't see the issues at

> https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open

>

> On 16/06/17 23:57, Catonano wrote:

>

> So I can't see the issues at

> https://bitbucket.org/sirgazil/guixsd-website/

> issues?status=new&status=open

>

>

>

>

>

> public. Also, you can use the tracker "anonymously" (i. e. you don't need a

> Bitbucket account).

>

>

>

> 2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com

> <mailto:catonano@gmail.com>>:

>

>

>

> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com

> <mailto:sirgazil@zoho.com>>:

>

>

>

> I'm fine with investigating the missing parts before or after

> moving to

> guix-artwork.git.

>

>

> For what it's worth, I vouch for moving all to gnu.org

> <http://gnu.org> and possibly expressing the issues in the

> appropriate debbugs instance

>

> Then, I might be able to collaborate in sorting out some issues

>

> I never used Mercurial. I should learn from scratch.

>

> Also, I can't access the issues on bitbucket because the login

> doesn't work in Icecat (plus some nonsense about upgrading my

> account and coming mobile apps that require me some voodoo right now)

>

> So I can't see the issues at

> https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open

> <https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>

>

>

> I managed to install mercurial, but I can't build it

>

> [env]$ haunt build

> Backtrace:

> In ice-9/boot-9.scm:

> 2986:16 19 (try-module-autoload _ _)

> 2316:4 18 (save-module-excursion #<procedure 11b0d50 at ice-9/boo…>)

> 3006:22 17 (_)

> In unknown file:

> 16 (primitive-load-path "apps/blog/utils" #<procedure 11d0…>)

> In ice-9/eval.scm:

> 721:20 15 (primitive-eval (define-module (apps blog utils) # (…) …))

> In ice-9/psyntax.scm:

> 1234:36 14 (expand-top-sequence ((define-module (apps blog #) # …)) …)

> 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)

> 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)

> In ice-9/eval.scm:

> 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)

> In ice-9/boot-9.scm:

> 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _ # _ …)

> 2879:24 9 (_)

> 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt …)) …))

> 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #)) (#) …))

> 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi srfi-1)) …))

> 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #)) (#) …))

> 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((# #)) #))

> 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #))

> 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#)))

> 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)

> In unknown file:

> 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)

>

> On 17/06/17 02:16, Catonano wrote:

>

>

>

> 2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com>:

>

>>

>>

>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com>:

>>

>>>

>>

>> I'm fine with investigating the missing parts before or after moving to

>>> guix-artwork.git.

>>>

>>

>> For what it's worth, I vouch for moving all to gnu.org and possibly

>> expressing the issues in the appropriate debbugs instance

>>

>> Then, I might be able to collaborate in sorting out some issues

>>

>> I never used Mercurial. I should learn from scratch.

>>

>> Also, I can't access the issues on bitbucket because the login doesn't

>> work in Icecat (plus some nonsense about upgrading my account and coming

>> mobile apps that require me some voodoo right now)

>>

>> So I can't see the issues at

>> https://bitbucket.org/sirgazil/guixsd-website/issues?status=

>> new&status=open

>>

>>

> I managed to install mercurial, but I can't build it

>

> [env]$ haunt build

> Backtrace:

> In ice-9/boot-9.scm:

> 2986:16 19 (try-module-autoload _ _)

> 2316:4 18 (save-module-excursion #<procedure 11b0d50 at ice-9/boo…>)

> 3006:22 17 (_)

> In unknown file:

> 16 (primitive-load-path "apps/blog/utils" #<procedure 11d0…>)

> In ice-9/eval.scm:

> 721:20 15 (primitive-eval (define-module (apps blog utils) # (…) …))

> In ice-9/psyntax.scm:

> 1234:36 14 (expand-top-sequence ((define-module (apps blog #) # …)) …)

> 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)

> 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)

> In ice-9/eval.scm:

> 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)

> In ice-9/boot-9.scm:

> 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _ # _ …)

> 2879:24 9 (_)

> 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt …)) …))

> 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #)) (#) …))

> 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi srfi-1)) …))

> 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #)) (#) …))

> 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((# #)) #))

> 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #))

> 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#)))

> 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ …)

> In unknown file:

> 0 (scm-error misc-error #f "~A ~S" ("no code for modu…" …) …)

>

>

> Catonano, could you try without an environment?

>

> $ cd /path/to/guixsd-website

> $ guix package -i git glibc-locales guile@2.2 guile-syntax-highlight guix

> haunt

>

> I actually work without environments, and it works, but will try to

> reproduce that error.

>

> 2017-06-17 17:46 GMT+02:00 sirgazil <sirgazil@zoho.com

> <mailto:sirgazil@zoho.com>>:

>

> On 17/06/17 02:16, Catonano wrote:

>>

>>

>> 2017-06-17 6:57 GMT+02:00 Catonano <catonano@gmail.com

>> <mailto:catonano@gmail.com>>:

>>

>>

>>

>> 2017-06-16 16:46 GMT+02:00 sirgazil <sirgazil@zoho.com

>> <mailto:sirgazil@zoho.com>>:

>>

>>

>>

>> I'm fine with investigating the missing parts before or

>> after moving to

>> guix-artwork.git.

>>

>>

>> For what it's worth, I vouch for moving all to gnu.org

>> <http://gnu.org> and possibly expressing the issues in the

>> appropriate debbugs instance

>>

>> Then, I might be able to collaborate in sorting out some issues

>>

>> I never used Mercurial. I should learn from scratch.

>>

>> Also, I can't access the issues on bitbucket because the

>> login doesn't work in Icecat (plus some nonsense about

>> upgrading my account and coming mobile apps that require me

>> some voodoo right now)

>>

>> So I can't see the issues at

>> https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open

>> <https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>

>>

>>

>> I managed to install mercurial, but I can't build it

>>

>> [env]$ haunt build

>> Backtrace:

>> In ice-9/boot-9.scm:

>> 2986:16 19 (try-module-autoload _ _)

>> 2316:4 18 (save-module-excursion #<procedure 11b0d50 at

>> ice-9/boo…>)

>> 3006:22 17 (_)

>> In unknown file:

>> 16 (primitive-load-path "apps/blog/utils" #<procedure

>> 11d0…>)

>> In ice-9/eval.scm:

>> 721:20 15 (primitive-eval (define-module (apps blog utils) #

>> (…) …))

>> In ice-9/psyntax.scm:

>> 1234:36 14 (expand-top-sequence ((define-module (apps blog #) #

>> …)) …)

>> 1181:24 13 (parse _ (("placeholder" placeholder)) ((top) #(# #

>> …)) …)

>> 284:10 12 (parse _ (("placeholder" placeholder)) (()) _ c&e

>> (eval) …)

>> In ice-9/eval.scm:

>> 293:34 11 (_ #<module (#{ g66}#) 11c2d20>)

>> In ice-9/boot-9.scm:

>> 2866:4 10 (define-module* _ #:filename _ #:pure _ #:version _

>> # _ …)

>> 2879:24 9 (_)

>> 230:29 8 (map1 (((apps aux lists)) ((apps aux web)) ((haunt

>> …)) …))

>> 230:29 7 (map1 (((apps aux web)) ((haunt post)) ((ice-9 #))

>> (#) …))

>> 230:29 6 (map1 (((haunt post)) ((ice-9 match)) ((srfi

>> srfi-1)) …))

>> 230:29 5 (map1 (((ice-9 match)) ((srfi srfi-1)) ((srfi #))

>> (#) …))

>> 230:29 4 (map1 (((srfi srfi-1)) ((srfi srfi-19)) ((#)) ((#

>> #)) #))

>> 230:29 3 (map1 (((srfi srfi-19)) ((syntax-highlight)) ((# #)) #))

>> 230:17 2 (map1 (((syntax-highlight)) ((syntax-highlight #)) (#)))

>> 2795:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _

>> # _ …)

>> In unknown file:

>> 0 (scm-error misc-error #f "~A ~S" ("no code for

>> modu…" …) …)

>>

>

> Catonano, could you try without an environment?

>

> $ cd /path/to/guixsd-website

> $ guix package -i git glibc-locales guile@2.2 <mailto:guile@2.2>

> guile-syntax-highlight guix haunt

>

> I actually work without environments, and it works, but will try

> to reproduce that error.

>

>

> You're right. Like this, it's working

>

> It's building the pages right now !

>

> Catonano, to avoid building all the packages (3-4 minutes in this

> machine), you should run the build like this:

>

> $ GUIX_WEB_SITE_LOCAL=yes haunt build

>

> Also, this way, the website URLs are modified to work locally, and only

> 300 packages will be built for testing.

>

> If you run:

>

> $ haunt build

>

> It will build the website for production, which uses the gnu.org URL path

> for projects, so running "haunt serve" after that won't display the website

> correctly. In this case, what I do is use python server, and not haunt

> server. Like so:

>

> $ haunt build

> $ cd /tmp/gnu/

> $ python3 -m http.server

>

> Then you can visit http://localhost:8000/, and the site should work as if

> it were in production.

>

> 2017-06-17 18:41 GMT+02:00 sirgazil <sirgazil@zoho.com

> <mailto:sirgazil@zoho.com>>:

>

>

> Catonano, to avoid building all the packages (3-4 minutes in this

> machine), you should run the build like this:

>

> $ GUIX_WEB_SITE_LOCAL=yes haunt build

>

> Also, this way, the website URLs are modified to work locally, and

> only 300 packages will be built for testing.

>

> If you run:

>

> $ haunt build

>

> It will build the website for production, which uses the gnu.org

> <http://gnu.org> URL path for projects, so running "haunt serve"

> after that won't display the website correctly. In this case, what

> I do is use python server, and not haunt server. Like so:

>

> $ haunt build

> $ cd /tmp/gnu/

> $ python3 -m http.server

>

> Then you can visit http://localhost:8000/, and the site should

> work as if it were in production.

>

>

> All this stuff is good to know, thanks

>

> I attempted to chhange te build pat to ./build and when seeing it in

> Icecat I got the html as plain text, not rendered.

>

> I reset it to what it was and it works like a charm

>

> Why ?

>

> Anyway, now I see the site, I like it but I can't be accurate

>

> I will have to re-red the whole thread to consiider all the issues

>

> Thanks !

> Ciao

> This implementation is missing the following parts:

>

> 1. New screenshots

> 2. Packages pages

> 1. Package detail page

> 2. Packages issues page

> 3. Packages reproducibility page

> 4. Packages JSON file

>

> To complete part (1) someone could provide the screenshots (ideally

> 1920×1080 px) in JPG and add them to the "static/media/img" directory,

> and update the list of screenshots in "apps/base/data.scm".

> To complete (2), there are some package related procedures missing

> (https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open).

> I tried to use the code that is already in the current website, but

> couldn't figure things out.

>

> To complete part (2.1), there is an issue to solve: package pages go in

> paths like "/packages/blender-3.0/", but running "haunt build" with

> pages on paths that include "." will render the pages with all the HTML

> content inside a pre element. David, the maintainer of Haunt, does not

> know yet why this would happen. If this issue is solved, there are

> already helper builders in "apps/packages/builders.scm" to generate all

> the pages.

> So, for now, the packages pages are working as in the current website,

> but not using tables (to make it easier to adapt the page to several

> screen widths), and packages are distributed in numbered pages to avoid

> big HTML pages that take too long to load.

>

> Also, the JavaScript code that gets package build status is not

> integrated (couldn't figure this one out either).

> To complete (2.2), (2.3), and (2.4) someone could add helper builders to

> the packages app, and recycle the related SXML pages already used in the

> current website.

> Hi sirgazil,

>

> Slowly trying to catch up…

>

> sirgazil <sirgazil@zoho.com> skribis:

>

>> This implementation is missing the following parts:

>>

>> 1. New screenshots

>> 2. Packages pages

>> 1. Package detail page

>> 2. Packages issues page

>> 3. Packages reproducibility page

>> 4. Packages JSON file

>>

>> To complete part (1) someone could provide the screenshots (ideally

>> 1920×1080 px) in JPG and add them to the "static/media/img" directory,

>> and update the list of screenshots in "apps/base/data.scm".

> Since “someone” has not shown up yet ;-), maybe we can delay (1), no?

>

>> To complete (2), there are some package related procedures missing

>> (https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open).

>> I tried to use the code that is already in the current website, but

>> couldn't figure things out.

>>

>> To complete part (2.1), there is an issue to solve: package pages go in

>> paths like "/packages/blender-3.0/", but running "haunt build" with

>> pages on paths that include "." will render the pages with all the HTML

>> content inside a pre element. David, the maintainer of Haunt, does not

>> know yet why this would happen. If this issue is solved, there are

>> already helper builders in "apps/packages/builders.scm" to generate all

>> the pages.

> Was this issue fixed in the meantime? David?

>

>> So, for now, the packages pages are working as in the current website,

>> but not using tables (to make it easier to adapt the page to several

>> screen widths), and packages are distributed in numbered pages to avoid

>> big HTML pages that take too long to load.

>>

>> Also, the JavaScript code that gets package build status is not

>> integrated (couldn't figure this one out either).

> Did you have a chance to look at whether you could include the existing

> code? After all, the code is already there so we should be able to just

> “move” it to its new home without further ado.

>

> If that’s more complicated that this, then maybe we can ask for help

> from Alex Sassmannshausen, or simply delay it.

>

>> To complete (2.2), (2.3), and (2.4) someone could add helper builders to

>> the packages app, and recycle the related SXML pages already used in the

>> current website.

> Likewise, can’t we just reuse the existing code? I haven’t looked

> closely but I imagine we won’t have to rewrite all of these from

> scratch.

>

> How can we proceed? I wouldn’t want to let the fancy web site bitrot!

> I’m a bit swamped though so it would be more productive if you could

> directly hack on it on the repo, but I think you were unwilling to do

> this? Thoughts? :-)

> Hey :)

>

>

>

> On 01/07/17 09:26, Ludovic Courtès wrote:

>

>> Hi sirgazil,

>>

>> Slowly trying to catch up…

>>

>> sirgazil <sirgazil@zoho.com> skribis:

>>

>> This implementation is missing the following parts:

>>>

>>> 1. New screenshots

>>> 2. Packages pages

>>> 1. Package detail page

>>> 2. Packages issues page

>>> 3. Packages reproducibility page

>>> 4. Packages JSON file

>>>

>>> To complete part (1) someone could provide the screenshots (ideally

>>> 1920×1080 px) in JPG and add them to the "static/media/img" directory,

>>> and update the list of screenshots in "apps/base/data.scm".

>>>

>> Since “someone” has not shown up yet ;-), maybe we can delay (1), no?

>>

>> To complete (2), there are some package related procedures missing

>>> (https://bitbucket.org/sirgazil/guixsd-website/issues?

>>> status=new&status=open).

>>> I tried to use the code that is already in the current website, but

>>> couldn't figure things out.

>>>

>>> To complete part (2.1), there is an issue to solve: package pages go in

>>> paths like "/packages/blender-3.0/", but running "haunt build" with

>>> pages on paths that include "." will render the pages with all the HTML

>>> content inside a pre element. David, the maintainer of Haunt, does not

>>> know yet why this would happen. If this issue is solved, there are

>>> already helper builders in "apps/packages/builders.scm" to generate all

>>> the pages.

>>>

>> Was this issue fixed in the meantime? David?

>>

>> So, for now, the packages pages are working as in the current website,

>>> but not using tables (to make it easier to adapt the page to several

>>> screen widths), and packages are distributed in numbered pages to avoid

>>> big HTML pages that take too long to load.

>>>

>>> Also, the JavaScript code that gets package build status is not

>>> integrated (couldn't figure this one out either).

>>>

>> Did you have a chance to look at whether you could include the existing

>> code? After all, the code is already there so we should be able to just

>> “move” it to its new home without further ado.

>>

>> If that’s more complicated that this, then maybe we can ask for help

>> from Alex Sassmannshausen, or simply delay it.

>>

>> To complete (2.2), (2.3), and (2.4) someone could add helper builders to

>>> the packages app, and recycle the related SXML pages already used in the

>>> current website.

>>>

>> Likewise, can’t we just reuse the existing code? I haven’t looked

>> closely but I imagine we won’t have to rewrite all of these from

>> scratch.

>>

>> How can we proceed? I wouldn’t want to let the fancy web site bitrot!

>> I’m a bit swamped though so it would be more productive if you could

>> directly hack on it on the repo, but I think you were unwilling to do

>> this? Thoughts? :-)

>>

>

> I was going to take a look again, and see what I could do to complete the

> thing, but during the application setup of guix 0.13.0 many things were

> being built and the computer turned off three times. It seems it can't take

> that job (I didn't have this problem with 0.12.0, though).

>

> So I don't know what to do

> I was going to take a look again, and see what I could do to complete

> the thing, but during the application setup of guix 0.13.0 many things

> were being built and the computer turned off three times. It seems it

> can't take that job (I didn't have this problem with 0.12.0, though).

>

>

> 2017-07-04 22:00 GMT+02:00 sirgazil <sirgazil@zoho.com

> <mailto:sirgazil@zoho.com>>:

>

> Hey :)

>

>

>

> On 01/07/17 09:26, Ludovic Courtès wrote:

>

> Hi sirgazil,

>

> Slowly trying to catch up…

>

> sirgazil <sirgazil@zoho.com <mailto:sirgazil@zoho.com>> skribis:

>

> This implementation is missing the following parts:

>

> 1. New screenshots

> 2. Packages pages

> 1. Package detail page

> 2. Packages issues page

> 3. Packages reproducibility page

> 4. Packages JSON file

>

> To complete part (1) someone could provide the screenshots

> (ideally

> 1920×1080 px) in JPG and add them to the

> "static/media/img" directory,

> and update the list of screenshots in "apps/base/data.scm".

>

> Since “someone” has not shown up yet ;-), maybe we can delay

> (1), no?

>

> To complete (2), there are some package related procedures

> missing

> (https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open

> <https://bitbucket.org/sirgazil/guixsd-website/issues?status=new&status=open>).

> I tried to use the code that is already in the current

> website, but

> couldn't figure things out.

>

> To complete part (2.1), there is an issue to solve:

> package pages go in

> paths like "/packages/blender-3.0/", but running "haunt

> build" with

> pages on paths that include "." will render the pages with

> all the HTML

> content inside a pre element. David, the maintainer of

> Haunt, does not

> know yet why this would happen. If this issue is solved,

> there are

> already helper builders in "apps/packages/builders.scm" to

> generate all

> the pages.

>

> Was this issue fixed in the meantime? David?

>

> So, for now, the packages pages are working as in the

> current website,

> but not using tables (to make it easier to adapt the page

> to several

> screen widths), and packages are distributed in numbered

> pages to avoid

> big HTML pages that take too long to load.

>

> Also, the JavaScript code that gets package build status

> is not

> integrated (couldn't figure this one out either).

>

> Did you have a chance to look at whether you could include the

> existing

> code? After all, the code is already there so we should be

> able to just

> “move” it to its new home without further ado.

>

> If that’s more complicated that this, then maybe we can ask

> for help

> from Alex Sassmannshausen, or simply delay it.

>

> To complete (2.2), (2.3), and (2.4) someone could add

> helper builders to

> the packages app, and recycle the related SXML pages

> already used in the

> current website.

>

> Likewise, can’t we just reuse the existing code? I haven’t looked

> closely but I imagine we won’t have to rewrite all of these from

> scratch.

>

> How can we proceed? I wouldn’t want to let the fancy web site

> bitrot!

> I’m a bit swamped though so it would be more productive if you

> could

> directly hack on it on the repo, but I think you were

> unwilling to do

> this? Thoughts? :-)

>

>

> I was going to take a look again, and see what I could do to

> complete the thing, but during the application setup of guix

> 0.13.0 many things were being built and the computer turned off

> three times. It seems it can't take that job (I didn't have this

> problem with 0.12.0, though).

>

> So I don't know what to do

>

>

> computers need manteinance

>

> This could be a sign that your computer needs a refreshing of its

> thermal grease and a cleaning of its grates.

>

> Usually when you do that, it becomes an almost new machine and can

> compile lots of stuff. That's my experience, by the way.

> Another thing you could do is wait for a better building servers park

> to be available for Guix

>

> Rekado has mentioned that an improvement is in the pipe, to be

> delivered soonish

>

> With that you could find way more binaries ready for use and you won't

> need your own computer to compile them

>

> Ludo is way more competent and informed than I am, though, so he might

> have some better suggestion.

> Hi!

>

> sirgazil <sirgazil@zoho.com> skribis:

>

>> I was going to take a look again, and see what I could do to complete

>> the thing, but during the application setup of guix 0.13.0 many things

>> were being built and the computer turned off three times. It seems it

>> can't take that job (I didn't have this problem with 0.12.0, though).

> Ouch, that’s no good. The web site itself needs a few packages of

> course; if you do ‘guix pull’ (the CPU-intensive part) and then “guix

> build -f guix.scm” in the website directory, that should build the thing

> and download the prerequisites.

> If that goes wrong, I guess I’ll allocate time for this maybe next week

> and ask for guidance (every else is welcome to help!).

>

> Hi sirgazil,

> Sorry for the looong delay. I’ve finally incorporated the new web site

> in the guix-artwork.git repo along with a couple of fixes:

>

> https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/log/?h=wip-website-update

> I think it’s mostly ready to go. There are a few things missing from

> package pages:

>

> • The gnu icon next to GNU packages; it’d be easy to re-introduce, but

> I’m not sure whether/how it could fit well in the page design.

> • The JS build status icons. Likewise, I’m not sure how to make it

> look good on package pages.

> • The reproducibility and issue pages, but we’ve disabled them

> recently anyway for performance reasons.

> Thoughts?

>

> I guess none of these are blockers, though.

> what's missing for this branch to be merged? I took a quick build on this

> (and because I like the code as a reference), and it looks good. Builds,

> maybe some changes from master have to be applied to it (like using

> https instead of http at the download URLs).

>

> Anything missing we could help out with?

> I wasn't able to make use of the guix build -f build.scm

> for my adaption of its code base

> but haunt build on its own worked. The build.scm was

> complaining about this:

> Hello!

>

> It’s embarrassing that it took us so long, but I’m happy to say that the

> new web site is on line!

>

> https://www.gnu.org/software/guix/

>

> I’ve created redirects from the old /news URLs to the new /blog URLs,

> using the oh-so-elegant script below (I can’t believe it’s not Scheme!).

>

> Please report:

>

> • broken links;

>

> • other pages that need a redirect;

>

> • information that disappeared—I’m thinking in particular of talks,

> which used to appear under /help, but are now supposed to be made

> available via a blog post, the advantage being that we get

> /blog/tag/TOPIC links to the post;

>

> • anything else that’s broken.

>

> For web design issues, I hope sirgazil or someone else can answer and

> take action—I’m still not much of a web person and it’s probably better

> for everyone when I stick to writing Scheme. ;-)

>

> Note that the cron job that used to update package pages from

> hydra.gnu.org is now broken. I’ll try to come up with something else

> with proper GuixSD integration and run it from berlin.guixsd.org.

>

> Thanks again sirgazil for all the work!

>

> Ludo’.

>

> #!/bin/sh

>

> function gen_redirect

> {

> TARGET_URL="$1"

> cat <<EOF

> <!DOCTYPE html>

> <html lang="en">

> <head>

> <meta charset="UTF-8" />

> <title>Page has moved! — GNU Guix</title>

> <noscript><meta http-equiv="refresh" content="0; url=$TARGET_URL"></noscript>

> </head>

> <body onload="window.location = '$TARGET_URL';">

> Redirecting to the new page location...

> </body>

> </html>

> EOF

> }

>

> URL_PREFIX="/software/guix/"

>

> for page in "$@"

> do

> page_without_extension="`echo $page | sed -es'/\.html$//g'`"

> new_page="`find ../blog -name $page_without_extension -type d | head -1`"

> if [ -z "$new_page" ]

> then

> echo "no new page for '$page'" >&2

> exit 1

> fi

>

> # Strip '../'.

> new_page_url="$URL_PREFIX`echo $new_page | cut -c 4-`"

>

> echo "redirect '$page' -> '$new_page_url'"

> gen_redirect "$new_page_url" > "$page".new && mv "$page".new "$page"

> done

> Hello!

>

> It’s embarrassing that it took us so long, but I’m happy to say that the

> new web site is on line!

>

> https://www.gnu.org/software/guix/

>

> I’ve created redirects from the old /news URLs to the new /blog URLs,

> using the oh-so-elegant script below (I can’t believe it’s not Scheme!).

>

> Please report:

>

> • broken links;

>

> • other pages that need a redirect;

>

> • information that disappeared—I’m thinking in particular of talks,

> which used to appear under /help, but are now supposed to be made

> available via a blog post, the advantage being that we get

> /blog/tag/TOPIC links to the post;

>

> • anything else that’s broken.

>

> For web design issues, I hope sirgazil or someone else can answer and

> take action—I’m still not much of a web person and it’s probably better

> for everyone when I stick to writing Scheme. ;-)

>

> Note that the cron job that used to update package pages from

> hydra.gnu.org is now broken. I’ll try to come up with something else

> with proper GuixSD integration and run it from berlin.guixsd.org.

>

> Thanks again sirgazil for all the work!

>

> Ludo’.

>

> #!/bin/sh

>

> function gen_redirect

> {

> TARGET_URL="$1"

> cat <<EOF

> <!DOCTYPE html>

> <html lang="en">

> <head>

> <meta charset="UTF-8" />

> <title>Page has moved! — GNU Guix</title>

> <noscript><meta http-equiv="refresh" content="0; url=$TARGET_URL"></noscript>

> </head>

> <body onload="window.location = '$TARGET_URL';">

> Redirecting to the new page location...

> </body>

> </html>

> EOF

> }

>

> URL_PREFIX="/software/guix/"

>

> for page in "$@"

> do

> page_without_extension="`echo $page | sed -es'/\.html$//g'`"

> new_page="`find ../blog -name $page_without_extension -type d | head -1`"

> if [ -z "$new_page" ]

> then

> echo "no new page for '$page'" >&2

> exit 1

> fi

>

> # Strip '../'.

> new_page_url="$URL_PREFIX`echo $new_page | cut -c 4-`"

>

> echo "redirect '$page' -> '$new_page_url'"

> gen_redirect "$new_page_url" > "$page".new && mv "$page".new "$page"

> done

>

> Wow, that looks super cool, well done!

>

> Really smooth and modern feel. Joyful to explore :-)

>

> Hello!

>

> It’s embarrassing that it took us so long, but I’m happy to say that the

> new web site is on line!

>

> https://www.gnu.org/software/guix/

> This is of course minor issue but we just have to insert proper

> copyright + license notices in the .scm files. ;)

> I’m happy to say that the new web site is on line!

>

> https://www.gnu.org/software/guix/

> Please report:

>

> • broken links;

>

> • other pages that need a redirect;

>

> • information that disappeared—I’m thinking in particular of talks,

> which used to appear under /help, but are now supposed to be made

> available via a blog post, the advantage being that we get

> /blog/tag/TOPIC links to the post;

>

> • anything else that’s broken.

>

> I believe there is a typo on the home page below the video. „leave“

> should be „live“:

>

> diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm

> index bf727dd..f7c2d1c 100644

> --- a/website/apps/base/templates/home.scm

> +++ b/website/apps/base/templates/home.scm

> @@ -196,7 +196,7 @@

>

> (p

> "GNU Guix won't interfere with the package manager that comes

> - with your distribution. They can leave together."))

> + with your distribution. They can live together."))

>

> I believe there is a typo on the home page below the video. „leave“

> should be „live“:

>

> diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm

> index bf727dd..f7c2d1c 100644

> --- a/website/apps/base/templates/home.scm

> +++ b/website/apps/base/templates/home.scm

> @@ -196,7 +196,7 @@

>

> (p

> "GNU Guix won't interfere with the package manager that comes

> - with your distribution. They can leave together."))

> + with your distribution. They can live together."))

>

> (div

> (@ (class "action-box centered-text"))

> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:

> >

> > I believe there is a typo on the home page below the video. „leave“

> > should be „live“:

> >

> > diff --git a/website/apps/base/templates/home.scm b/website/apps/base/templates/home.scm

> > index bf727dd..f7c2d1c 100644

> > --- a/website/apps/base/templates/home.scm

> > +++ b/website/apps/base/templates/home.scm

> > @@ -196,7 +196,7 @@

> >

> > (p

> > "GNU Guix won't interfere with the package manager that comes

> > - with your distribution. They can leave together."))

> > + with your distribution. They can live together."))

> >

> > (div

> > (@ (class "action-box centered-text"))

>

> Did you write this patch by hand or did you use some kind of help? If

> you got help from something such as Emacs, I would like to learn how you

> did it so I can contribute with patches to easy stuff such as typos,

> website and documentation.

>