A dynamic website for Cita, a feminist open-source digital library publishing books by women. 💪🏻
Thank you for your interest in Cita. Here you’ll find how to contribute, suggest, reproduce. There are many ways of helping. Please take a look at this document, and if you still have some questions, reach out. . 👀
💻 For developers and experience designers: You’llfat our How-to-Contribute guidelines and our issues. Feel free to suggest things that you think would improve Cita’s UX/UI experience, but don’t file an issue to ask a question.
🖍🏻 For artists, illustrators and graphic designers: Here’s the current list of books we are working on or considering working on. If you think you can make the cover for one of these books or want to suggest a new book, e-mail us. / Tender Buttons / The Incidents in the Live of a Slave Girl / La Voz de la Mujer
📖🏻 For writers and editors: Here’s the list of books we are working on and the list of books we are considering starting. If you or someone you know can write a foreword for these books, please email us. If you are an editor, a careful reader or a writer familiar with HTML and Github, please take a look at our soon-to-be books, and read over them, comment.
🧐 What's inside technical overview?
A quick look at the top-level files and directories you'll see in a typical Gatsby project.
/node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
/src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template.
srcis a convention for “source code”.
.gitignore: This file tells git which files it should not track / not maintain a version history for.
gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.
gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).
gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.
gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.
LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.
package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.