Giter Site home page Giter Site logo

xsf / xmpp.org Goto Github PK

View Code? Open in Web Editor NEW
272.0 37.0 355.0 87.84 MB

xmpp.org website (builds: https://github.com/xsf/xmpp.org/actions)

Home Page: http://xmpp.org

Makefile 1.07% HTML 53.81% Python 17.68% JavaScript 16.53% CSS 8.16% Dockerfile 0.96% XSLT 1.78%

xmpp.org's Introduction

xmpp.org

Build Website

Please log any issues.

Contributing new content and updates

  • Fork the code to your own git repository.
  • Make your changes in /content or directly via GitHub.
  • When you are happy with your updates, submit a pull request describing the changes.
  • IMPORTANT: Before sending a Pull Request make sure that your forked repo is in sync with the base repo.
  • The updates will be reviewed and merged in.

Communication forum

Please use [email protected] for discussions about the site, content, generation etc.

Site generation

  • Commits to the master branch generate a new build.
  • Builds are visible at Github Actions.
  • Changes will be visible on xmpp.org after the next update.

Build instructions

Clone this repository:

git clone ssh://[email protected]/xsf/xmpp.org.git
cd xmpp.org

Build locally or via Docker:

Regular build

To run a development server on your local machine, follow these basic steps. You need to have the following dependencies installed:

  • Hugo
  • Python >=3.11
  • lua (>=5.2) and lua-expat

The development server will automatically rebuild the page whenever a file is changed:

make serve

View at http://localhost:1313

Docker build

To build and serve the website locally, simply run:

docker build -t xmpp-org --build-arg BASEURL=http://localhost/ --build-arg BUILDFUTURE=--buildFuture .

It will do the following:

  • Build a Docker image with a complete set of dependencies ready.
  • Generate the website from the locally checked out xmpp.org repository (make publish). This includes rules from deploy/xsf.conf.

For development convenience, you can serve the website locally:

docker run -p 80:80 -t -i xmpp-org

View at http://localhost:80

Development

Repository structure

<repo>
  public
    <generated files>
  content
    <website page files>
  themes
    <website theme>

Introduction to Hugo

Hugo’s quickstart page is a good place to learn about the basics of Hugo (setup, project skeleton, development cycle, etc.).

Theme development

xmpp.org's theme makes use of:

The theme (layout and styling) can be customized in the /themes/xmpp.org directory.

You can directly modify styles in themes/xmpp.org/assets/css/style.css.

xmpp.org's People

Contributors

agnauck avatar bear avatar butyoutried avatar cal0pteryx avatar dondebonair avatar echolon avatar flowdalic avatar ge0rg avatar guusdk avatar hlapp avatar horazont avatar imaginator avatar inputmice avatar intosi avatar jcbrand avatar lauracrossley avatar linkmauve avatar lnjx avatar mwild1 avatar nyco avatar peterwaher avatar pmaziere avatar ppjet6 avatar samwhited avatar sevefp avatar sockdrawermoney avatar tfar avatar thecoffemaker avatar woj-tek avatar zash avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

xmpp.org's Issues

Plan for existing content (input, please)

NOTE: Deleting things as they get added in or other, more specific issues created for them

We need to move existing content to the new site. But before we can do that, we need some kind of plan for what goes where.

I've pulled down an exhaustive list of all URLs on the present xmpp.org site, then grouped and sorted by what I think we should do with them.

I would really like input on the "misc" sections.


Misc:

Not sure what to do with these.

http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/
http://xmpp.org/about-xmpp/xsf/xsf-people/
http://xmpp.org/author/admin/
http://xmpp.org/about-xmpp/?page_id=297
http://xmpp.org/author/stpeter/
http://xmpp.org/about-xmpp/faq/?page_id=297
http://xmpp.org/internet-drafts/attic/draft-jabber-00.txt
http://xmpp.org/internet-drafts/attic/draft-jabber-00.html
http://xmpp.org/internet-drafts/attic/draft-miller-jabber-00.txt
http://xmpp.org/internet-drafts/attic/draft-miller-jabber-00.html
http://xmpp.org/about/bof-minutes.txt
http://xmpp.org/about/wg-charter.txt
http://xmpp.org/about/ipr-notice.txt

Misc XEP/Protocol supporting pages:

Not sure what to do with these.

http://xmpp.org/xmpp-protocols/xmpp-core/?page_id=297
http://xmpp.org/participate/become-a-member/editor-team/
http://xmpp.org/extensions/inbox/
http://xmpp.org/extensions/refs/
http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/

RFCs:

Need to make some decisions about how and where these are linked to/from. @ralphm would love to have your input.

http://xmpp.org/rfcs/rfc3920.html
http://xmpp.org/rfcs/rfc3921.html
http://xmpp.org/rfcs/rfc6120.html
http://xmpp.org/rfcs/rfc6121.html
http://xmpp.org/rfcs/rfc6122.html

convert blog posts only to markdown

per issue #17 the following need to be converted:

http://xmpp.org/2015/05/eyeball-networks/ 
http://xmpp.org/2015/04/xsf-gsoc-students-2015/
http://xmpp.org/2015/03/board-goals-for-2015/
http://xmpp.org/2015/03/summit-17-the-presentations/
http://xmpp.org/2015/03/an-introduction-to-xmppresearch-org/
http://xmpp.org/2009/02/google-summer-of-code/
http://xmpp.org/2015/03/xmpp-in-google-summer-of-code-2015/
http://xmpp.org/2015/03/no-its-not-the-end-of-xmpp-for-google-talk/
http://xmpp.org/2015/02/thank-you-xsf-sponsors/
http://xmpp.org/2015/01/its-all-about-choices-and-control/
http://xmpp.org/2015/01/xmpp-summit-17/
http://xmpp.org/2014/05/upcoming-events/
http://xmpp.org/2014/05/happy-encrypted-network/
http://xmpp.org/2014/04/xmpp-on-the-global-internet-of-things-day/
http://xmpp.org/2014/04/security-notice-uncontrolled-resource-consumption-with-highly-compressed-xmpp-stanzas/
http://xmpp.org/2014/03/third-security-test-day/

Remove need for .html extension from URLs

Presently, all page URLs end with .html

It's possible to get URLs that end without .html through changes to pelican's configuration.

Compare the present XSF configuration:

ARTICLE_PATHS = [ 'posts/blog', 'posts/learn' ]
ARTICLE_URL = 'posts/{blog_id}/{date:%Y}/{date:%b}/{date:%d}/{slug}'
ARTICLE_SAVE_AS = 'posts/{blog_id}/{date:%Y}/{date:%b}/{date:%d}/{slug}.html'

INDEX_SAVE_AS = 'posts/blog/index.html'
...
YEAR_ARCHIVE_SAVE_AS = 'posts/blog/{date:%Y}/index.html'

with my own site's pelican configuration:

PAGE_URL = '{slug}'
PAGE_SAVE_AS = '{slug}/index.html'

CATEGORY_URL = '{slug}'
CATEGORY_SAVE_AS = '{slug}/index.html'

YEAR_ARCHIVE_SAVE_AS = '{date:%Y}/index.html'
MONTH_ARCHIVE_SAVE_AS = '{date:%Y}/{date:%m}/index.html'
DAY_ARCHIVE_SAVE_AS = '{date:%Y}/{date:%m}/{date:%d}/index.html'

Release dates in tables libraries and servers

I suggest to remove the release dates in those tables.
Some of the dates are wrong right now. And it would be hard for us to maintain all this dates.
We should not give a visitor the impression that a software is outdated only because we missed updating the dates.

Consolidate these pages into /about/xsf and /community/membership

Re-add as blog posts

/posts/learn index not generating?

If I add a file to content/posts/learn I do get the learn post properly generated, but I don't seem to get any of the indexes generated.

Pages in need of initial content

Much of this content can come from the original website.

About

  • /about/who-uses-xmpp
  • /about/standards-process

Uses

  • /uses
  • /uses/instant-messaging
  • /uses/internet-of-things
  • /uses/social
  • /uses/webrtc
  • /uses/realtime-web

Software

  • /software
  • /software/clients
  • /software/servers
  • /software/libraries
  • /software/projects

Community

  • /community
  • /community/chat
  • /community/mailing-lists
  • /community/membership
  • /community/events
  • /community/sponsorship

Consolidate into /about/xsf and /community/membership

Updated RFCs

At the least, we need to change RFC 6122 to RFC 7622.

Also adding RFC 7395 would be good.

Content redirects

We'll want some redirects for some existing pages given the restructuring of some of the content. This issue is a placeholder for mapping 301s we'd need. (Waiting on #17)

Move protocol content to new site

Need to figure out where this lives first.

http://xmpp.org/xmpp-protocols/
http://xmpp.org/xmpp-protocols/protocol-namespaces/
http://xmpp.org/xmpp-protocols/xmpp-core/
http://xmpp.org/xmpp-protocols/xmpp-extensions/
http://xmpp.org/xmpp-protocols/internet-drafts/
http://xmpp.org/xmpp-protocols/rfcs/
http://xmpp.org/xmpp-protocols/?page_id=297
http://xmpp.org/protocols/activity/
http://xmpp.org/protocols/address/
http://xmpp.org/protocols/amp/
http://xmpp.org/protocols/bookmarks/
http://xmpp.org/protocols/bytestreams/
http://xmpp.org/protocols/caps/
http://xmpp.org/protocols/chatstates/
http://xmpp.org/protocols/commands/
http://xmpp.org/protocols/compress/
http://xmpp.org/protocols/disco/
http://xmpp.org/protocols/feature-neg/
http://xmpp.org/protocols/file-transfer/
http://xmpp.org/protocols/geoloc/
http://xmpp.org/protocols/http-auth/
http://xmpp.org/protocols/httpbind/
http://xmpp.org/protocols/ibb/
http://xmpp.org/protocols/jabber_client/
http://xmpp.org/protocols/jabber_iq_last/
http://xmpp.org/protocols/jabber_iq_oob/
http://xmpp.org/protocols/jabber_iq_privacy/
http://xmpp.org/protocols/jabber_iq_register/
http://xmpp.org/protocols/jabber_iq_roster/
http://xmpp.org/protocols/jabber_iq_rpc/
http://xmpp.org/protocols/jabber_iq_version/
http://xmpp.org/protocols/jabber_server/
http://xmpp.org/protocols/jabber_server_dialback/
http://xmpp.org/protocols/jabber_x_conference/
http://xmpp.org/protocols/jabber_x_data/
http://xmpp.org/protocols/jabber_x_oob/
http://xmpp.org/protocols/jidescaping/
http://xmpp.org/protocols/linklocal/
http://xmpp.org/protocols/mood/
http://xmpp.org/protocols/muc/
http://xmpp.org/protocols/nick/
http://xmpp.org/protocols/offline/
http://xmpp.org/protocols/pep/
http://xmpp.org/protocols/pubsub/
http://xmpp.org/protocols/rc/
http://xmpp.org/protocols/rosterx/
http://xmpp.org/protocols/rsm/
http://xmpp.org/protocols/shim/
http://xmpp.org/protocols/si/
http://xmpp.org/protocols/sipub/
http://xmpp.org/protocols/soap/
http://xmpp.org/protocols/streams/
http://xmpp.org/protocols/tune/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-bind/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-e2e/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-sasl/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-session/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-stanzas/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-streams/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-tls/
http://xmpp.org/protocols/urn_xmpp_archive/
http://xmpp.org/protocols/urn_xmpp_attention/
http://xmpp.org/protocols/urn_xmpp_avatar/
http://xmpp.org/protocols/urn_xmpp_blocking/
http://xmpp.org/protocols/urn_xmpp_bob/
http://xmpp.org/protocols/urn_xmpp_captcha/
http://xmpp.org/protocols/urn_xmpp_delay/
http://xmpp.org/protocols/urn_xmpp_features_rosterver/
http://xmpp.org/protocols/urn_xmpp_jingle/
http://xmpp.org/protocols/urn_xmpp_jingle_apps_rtp/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_ibb/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_ice-udp/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_raw-udp/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_s5b/
http://xmpp.org/protocols/urn_xmpp_langtrans/
http://xmpp.org/protocols/urn_xmpp_media-element/
http://xmpp.org/protocols/urn_xmpp_pie/
http://xmpp.org/protocols/urn_xmpp_ping/
http://xmpp.org/protocols/urn_xmpp_receipts/
http://xmpp.org/protocols/urn_xmpp_sm/
http://xmpp.org/protocols/urn_xmpp_ssn/
http://xmpp.org/protocols/urn_xmpp_time/
http://xmpp.org/protocols/urn_xmpp_xbosh/
http://xmpp.org/protocols/waitinglist/
http://xmpp.org/protocols/xdata-layout/
http://xmpp.org/protocols/xdata-validate/
http://xmpp.org/protocols/xhtml-im/
http://xmpp.org/xmpp-protocols/protocol-namespaces/?page_id=297
http://xmpp.org/protocols/jabber:client/
http://xmpp.org/protocols/jabber:server/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-session/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-bind/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-sasl/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-e2e/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-stanzas/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-streams/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-tls/

Logos for home page

  • Ruby logo
  • Python logo
  • Java logo
  • JS logo
  • Node.js logo
  • C++ logo
  • Lua logo
  • Apple logo
  • Win logo
  • Linux logo
  • Android logo

Settle on tagline / strapline

We need to settle on the homepage tagline / strapline. Current it reads:

"The most secure messaging standard"

Is that what we agree to use for launch?

header is too high

Header at new.xmpp.org looks too high for me
I think it should be in a half smaller, takes in one line.
2014-08-12 1 12 37

Council voting history

These voting records (linked from here) need to be ported to markdown pages in content/pages/about/xsf/records/council-votes

For generating markdown tables, this tool is awesome.

Arguably, these could all just go into one page reverse chronologically sorted.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.